Program, information processing device, manufacturing method, information processing method

Abstract

The present invention provides a program, apparatus, and method for easily creating messages to customers requesting cancellation fees. [Solution] The billing processing method includes: a reservation acquisition step that acquires reservation information for multiple reservations from a reservation management service operated by an external business operator; a reservation selection step that accepts an operation to select a predetermined reservation information from among the multiple reservation information acquired in the reservation acquisition step that does not satisfy the content relating to the reservation; a customer identification step that identifies customer information relating to the customer who made the reservation for the predetermined reservation information selected in the reservation selection step; a creation step that creates a message to bill a cancellation fee for the predetermined reservation information based on the predetermined reservation information selected in the reservation selection step and the customer information identified in the customer identification step; and a notification step that notifies the customer identified based on the customer information of the message created in the creation step.

Description

Technical Field

[0001] The present disclosure relates to a program, an information processing apparatus, a manufacturing method, and an information processing method.

Background Art

[0002] Techniques for making facility reservations such as accommodation facilities and restaurants online are known. Patent Document 1 discloses a reservation management system that can suppress damage caused by no-shows and cancellations and is easy to introduce into stores that receive many reservations by phone.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] There is a problem that a message for billing a cancellation fee to a customer cannot be easily created. Therefore, the present disclosure has been made to solve the above problems, and an object thereof is to provide a technique for easily creating a message for billing a cancellation fee to a customer.

Means for Solving the Problems

[0005] A program to be executed by a computer having a processor and a memory unit, wherein the processor executes: a reservation acquisition step of acquiring reservation information for multiple reservations from a reservation management service operated by an external business operator; a reservation selection step of accepting an operation to select a predetermined reservation information from among the multiple reservation information acquired in the reservation acquisition step that does not satisfy the content relating to the reservation; a customer identification step of identifying customer information relating to the customer who made the reservation for the predetermined reservation information selected in the reservation selection step; a creation step of creating a message to charge a cancellation fee for the predetermined reservation information based on the predetermined reservation information selected in the reservation selection step and the customer information identified in the customer identification step; and a notification step of notifying the customer identified based on the customer information identified in the customer identification step of the message created in the creation step. [Effects of the Invention]

[0006] According to this disclosure, it is possible to easily create a message to charge a cancellation fee to a customer. [Brief explanation of the drawing]

[0007] [Figure 1] This is a block diagram showing the functional configuration of System 1. [Figure 2] This block diagram shows the functional configuration of Server 10. [Figure 3] This is a block diagram showing the functional configuration of user terminal 20. [Figure 4] This diagram shows the data structure of user table 1012. [Figure 5] This diagram shows the data structure of reservation table 1013. [Figure 6] This diagram shows the data structure of billing table 1014. [Figure 7] This is a flowchart showing the operation of the reservation acquisition process. [Figure 8] This is a flowchart showing the operation of the reservation notification process. [Figure 9]This is a flowchart showing the billing process. [Figure 10] This is an example screen showing the operation of the reservation notification process. [Figure 11] This is an example screen showing the integration details page for billing processing. [Figure 12] This is an example screen showing the invoice creation page in the invoice processing. [Figure 13] This figure shows an example of a billing message that is sent to a customer during the billing process. [Figure 14] A block diagram showing the basic hardware configuration of Computer 90. [Modes for carrying out the invention]

[0008] The embodiments of this disclosure will be described below with reference to the drawings. In all the drawings illustrating the embodiments, common components are denoted by the same reference numerals, and repeated explanations are omitted. The following embodiments are not intended to unduly limit the content of this disclosure as described in the claims. Not all components shown in the embodiments are necessarily essential components of this disclosure. Also, each drawing is a schematic diagram and is not necessarily a strict illustration.

[0009] <Configuration of System 1> System 1 in this disclosure is an information processing system for providing information processing services to efficiently handle facility reservations and billing for cancellation fees of facility reservations. System 1 comprises information processing devices such as PMS501, OTA511, site controller 521, server 10, and user terminal 20, all connected via network N. Figure 1 is a block diagram showing the functional configuration of System 1. Figure 2 is a block diagram showing the functional configuration of server 10. Figure 3 is a block diagram showing the functional configuration of the user terminal 20.

[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 to be 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. Multiple operators provide different services according to reservation details such as accommodation and restaurant reservations. For example, OTA511 related to accommodation facilities includes jalan, Rakuten Travel, Ichiy休.com, etc. Usually, it is common for a facility to contract with and use one OTA.

[0013] <Configuration of site controller 521> Site Controller 521 is a system that provides an information processing service for centrally managing facility reservations received from customers through multiple OTAs (Online Travel Agencies). While facilities commonly use multiple different OTAs to improve occupancy rates, managing inventory, pricing, reservations, and pricing structures for each individual OTA can be cumbersome and prone to errors such as double bookings. Site Controller 521 allows facilities to efficiently manage reservations and other related tasks. For example, Site Controller 521 includes services such as Temairazu, TL Lincoln, and Rakutsu with. Typically, facilities contract with and utilize multiple OTA (Online Travel Agency) systems. PMS501, OTA511, and Site Controller 521 are typically provided as cloud services via the internet. Facility employees and others can access these services by accessing each system via the internet. Furthermore, customers wishing to use facilities can make reservations through OTAs (Online Travel Agencies). Information regarding customer facility reservations stored in the OTA is retrieved by the site controller and reflected in the PMS (Property Management System). Information regarding a single facility reservation is stored in the PMS, OTA, site controller, etc. Information regarding the same facility reservation is linked by a unique number called a reservation number, which will be described later.

[0014] <Server 10 Configuration> Server 10 is an information processing device that provides information processing services for efficiently billing for cancellation fees for facility reservations, etc. Specifically, Server 10 is connected to the Internet. Similarly, it is possible to obtain reservation information regarding facility reservations made for the provision of accommodations, restaurants, and other arbitrary services from multiple PMS 501, 502, etc., multiple OTA 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. is described as an example, but it is also applicable to reservation management services for skill sharing, lessons, etc. that do not require a facility. Specifically, server 10 can access API (Application Programming Interface) endpoints provided by reservation management services such as multiple PMS 501, 502, etc., multiple OTA 511, 512, etc., and multiple site controllers 521, 522, etc., upload data such as CSV files obtained from reservation management services by employees managing the facility, and automatically or manually obtain various information from reservation management services through scraping by robots such as web crawlers. Reservation management services include reservation systems (reservation engines) that accept reservations from the facility's own website, etc., reservation ledger systems that manage electronic reservations and have reservation management functions tailored to the specific needs of facilities such as restaurants, and reservation customer management systems that include reservation systems and reservation ledger systems and have customer management functions. Furthermore, this disclosure explains an example in which server 10 is connected to multiple reservation management services at accommodation facilities, etc., but reservation management services other than those for accommodation facilities may not require a reservation management system such as a PMS. This disclosure is applicable to any reservation management service, etc. that is capable of storing customer reservation information. The server 10 includes a storage unit 101 and a control unit 104.

[0015] <Configuration of the storage unit 101 of 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 that causes the control unit 104 of the server 10 to function as individual functional units. Application program 1011 includes applications such as a web browser application.

[0017] User table 1012 is a table that stores and manages information about member users (hereinafter referred to as "users") who use the service. In this disclosure, employees who manage and operate facilities, etc., are considered users of the information processing service related to this disclosure. When a user registers to use the service, their information is stored in a new record in user table 1012. This allows the user to use the services described in this disclosure. User table 1012 is a table with User ID as the primary key and contains columns for User ID, Username, User Data, Service Data, and Linked Reservation Service. Figure 4 shows the data structure of user table 1012.

[0018] The User ID is an item that stores user identification information to identify a user. User identification information is an item that is set to a unique value for each user. The username field is used to store the user's real name. However, the username can also be a nickname or any other string of characters. User data is a section that stores information about the user. User data includes information such as the user's name, address, and contact information. User data may include facility information that the user provides to customers. For example, user data may include facility name, facility address, facility contact information, etc. Service data is a section that stores information about the services a user provides to a customer. Service data includes information such as the type of service a user provides to a customer, the content of the service, the service fee, and the cancellation policy in case of cancellation. • The service type includes information that identifies the type of service, such as accommodation, food and beverage, transportation (airplanes, trains, buses, etc.), and lessons / classes. Multiple service types may be included. The service description includes information that identifies the service, such as accommodation plans, menus and courses for meals and drinks, travel routes by public transport, and seat types. It may include information about multiple services. • Service fees include charges for each service provided. Multiple pricing options may be available depending on the booking date (weekdays, holidays) and time of day (early morning, daytime, evening). The booking date is the date and time the service is provided. The cancellation policy includes information that defines the obligations that apply to customers when they cancel a reservation. For example, it may stipulate that if a customer cancels a reservation and the reservation date and time meet certain time requirements (for example, if the customer cancels within a specified period from the reservation date and time), the customer is obligated to pay the user part or all of the service fee as a cancellation fee. Service data may include information about facilities that users provide to their customers. For example, service data may include information such as facility name, facility address, and facility contact information. The linked reservation service is an item that stores information identifying the reservation management service, such as PMS, site controller, or OTA, that the user is using. Specifically, it stores reservation management service identification information (reservation management service ID) to identify the reservation management service the user is using. The user can edit the contents of the linked reservation service on an unillustrated management screen provided by server 10.

[0019] Reservation table 1013 is a table for storing and managing information related to facility reservations (reservation information). Reservation table 1013 is a table with reservation ID as the primary key and containing columns for reservation ID, reservation management service ID, user ID, reservation number, facility reservation data, customer data, cancellation data, priority, and update date and time. Figure 5 shows the data structure of the reservation table 1013.

[0020] The reservation ID is an item that stores reservation identification information to identify a reservation. Each reservation has a unique value assigned to it. The reservation management service ID is an item that stores service identification information to identify the reservation management service. Specifically, the service identification information is a string used to identify each of the following: multiple PMS 501, 502..., multiple OTA 511, 512..., and multiple site controllers 521, 522.... The User ID is an item that stores user identification information used to identify a user. The reservation number is an item that stores a number used to identify reservation information. Specifically, Facility reservation data is an item that stores information about the details of a facility reservation. Facility reservation information includes details such as the planned date and time of use of the facility, the desired usage plan, the number of users, and the usage fee. Customer data is an item that stores information (customer information) about customers who have made facility reservations. Customer information includes the customer's name, address, and contact information (telephone number, email address, social media ID). Customer information may also include information about customer attributes such as gender and age. Cancellation data is an item that stores cancellation information for reservation information. Cancellation information includes information indicating that the reservation identified by the reservation identification information has been canceled, the date and time of cancellation, the applicable cancellation policy, and the cancellation fee. Priority is an item that stores information regarding the priority of reservation details. The update date and time field stores the date and time the reservation information was updated.

[0021] The billing table 1014 is a table for storing and managing information (billing information) related to the billing of cancellation fees for reservation information. The billing table 1014 is a table that has columns for reservation ID, billing date and time, billing data, billing amount, and payment data. Figure 6 shows the data structure of the billing table 1014.

[0022] The reservation ID is an item that stores reservation identification information used to identify reservations that customers have canceled. The billing date and time field is used to record the date and time when a message requesting a cancellation fee was sent to the customer through the billing process described later. The billing data is an item that stores information regarding the billing of cancellation fees. The billing data includes string information such as one or more billing dates and times, the notification method for each billing date and time (telephone, email, SMS, etc.), and the content of the notification message for each billing date and time. The billing data may also include the content of the message requesting the cancellation fee. The billing amount is an item that stores information regarding cancellation fees. The payment data field is used to store information about when a customer has paid a cancellation fee. 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 server 10> The control unit 104 of the server 10 comprises a user registration control unit 1041, an acquisition unit 1042, a presentation unit 1043, and a billing unit 1044. The control unit 104 realizes each functional unit by executing the application program 1011 stored in the storage unit 101.

[0024] The user registration control unit 1041 processes information of users who wish to use the services related to this disclosure and stores it in the user table 1012. Information stored in the user table 1012 is obtained when a user opens a web page operated by the service provider from any information processing terminal, enters information into a designated input form, and sends it to the server 10. The user registration control unit 1041 stores the received information in a new record in the user table 1012, and user registration is completed. As a result, users stored in the user table 1012 can use the service. Prior to the registration of user information in the user table 1012 by the user registration control unit 1041, the service provider may perform a prescribed review and restrict whether or not the user can use the service. The user ID can be any string or number that can identify the user, and may be any string or number desired by the user, or the user registration control unit 1041 may automatically set any string or number.

[0025] The acquisition unit 1042 executes the reservation acquisition process. Details will be described later.

[0026] The presentation unit 1043 executes the reservation presentation process. Details will be described later.

[0027] The billing unit 1044 executes the billing process. Details will be described later.

[0028] <Configuration of User Terminal 20> The user terminal 20 is an information processing device operated by a user of the service. The user terminal 20 may be, for example, a mobile device such as a smartphone or tablet, or a stationary PC (Personal Computer) or laptop PC. It may also be a wearable device such as an HMD (Head Mount Display) or a smartwatch. The user terminal 20 includes a storage unit 201, a control unit 204, an input device 206, and an output device 208.

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

[0030] User ID 2011 is the user's account ID. The user sends User ID 2011 from user terminal 20 to server 10. Server 10 identifies the user based on User ID 2011 and provides the services related to this disclosure to the user. User ID 2011 includes information such as a session ID that is temporarily assigned by server 10 to identify the user using user terminal 20.

[0031] The application program 2012 may be pre-stored in the memory unit 201, or it may be configured to be downloaded from a web server operated by the service provider via a communication interface. Application Program 2012 includes applications such as web browser applications. 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.

[0032] <Configuration of the control unit 204 of the user terminal 20> The control unit 204 of the user terminal 20 comprises an input control unit 2041 and an output control unit 2042. The control unit 204 realizes each functional unit by executing the application program 2012 stored in the memory unit 201.

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

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

[0035] <System 1 operation> The following describes each process in System 1. Figure 7 is a flowchart showing the operation of the reservation acquisition process. Figure 8 is a flowchart showing the operation of the reservation presentation process. Figure 9 is a flowchart showing the operation of the billing process. Figure 10 shows an example screen illustrating the operation of the reservation notification process. Figure 11 is an example screen showing the linkage details page in the billing process. Figure 12 shows an example screen of the invoice creation page in the invoice processing. Figure 13 shows an example of a billing message that is sent to a customer during the billing process.

[0036] <Reservation acquisition process> The reservation retrieval process is the process of obtaining reservation information from the reservation management service.

[0037] <Overview of reservation acquisition process> The reservation acquisition process is a series of operations that involves identifying user information, retrieving facility reservation data, customer data, cancellation data, etc., from the reservation management service used by that user, and storing the reservation information. Specifically, the acquisition unit 1042 of server 10 acquires reservation information for each user at predetermined intervals from an external reservation management service used by that user. The acquisition unit 1042 of server 10 stores the acquired reservation information in the reservation table 1013 of server 10, associating it with user identification information to identify the user. The acquisition unit 1042 of server 10 periodically executes reservation acquisition processing. Note that the reservation acquisition processing may be configured to be executed in response to input operations by users utilizing the service. Alternatively, it may be configured to be executed automatically prior to the reservation presentation processing and billing processing described later.

[0038] The reservation acquisition process allows for the storage of reservation numbers, facility reservation data, customer data, and cancellation data obtained from multiple reservation management services operated by different external companies, associated with each user, in the reservation table 1013. This enables the centralized management of reservation information that is scattered across multiple reservation management services operated by different external companies, by consolidating it into the reservation table 1013. Furthermore, the multiple reservation management services operated by different external businesses include at least a property management system, a site controller, and an online travel agent system.

[0039] <Details of the reservation acquisition process> The details of the reservation acquisition process are explained below.

[0040] In step S101, the acquisition unit 1042 of the server 10 retrieves user information, including user ID, user data, service data, and linked reservation service, by searching the user table 1012. The acquisition unit 1042 of the server 10 executes the processing described below from step S102 onwards for each piece of retrieved user information. Furthermore, the acquisition unit 1042 of server 10 may change the frequency at which it executes the reservation acquisition process according to the acquired user data and service data. For example, the acquisition unit 1042 of server 10 calculates a priority according to the user data and service data and changes the frequency at which it executes the reservation acquisition process based on that priority. For example, the acquisition unit 1042 of server 10 executes the external reservation acquisition process at shorter intervals the higher the priority. This makes it possible to better synchronize the reservation information stored in the external reservation management service with the reservation information stored in the reservation table 1013 of server 10. For simplicity, this disclosure describes the reservation acquisition process for a predetermined user (identified by a predetermined user ID) below. Note that the processing from step S102 onward is also performed similarly for other user information stored in the user table 1012.

[0041] In step S102, the acquisition unit 1042 of the server 10 executes a reservation acquisition step in which it acquires reservation information for multiple reservations from multiple reservation management services operated by different external businesses. Specifically, the acquisition unit 1042 of server 10 acquires the reservation management service ID of the reservation management service used by the user, which is included in the linked service item acquired in step S101. Specifically, it acquires and identifies a string to identify the reservation management service such as PMS, site controller, and OTA that the user uses (contracts) to manage their facility reservations. Typically, one user has contracts with one PMS, one site controller, and multiple OTAs. The acquisition unit 1042 of server 10 identifies an API endpoint for accessing each reservation management service by referring to a database (not shown) or the like, based on the acquired reservation management service identification information. The acquisition unit 1042 of server 10 sends a request to the acquired API endpoint to acquire reservation information, including a predetermined user ID, or a user ID for each reservation management service identified based on the predetermined user ID. The reservation management service sends a reservation number, facility reservation data, customer data, and cancellation data as a response to the request. As a result, the acquisition unit 1042 of server 10 can acquire reservation numbers, facility reservation data, customer data, and cancellation data from external reservation management services for each reservation management service ID. Furthermore, the acquisition unit 1042 of server 10 only needs to be able to acquire reservation information for 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 to be able to acquire reservation information for 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, simultaneously. It is sufficient if reservation information can be acquired from any two or more reservation management services.

[0042] The reservation information obtained in the reservation acquisition step may include information about the reservation amount, reservation date and time, and cancellation date and time. Specifically, the facility reservation data acquired by the acquisition unit 1042 of server 10 includes information such as usage fees as the reservation amount and the reservation date and time. In addition, the cancellation data acquired by the acquisition unit 1042 of server 10 includes information on the cancellation date and time. Specifically, in reservation management services such as OTAs, customers can cancel reservation information they have made in the past by accessing the OTA. In this case, the OTA stores and accumulates information related to the cancellation as cancellation data. The acquisition unit 1042 of server 10 can acquire the cancellation data stored and accumulated by the OTA. Note that cancellation data is not limited to input operations by the customer; the user may also directly input cancellation data into the PMS, site controller, OTA, etc., upon receiving contact from the customer. Furthermore, even in the case of no-show cancellations that do not appear in the service usage, the user may directly input cancellation data into the PMS, site controller, OTA, etc. Furthermore, a user may edit the cancellation data in the reservation table 1013 by accessing the server 10 related to this disclosure by operating the input device 206 of the user terminal 20. For example, in the case of a no-show that does not appear to be using the service, the user can input cancellation information into the cancellation data field included in the reservation information record related to the no-show in the reservation table 1013 by operating the input device 206 of the user terminal 20. This allows the cancellation procedure for the customer's reservation information to be performed.

[0043] In step S102, the acquisition unit 1042 of the server 10 executes a terms acquisition step to acquire a cancellation policy that defines the cancellation conditions for the multiple reservation information acquired in the reservation acquisition step. Specifically, the cancellation data acquired by the acquisition unit 1042 of server 10 includes a cancellation policy that specifies the cancellation conditions that apply when facility reservation data is canceled. The acquisition unit 1042 of server 10 does not need to acquire cancellation policies for each reservation management service; it may acquire them from a predetermined reservation management service such as a PMS or site controller, and use the acquired cancellation policies for other reservation management services such as OTAs. The acquisition unit 1042 of the server 10 may also 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 relating to this disclosure in advance, inputs and edits the cancellation policy of the facility under their management, and stores it in advance in the service data item of the user table 1012. Furthermore, users may input and edit cancellation policies by editing cancellation data for each reservation by operating the input device 206 of the user terminal 20.

[0044] In this disclosure, a configuration for obtaining facility reservation data, customer data, and cancellation data from API endpoints provided by various reservation management services such as PMS, site controllers, and multiple OTAs is disclosed as an example, but is not limited to this. For example, facility reservation data, customer data, and cancellation data may be obtained from reservation management services such as PMS and multiple OTAs via the site controller's API endpoint. This case also includes obtaining reservation information for multiple reservations from multiple reservation management services operated by different external businesses. Furthermore, the user can access various websites provided by the PMS, site controller, and multiple OTAs by operating a web browser application or the like using the input device 206 of the user terminal 20, and download files such as CSV files containing reservation numbers, facility reservation data, customer data, and cancellation data. The user may also send the downloaded files to the server 10 by uploading them from an upload page (not shown) provided by the server 10 using the input device 206 of the user terminal 20. 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 of the reservation management services of the PMS, site controller, and multiple OTAs. Alternatively, the acquisition unit 1042 of server 10 may be configured to acquire facility reservation data, customer data, and cancellation data from various reservation management services such as PMS, site controllers, and multiple OTAs by executing a web scraping program stored in the storage unit 101 of server 10, without going through an API endpoint. Furthermore, the system may be configured so that a user can acquire reservation numbers, facility reservation data, customer data, cancellation data, etc., into the reservation table 1013 by operating the input device 206 of the user terminal 20.

[0045] In step S103, the acquisition unit 1042 of the server 10 stores the reservation management service ID, the predetermined user ID identified in step S101, the reservation number obtained from the reservation management service identified by the reservation management service ID, the facility reservation data, the customer data, and the cancellation data in the fields for the reservation management service ID, user ID, facility reservation data, customer data, and cancellation data of a new record in the reservation table 1013, respectively. At this time, the reservation ID is automatically assigned. The acquisition unit 1042 of server 10 may store the priority identified based on the reservation management service ID in the priority field of the newly created record. For example, in this disclosure, 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 that case, it is preferable that the priority order of PMS, site controller, and OTA remains unchanged. This is because the reservation management service with a higher priority has a higher reliability of the stored reservation information.

[0046] In this disclosure, the case in which all reservation information is obtained from an external reservation management service is disclosed as an example, but the acquisition unit 1042 of the server 10 may perform a process to obtain only the reservation information associated with cancellation data. Specifically, the acquisition unit 1042 of the server 10 may be configured to obtain only the reservation information for which cancellations have been received from customers and the reservation information for no-shows that do not appear in service usage from the external reservation management service, and not obtain other reservation information. This makes it possible to obtain only the reservation information for which cancellation fees will be charged to the customer, thereby reducing the amount of communication.

[0047] <Reservation confirmation process> The reservation presentation process is the process of presenting the reservation information obtained through the reservation acquisition process to the user.

[0048] <Overview of reservation confirmation process> The reservation presentation process is a series of operations that displays a reservation presentation screen to the user, retrieves the reservation information managed by the user when the user enters their user ID, and displays the reservation information in a list.

[0049] <Details of the reservation confirmation process> The details of the reservation confirmation process are explained below.

[0050] In step S301, the user operates the input device 206 of the user terminal 20, runs a browser application or the like, and opens the reservation presentation page D1 by entering the URL of the web page (reservation presentation page) for executing the reservation presentation process. The control unit 204 of the user terminal 20 sends a request to the server 10 that includes the user ID 2011 to open the reservation presentation page.

[0051] In step S302, when the server 10's presentation unit 1043 receives a request, it searches the reservation ID column in the reservation table 1013 based on the user ID 2011 and retrieves multiple reservation information.

[0052] In step S303, the presentation unit 1043 of the server 10 executes a list presentation step that presents a list of multiple 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 sends it to the user terminal 20. The control unit 204 of the user terminal 20 displays the reservation presentation page on the user terminal 20's display 2081 and presents it. Furthermore, the display unit 1043 of the server 10 may display only the reservation information associated with cancellation data from the reservation management service obtained from an external reservation management service on the reservation display page, and may not display reservation information not associated with cancellation data on the reservation display page.

[0053] Figure 10 shows an example of the reservation presentation screen in the reservation presentation process. The user terminal 20's display 2081 shows the reservation presentation page D1. The reservation presentation page D1 includes the reservation presentation screen D11. The reservation presentation screen D11 includes a billing button D110, a list of reservation management services contracted by the user D111, the name of the currently displayed reservation management service D112, and reservation information D121 and D122 obtained from the reservation management service named D112 through the reservation acquisition process. The reservation information D121 and D122 each include billing buttons D1211 and D1221, and cancellation fees D1212 and D1222, respectively.

[0054] The user can perform the billing process by operating the input device 206 of the user terminal 20 and pressing the billing button D110. In this case, the user performs the billing process manually by operating the input device 206 of the user terminal 20, without using the information stored in the reservation table 1013. Details of the billing process will be described later.

[0055] The list of reservation management services D111 is created by removing duplicates from the reservation management service IDs of the acquired reservation information and displaying a list of reservation management service names by referring to tables (not shown). The user selects a specific reservation management service from the list of reservation management services D111 by operating the input device 206 of the user terminal 20, from which they wish to display reservation information. The control unit 204 of the user terminal 20 displays the name D112 of the selected reservation management service on the reservation display 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 displays a list of records containing the selected specific reservation management service ID from the acquired reservation information in reservation information D121 and D122. Furthermore, the control unit 204 of the user terminal 20 sends a request to the server 10 to obtain billing information including the reservation IDs of reservation information D121 and D122. Based on the reservation IDs included in the request, the presentation unit 1043 of the server 10 searches the reservation ID field in the billing table 1014 and obtains the billing information associated with reservation information D121 and D122. The presentation unit 1043 of the server 10 sends the obtained billing information to the user terminal 20. The control unit 204 of the user terminal 20 changes the display 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 label "Bill this reservation" is displayed on the billing button D1211 and presented in a manner that the user can press. If there is billing information corresponding to the reservation information, the label "Billed" is displayed on the billing button D1221 and presented in a manner that the user cannot press. Even if there is billing information corresponding to the reservation information, it is possible to perform the billing process again, so the button color may be changed to an inconspicuous color such as gray and presented in a manner that the user can press.

[0056] The user can perform a billing process for the reservation information D121 associated with the billing button D1211 by operating the input device 206 of the user terminal 20 and pressing the billing button D1211. Details of the billing process will be described later.

[0057] In step S303, the presentation unit 1043 of the server 10 executes a calculation step to calculate the cancellation fee for 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 display unit 1043 of the server 10 may calculate the cancellation fee for each reservation based on the facility reservation data and cancellation data included in the acquired reservation information. For example, the display unit 1043 of the server 10 compares the reservation date and time and the cancellation date and time based on the usage fee included in the facility reservation data, and calculates the cancellation fee if a cancellation fee is incurred based on the cancellation policy. If the cancellation policy stipulates a 100% cancellation fee for same-day cancellations, a 70% cancellation fee for cancellations the day before, and a 50% cancellation fee for cancellations within three days prior, and the customer cancels on the day of the reservation or does not show up to use the service (no-show), the usage fee included in the facility reservation data is calculated as the cancellation fee. If the 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 the customer cancels within three days prior to the reservation, 50% of the usage fee included in the facility reservation data is calculated as the cancellation fee. The acquisition unit 1042 of server 10 sends the cancellation fee to the user terminal 20. The control unit 204 of user terminal 20 associates the received cancellation fees D1212 and D1222 with the reservation information to be calculated and displays them in a list in the reservation information D121 and D122.

[0058] In step S303, the presentation unit 1043 of the server 10 executes a candidate presentation step in which it presents candidate reservation information that will be used to create a message in which a cancellation fee will be charged, 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 the cancellation fee has been calculated as zero yen or more on the display 2081 of the user terminal 20 as a candidate reservation information for executing the billing process described later. For example, the control unit 204 of the user terminal 20 may highlight the billing buttons D1211 and D1221 on the display 2081 of the user terminal 20 as a candidate reservation information for executing the billing process. Alternatively, the control unit 204 of the user terminal 20 may present the candidate reservation information on the display 2081 of the user terminal 20 by displaying it in a pop-up dialog box or the like. This allows the user to execute the billing process without overlooking customers for whom a cancellation fee will be incurred. Furthermore, the control unit 204 of the user terminal 20 may highlight reservation information candidates with cancellation fees equal to or greater than a predetermined amount in a manner that allows for identification. Specifically, the background of reservation information D121 with a cancellation fee equal to or greater than a predetermined amount may be displayed on the reservation presentation screen D11 in a manner that allows for identification, such as a different background color, text color, font, and drawing style from other reservation information D122. For example, the control unit 204 of the user terminal 20 may display reservation information candidates with cancellation fees of 2,000 yen or more in a manner that allows for identification. In addition, the control unit 204 of the user terminal 20 may display reservation information candidates on the reservation presentation screen D11 in descending order of the amount of the cancellation fee. This allows users to process billing in order of cancellation fees, even when there are many potential bookings. Billing can be prioritized for bookings with higher cancellation fees, rather than those with lower fees. Users can identify customers or bookings from among the retrieved bookings to create a message requesting a cancellation fee, taking cancellation fees into consideration.

[0059] In step S303, the list presentation step may perform a step of presenting a list of reservation information obtained from multiple reservation management services operated by different external businesses in a manner that allows for the identification of duplicate reservation information. Specifically, in step S302, the acquisition unit 1042 of server 10 identifies records of different reservation information with the same reservation number as duplicate reservation information from among multiple reservation information obtained from the reservation table 1013. For example, the acquisition unit 1042 of server 10 counts the number of reservation numbers included in multiple reservation information and identifies reservation information with a count of 2 or more as duplicate reservation information. Specifically, in this disclosure, it is assumed that different reservation information with the same reservation number is obtained from a PMS, a site controller, and multiple OTAs and stored in the reservation table 1013. The acquisition unit 1042 of server 10 renders the background of the duplicate reservation information D121 on the reservation presentation screen D11 in a distinguishable manner, such as a different background color, text color, font, and drawing style from the other reservation information D122. This allows users to easily identify duplicate reservation information when multiple reservation management services operated by external vendors, such as PMS, site controllers, and OTAs, display a list of reservation information for the same reservation that is stored multiple times. For example, it can prevent sending customers messages that charge duplicate cancellation fees based on duplicate reservation information.

[0060] In step S303, the list presentation step executes a step that presents a list of reservation information obtained from multiple reservation management services operated by different external businesses, after excluding duplicate reservation information. Specifically, in step S302, the acquisition unit 1042 of server 10 removes all but one of the duplicate reservation information entries with the same reservation number from the multiple reservation information entries acquired from the reservation table 1013, and displays reservation information D121 and D122 as a list on the reservation presentation screen D11. This allows users to filter out duplicate reservation information when viewing a list of reservation details for the same reservation that have been stored multiple times across various reservation management services operated by external vendors, such as PMS, site controllers, and OTAs. For example, it can prevent sending customers duplicate cancellation fee bills based on duplicate reservation information.

[0061] The list presentation step performs a step that displays only one reservation from among multiple duplicate reservation information, identified according to the reservation management service from which the reservation information was obtained. Specifically, from among multiple duplicate reservation information, only the reservation with the highest priority is displayed, according to the priority order of the property management system, site controller, and online travel agent system. For example, the acquisition unit 1042 of server 10 assumes a case where it acquires multiple reservation information with duplicate reservation numbers, including a reservation management service ID that identifies travel management services related to PMS, site controllers, and OTAs. In this case, the acquisition unit 1042 of server 10 deletes reservation information where the reservation management service ID is not related to PMS, and where the reservation management service ID is related to site controllers and OTAs. The acquisition unit 1042 of server 10 displays a list of reservation information D121 and D122 for reservation management services related to PMS on the reservation presentation screen D11. This allows the system to display only one predefined reservation to the user, based on the priority of multiple reservation management services operated by external vendors. Customers can then create a message requesting cancellation fees based on the most recent reservation information they receive.

[0062] In step S303, the list presentation step may perform a step of presenting a list of reservation information excluding reservation information for which the customer who made the reservation has paid the cancellation fee. Specifically, the acquisition unit 1042 of server 10 searches the reservation ID field in the billing table 1014 based on the reservation IDs included in the multiple reservation information obtained from the reservation table 1013 in step S302, and obtains the payment data. The acquisition unit 1042 of server 10 excludes records from the multiple reservation information in which information indicating that a customer has paid a cancellation fee is stored in the payment data, and presents the reservation information D121 and D122 as a list on the reservation presentation screen D11. This allows the system to display a list of reservations excluding those for which cancellation fees have already been paid by the customer. It also prevents sending cancellation fee reminders for reservations for which payment has already been received.

[0063] In step S303, the list presentation step may perform a step in which, among the reservation information obtained from multiple reservation management services operated by different external businesses, if a customer has paid a cancellation fee for at least one of the duplicate reservation information entries, all of the duplicate reservation information entries are excluded and presented in the list. Specifically, in step S302, the acquisition unit 1042 of server 10, among the multiple reservation information acquired from the reservation table 1013, if there are multiple duplicate reservation information with the same reservation number, and the payment data of the billing information corresponding to the reservation ID of one of the reservation information contains information indicating that a customer has paid a cancellation fee, then that record is also excluded, and reservation information D121 and D122 are displayed as a list on the reservation presentation screen D11. This allows users to easily identify duplicate reservation information, even if there are multiple duplicate reservations, for which at least one cancellation fee has been paid. It also prevents sending cancellation fee requests for reservations for which payment has already been made.

[0064] In step S303, the list presentation step may also include a step in which, if a customer has paid a cancellation fee for at least one of the duplicate reservation information obtained from multiple reservation management services operated by different external businesses, the duplicate reservation information is presented in a manner that allows for identification of the duplicate reservation information. Specifically, in step S302, among the multiple reservation information obtained from the reservation table 1013, if the payment data of the billing information corresponding to the reservation ID of one of the duplicate reservation information having the same reservation number contains information indicating that a customer has paid a cancellation fee, the acquisition unit 1042 of the server 10 may draw the background of the reservation information D121 on the reservation presentation screen D11 in a distinguishable manner, such as a different background color, text color, font, and drawing style from the other reservation information D122. This allows users to easily identify duplicate reservation information, even if there are multiple duplicate reservations, for which at least one cancellation fee has been paid. It also prevents sending cancellation fee requests for reservations for which payment has already been made.

[0065] In step S303, the list presentation step executes a step in which, if the amount of the cancellation fee calculated for at least two or more reservation information items does not match among the reservation information obtained from multiple reservation management services operated by different external businesses, the list presents two or more reservation information items in a manner that allows for identification. Specifically, in step S302, the acquisition unit 1042 of the server 10 calculates a cancellation fee for each of the multiple duplicate reservation information entries that have the same reservation number, based on facility reservation data and cancellation data. The acquisition unit 1042 of the server 10 compares the calculated cancellation fees for the multiple reservation information entries, and if they do not match, it displays the reservation information entries D121 and D122 on the reservation display screen D11 in an identifiable manner, such as with a different background color, text color, font, and drawing style from the other reservation information. Furthermore, if the cancellation fees calculated for each of the multiple duplicate reservation information entries do not match, the control unit 204 of the user terminal 20 may indicate this discrepancy by displaying it in a pop-up dialog box or the like. This allows users to easily identify reservations with inconsistent cancellation fee amounts when there are multiple duplicate reservation entries. It also helps avoid sending messages that incorrectly charge cancellation fees.

[0066] <Invoice Processing> The billing process is the process of billing for cancellation fees for reservation information obtained through the reservation acquisition process.

[0067] <Overview of billing process> The billing process involves selecting the reservation information to send a message to from the list of reservation information displayed by the reservation presentation process, retrieving the selected reservation information, calculating the billing amount, creating a message, sending the message to the customer, and notifying the customer of the message.

[0068] <Details of billing process> The details of the billing process are explained below.

[0069] In step S501, the billing unit 1044 of the server 10 executes a reservation selection step in which it accepts a selection operation for a predetermined reservation information that does not satisfy the content of the reservation from among the multiple reservation information obtained in the reservation acquisition step. The reservation selection step executes a step in which it accepts a selection operation for the multiple reservation information presented in the list presentation step. Specifically, the user presses the billing button D1211 displayed on the reservation presentation screen D11 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 web page (linked content page) that displays the details of the reservation information, including the reservation ID of the reservation information D121 corresponding to the billing button D1211. As a result, the billing unit 1044 of the server 10 receives a selection operation for predetermined reservation information that has been canceled by the customer or does not satisfy the requirements related to the reservation, such as a no-show that does not appear to be using the service. Based on the received reservation ID, the billing unit 1044 of the server 10 searches the reservation ID field in the reservation table 1013 and obtains the reservation information. Based on the received reservation ID, the billing unit 1044 of the server 10 searches the reservation ID field in the billing table 1014 and obtains the billing information. When the billing unit 1044 of the server 10 receives a request, it generates a linking details page and sends it to the user terminal 20. The control unit 204 of the user terminal 20 displays and presents the linking details page on the display 2081 of the user terminal 20.

[0070] Figure 11 shows an example of the integration details page screen. The user terminal 20's display 2081 shows the integration details page D2. The integration details page D2 includes cancellation fees D201, billing status D202, message button D203, edit button D204, facility reservation information D211 based on facility reservation data, customer information D212 based on customer data, and billing information D213.

[0071] 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, check-in date, check-out date, and, if the reservation information includes cancellation data, the cancellation date and time included in the cancellation data.

[0072] In step S502, the billing unit 1044 of the server 10 performs a customer identification step to identify customer information relating 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 about the name and contact information of the customer who made the reservation. Specifically, customer information D212 includes contact information such as the customer number, reservation name (the name of the customer who made the reservation), telephone number, and email address included in the customer data, as well as information such as the number of guests included in the facility reservation data. Note that customer data may also be included in the facility reservation data.

[0073] In step S502, the billing unit 1044 of the server 10 performs a calculation step to calculate the 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. Note that the calculation of the cancellation fee D201 is the same as the calculation of the cancellation fee in step S303 of the reservation presentation process, so the explanation is omitted. The billing status D202 displays "Not Billed" if no billing information exists associated with the selected reservation information, and "Billed" if it exists. Additionally, if billing information exists, supplementary information such as the billing date and time and billing amount may be displayed. Note that calculating the cancellation fee in step S502 is optional, not mandatory. Specifically, in step S503, the user is asked to enter the cancellation fee, and if the billing information including the entered 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 the cancellation fee D201.

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

[0075] 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 (billing creation page) that includes the reservation ID displayed on the linking details page.

[0076] Furthermore, by operating the input device 206 of the user terminal 20 and pressing the edit button D204, the user can edit the facility reservation information D211, customer information D212, and billing information D213 displayed on the linked content page D2. The control unit 204 of the user terminal 20 sends 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 billing table 1014 based on the received information. This allows the user to edit the linked content page D2 displayed on the display 2081 of the user terminal 20. Alternatively, the user may also be able to edit 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.

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

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

[0079] When the billing unit 1044 of server 10 receives reservation information, it generates a billing creation page and sends it to the user terminal 20. The control unit 204 of user terminal 20 displays and presents the billing creation page on the display 2081 of user terminal 20. Figure 12 shows an example of the invoice creation screen in the invoice processing. The invoice creation page D3 is displayed on the user terminal 20's display 2081. The invoice creation page D3 includes the following fields: billing name D301, billing amount D302, and other billing information; contact information including telephone number D311 and 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 a send button D351.

[0080] In step S504, the billing unit 1044 of the server 10 executes a creation step to create a message that bills a cancellation fee for a predetermined reservation based on the predetermined reservation information selected in the reservation selection step and the customer information identified in the customer identification step. The creation step is a step to create a message that bills a cancellation fee to the customer who made the reservation for the predetermined 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 to present the cancellation fee calculated in the calculation step to the user. Specifically, by operating the input device 206 of the user terminal 20 and entering and editing each input field included in the billing creation page D3, the user can create a message to charge the customer a cancellation fee for the reservation information selected in step S501.

[0081] The billing unit 1044 of the server 10 may generate a billing page with values ​​entered in the input fields of billing page D3 based on the reservation information acquired in step S502, and send it to the user terminal 20. The control unit 204 of the user terminal 20 displays and presents the value entered in the input fields of billing page D3 on the display 2081 of the user terminal 20 based on the reservation information. Specifically, the billing unit 1044 of server 10 generates a billing creation page D3 with the customer name included in the customer data entered as billing name D301, the cancellation fee calculated based on the facility reservation data and cancellation data entered as billing amount D302, the customer's telephone number and email address included in the customer data entered as telephone number D311 and email address D312 respectively, the language used by the customer if it is included in the customer data entered as language D321, the reservation site name identified based on the reservation management service ID entered as reservation site name D331, the reservation number entered as reservation number D332, the check-in date and time and check-out date and time included in the facility reservation data entered as check-in date D333 and check-out date D334 respectively, the usage fee included in the facility reservation data entered as accommodation fee D335, and other incidental information included in the facility reservation data, customer data, cancellation data, etc., such as cancellation policy, entered in memo field D341, and sends it 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 presentation process, so the explanation is omitted. This allows users to avoid the tedious task of entering information into the input fields on the invoice creation page D3, and also helps to reduce input errors.

[0082] The user presses the send button D351 by operating the input device 206 of the user terminal 20. As a result, the control unit 204 of the user terminal 20 sends a request to the server 10 to send a message to the customer who made the reservation, which includes the information entered in the input fields of the billing creation page D3, informing them that a cancellation fee will be charged.

[0083] In this disclosure, the system is configured such that the linked information page D2 is displayed in step S502 and the cancellation fee is calculated in step S503. However, it is also acceptable to skip steps S502 and S503, display the billing creation page D3 instead of the linked information page D2, and execute from step S504. Furthermore, the linked information page D2 may be displayed by clicking a button or similar to view "detailed information" provided for each of the reservation information D121 and D122.

[0084] In step S504, the creation step may perform a step of creating a message that automatically charges a cancellation fee based on the cancellation fee calculated in the calculation step. In this disclosure, as an example, the billing unit 1044 of the server 10 generates a billing creation page D3 in 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 the user can input and edit. However, the creation of a message by the user in step S504 may be omitted. In other words, the billing unit 1044 of server 10 may automatically create a message assuming that the input values ​​for the input fields on the billing creation page D3 have been entered based on the reservation information. This allows the user to easily create a message to bill the customer for the cancellation fee without having to calculate the cancellation fee themselves.

[0085] In step S505, when the billing unit 1044 of the server 10 receives a request, it generates a message to the customer requesting a cancellation fee based on the values ​​in the input fields of 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 requesting the customer to pay a cancellation fee specified by the billing amount D302. The billing unit 1044 of server 10 stores the message containing the reservation ID, transmission date and time, recipient information (telephone number D311, email address D312, etc.), and billing amount D302 in new records for reservation ID, billing date and time, billing data, and billing amount, respectively, in the billing table 1014. This records in the billing table 1014 that billing processing has been performed for the customer. Additionally, the information entered in the input field on the invoice creation page D3 may be stored in the invoice data fields of the invoice table 1014.

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

[0087] Figure 13 shows an example of a billing message that is sent to a customer during the billing process. Billing message D4 includes the subject, sender information (user name, email address, address, etc.), recipient's name, company name, and a document requesting cancellation fees.

[0088] Customers who receive the message can pay the cancellation fee using payment methods such as bank transfer or credit card. When a customer pays the cancellation fee, the billing unit 1044 of 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 a payment has been made by the customer for the billing information. Furthermore, the payment information may be entered not by the billing unit 1044 of the server 10, but by the user operating the input device 206 of the user terminal 20.

[0089] In step S506, if the notification step has notified the customer of a message in the notification step, and the customer has not paid the cancellation fee after a predetermined period has elapsed, the notification step may also execute a step to notify the customer of a message again. Specifically, the billing unit 1044 of server 10 searches the payment data field in the billing table 1014 and retrieves billing information that includes the billing date and time for which the customer has not yet paid the cancellation fee. The billing unit 1044 of server 10 refers to the billing date and time field in the retrieved billing information and identifies billing information that is more than a predetermined period prior to the current date and time. For example, it may present billing information that is more than one week old. The billing unit 1044 of server 10 may, based on the identified billing information, resend a message to the customer requesting payment of the cancellation fee, thereby urging the customer to pay the cancellation fee. The message sending can also be configured to be automated. This allows the user to resend the message to customers who have not made payment without having to perform cumbersome resending tasks. The billing unit 1044 of server 10 stores and updates the resend date and time in the billing date and time field of the record in the billing table 1014 where the message was resent. Alternatively, the billing information may be newly stored in a new record in the billing table 1014.

[0090] <Basic Computer Hardware Configuration> Figure 14 is a block diagram showing the basic hardware configuration of computer 90. Computer 90 includes at least a processor 901, main memory 902, auxiliary memory 903, and a communication interface 991. These are electrically connected to each other by a communication bus 921.

[0091] The processor 901 is hardware for executing the instruction set written in a program. The processor 901 consists of an arithmetic unit, registers, peripheral circuits, etc.

[0092] Main memory 902 is used to temporarily store programs and data processed by programs, etc. For example, it is a volatile memory such as DRAM (Dynamic Random Access Memory).

[0093] Auxiliary storage device 903 refers to a storage device for saving data and programs. Examples include flash memory, HDD (Hard Disc Drive), magneto-optical disk, CD-ROM, DVD-ROM, and semiconductor memory.

[0094] The IF991 communication interface is an interface for inputting and outputting signals for communication with other computers via a network using wired or wireless communication standards. A network consists of various mobile communication systems, such as the internet, LANs, and wireless base stations. For example, a network includes 3G, 4G, and 5G mobile communication systems, LTE (Long Term Evolution), and wireless networks that can connect to the internet via designated access points (e.g., Wi-Fi®). When connecting wirelessly, communication protocols include, for example, Z-Wave®, ZigBee®, and Bluetooth®. When connecting via a wired connection, the network also includes connections made directly via USB (Universal Serial Bus) cables, etc.

[0095] Furthermore, by distributing all or part of each hardware configuration across multiple computers 90 and connecting them to each other via a network, a computer 90 can be virtually realized. Thus, the concept of computer 90 includes not only a computer 90 housed in a single enclosure or case, but also a virtualized computer system.

[0096] <Basic Functional Configuration of Computer 90> The functional configuration of the computer realized by the basic hardware configuration of computer 90 (Figure 14) will be explained. The computer comprises at least one functional unit: a control unit, a memory unit, and a communication unit.

[0097] Furthermore, the functional units of computer 90 can also be realized by distributing all or part of each functional unit across multiple computers 90 interconnected via a network. The concept of computer 90 includes not only a single computer 90 but also a virtualized computer system.

[0098] The control unit is realized when the processor 901 reads various programs stored in the auxiliary storage device 903, loads them into the main memory device 902, and executes processing according to those programs. The control unit can realize various functional units that perform information processing depending on the type of program. In this way, the computer is realized as an information processing device that performs information processing.

[0099] The memory unit is implemented by the main memory 902 and the auxiliary memory 903. The memory unit stores data, various programs, and various databases. The processor 901 can also reserve memory areas corresponding to the memory unit in the main memory 902 or the auxiliary memory 903 according to the program. The control unit can also cause the processor 901 to perform operations such as adding, updating, and deleting data stored in the memory unit according to the various programs.

[0100] A database, specifically a relational database, is used to manage and link together tabular data sets called masters, which are structurally defined by rows and columns. In a database, tables are called tables, masters are called masters, the columns of tables are called columns, and the rows of tables are called records. In a relational database, relationships can be established and linked between tables and masters. Typically, each table and master has a primary key column to uniquely identify records, but setting a primary key column is not mandatory. The control unit can instruct the processor 901 to add, delete, or update records in specific tables and masters stored in the memory unit, according to various programs. Furthermore, by storing data, various programs, and various databases in the memory unit, the information processing device and information processing system related to this disclosure can be considered to have been manufactured.

[0101] Furthermore, the databases and masters in this disclosure may include any data structures (lists, dictionaries, associative arrays, objects, etc.) in which information is structurally defined. Data structures also include data that can be considered as data structures by combining data with functions, classes, methods, etc., written in any programming language.

[0102] The communication unit is implemented by the communication IF991. The communication unit provides the functionality to communicate with other computers 90 via the network. The communication unit can receive information transmitted from other computers 90 and input it to the control unit. The control unit can cause the processor 901 to perform information processing on the received information according to various programs. The communication unit can also transmit information output from the control unit to other computers 90.

[0103] <Note> The details described in each of the above embodiments are noted below.

[0104] (Note 1) A program to be executed by a computer having a processor and a memory unit, wherein the processor executes: a reservation acquisition step (S102) in which reservation information for multiple reservations is acquired from a reservation management service operated by an external business operator; a reservation selection step (S501) in which the processor accepts a selection operation for a predetermined reservation information from among the multiple reservation information acquired in the reservation acquisition step that does not satisfy the content relating to the reservation; a customer identification step (S502) in which customer information relating to the customer who made the reservation for the predetermined reservation information selected in the reservation selection step is identified; a creation step (S504) in which a message is created to request a cancellation fee for the predetermined reservation information based on the predetermined reservation information selected in the reservation selection step and the customer information identified in the customer identification step; and a notification step (S506) in which the message created in the creation step is notified to the customer identified based on the customer information identified in the customer identification step. This allows facility operators and others to easily create messages to charge customers a cancellation fee for reservations that were not fulfilled due to cancellations or no-shows.

[0105] (Note 2) The program described in Appendix 1, wherein the reservation acquisition step (S102) is a step in which reservation information is acquired from multiple reservation management services operated by different external businesses, and the processor executes a list presentation step (S303) in which it presents a list of the multiple reservation information acquired in the reservation acquisition step, and the reservation selection step (501) is a step in which the program accepts a selection operation for the multiple reservation information presented in the list presentation step. This allows for centralized management of reservation information that is currently scattered across multiple reservation management services. A message requesting a cancellation fee from the customer can be seamlessly created based on the acquired reservation information.

[0106] (Note 3) Multiple reservation management services operated by different external operators include the programs described in Appendix 2, which include at least a property management system, a site controller, and an online travel agent system. This allows for centralized management of reservation information that is currently scattered and stored across multiple reservation management services operated by external companies with different roles and hierarchies, such as PMS, site controllers, and OTAs. A message requesting a cancellation fee from the customer can be seamlessly created based on the acquired reservation information.

[0107] (Note 4) The program described in Appendix 3 is a step in which the list presentation step (S303) presents a list of reservation information obtained from multiple reservation management services operated by different external businesses, in a manner that allows for the identification of duplicate reservation information. This allows users to easily identify duplicate reservation information when multiple reservation management services operated by external vendors, such as PMS, site controllers, and OTAs, display a list of reservation information for the same reservation that is stored multiple times. For example, it can prevent sending customers messages that charge duplicate cancellation fees based on duplicate reservation information.

[0108] (Note 5) The list presentation step (S303) is a step in the program described in Appendix 3 that presents a list of reservation information obtained from multiple reservation management services operated by different external businesses, after excluding duplicate reservation information. This allows users to filter out duplicate reservation information when viewing a list of reservation details for the same reservation that have been stored multiple times across various reservation management services operated by external vendors, such as PMS, site controllers, and OTAs. For example, it can prevent sending customers duplicate cancellation fee bills based on duplicate reservation information.

[0109] (Note 6) The program described in Appendix 5 is a step in which the list presentation step (S303) presents only one reservation from among multiple duplicate reservation information, which is identified according to the reservation management service from which the reservation information was obtained. This ensures that when presenting a list of reservation information for the same reservation that is duplicated across multiple reservation management services operated by external vendors, such as PMS, site controllers, and OTAs, the user will only be shown one reservation piece of information, identified by the external reservation management service from which the reservation information was obtained. For example, this prevents sending customers duplicate cancellation fee charges based on duplicate reservation information.

[0110] (Note 7) The list presentation step (S303) is a step in the program described in Appendix 6 that presents only the single highest-priority reservation from among multiple duplicate reservation information, according to the priority order of the property management system, site controller, and online travel agent system. This allows the system to present only one predetermined reservation to the user, based on the priority of multiple reservation management services operated by external vendors. Customers can create a message requesting a cancellation fee based on the most recent reservation information they have obtained.

[0111] (Note 8) The list presentation step (S303) is a step in the program described in Appendix 3 that presents a list of reservation information, excluding reservation information for which the customer who made the reservation has paid the cancellation fee. This allows the system to display a list of reservations excluding those for which cancellation fees have been paid by the customer. This prevents sending a message requesting a cancellation fee for reservations for which the cancellation fee has already been paid.

[0112] (Note 9) The program described in Appendix 8 includes a step (S303) in which, among reservation information obtained from multiple reservation management services operated by different external businesses, if a customer has paid a cancellation fee for at least one of the duplicate reservation entries, all of the duplicate reservation entries are excluded and presented in a list. This allows for the display of a list of reservations, even if there are multiple duplicate reservation entries, to exclude all of the duplicate entries if a cancellation fee has been paid for at least one of them. This prevents sending a message requesting a cancellation fee for reservations for which the cancellation fee has already been paid.

[0113] (Note 10) The program described in Appendix 8 includes a step (S303) in which, among the reservation information obtained from multiple reservation management services operated by different external businesses, if a customer has paid a cancellation fee for at least one of the duplicate reservation information entries, the program presents the duplicate reservation information in a manner that allows for identification. This allows users to easily identify duplicate reservation information, even when there are multiple duplicate reservation entries, for which at least one cancellation fee has been paid. This prevents sending a message requesting a cancellation fee for reservations for which the cancellation fee has already been paid.

[0114] (Note 11) The program described in Appendix 8 includes a step (S303) in which, among reservation information obtained from multiple reservation management services operated by different external businesses, if the amount of the cancellation fee calculated for at least two or more duplicate reservation information items does not match, the program presents a list of such two or more reservation information items in a manner that allows for identification. This allows users to easily identify reservation information with inconsistent cancellation fee amounts when there are multiple duplicate reservation entries. This helps avoid sending messages that incorrectly charge cancellation fees.

[0115] (Note 12) The customer information identified in the customer identification step (S502) includes the name and contact information of the customer who made the reservation, and the reservation information acquired in the reservation acquisition step (S102) includes the reservation amount, reservation date and time, and cancellation date and time, as described in Appendix 1 of the program. This makes it easy to create messages to customers requesting cancellation fees.

[0116] (Note 13) The program as described in Appendix 12, wherein the processor performs a terms acquisition step (S503) to acquire a cancellation policy that defines the cancellation conditions for predetermined reservation information selected in the reservation selection step, and a calculation step (S503) to calculate 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, and the creation step (S504) is a step to create a message that charges the customer who made the reservation for the predetermined reservation information a cancellation fee, including the cancellation fee calculated in the calculation step. This makes it easy to calculate cancellation fees based on reservation information, customer information, and cancellation policies, and also makes it easy to create messages to customers requesting cancellation fees.

[0117] (Note 14) The program as described in Appendix 13, wherein the processor performs a fee presentation step (S504) in which it presents the cancellation fee calculated in the calculation step to the user, and the creation step (S504) is a step in which the user creates a message in which they are charged a cancellation fee based on the cancellation fee presented in the fee presentation step. This allows users to easily calculate cancellation fees for their customers.

[0118] (Note 15) The creation step (S504) is the program described in Appendix 13, which is the step of creating a message that automatically charges the cancellation fee based on the cancellation fee calculated in the calculation step. This allows users to easily create messages to customers requesting cancellation fees without having to calculate them themselves.

[0119] (Note 16) The program described in Appendix 1, wherein the processor executes a terms acquisition step (102) for acquiring a cancellation policy that defines the cancellation conditions for multiple reservation information acquired in the reservation acquisition step; a calculation step (S303) for calculating the cancellation fee for 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; and a candidate presentation step (S303) for presenting candidate reservation information that can be used to create a message to charge a cancellation fee in the creation step based on the cancellation fee calculated in the calculation step. This allows users to identify, from among multiple reservation details they have retrieved, the customer or reservation information for which they should create a message requesting a cancellation fee, taking cancellation fees into consideration.

[0120] (Note 17) The notification step (S506) is a step in the program described in Appendix 1 in which, if the customer has not paid the cancellation fee after a predetermined period has elapsed since the notification step, the program sends another message to the customer. This allows you to send a message requesting a cancellation fee to a customer who has already received a message requesting the fee but has not yet paid it.

[0121] (Note 18) An information processing apparatus comprising a processor and a memory unit, wherein the processor executes a program described in any of the appendices 1 to 17. This allows facility operators and others to easily create messages to charge customers a cancellation fee for reservations that were not fulfilled due to cancellations or no-shows.

[0122] (Note 19) A method for manufacturing an information processing system, comprising an information processing device having a processor and a memory unit, the method comprising providing the information processing device with a program described in any one of the appendices 1 to 17. This allows facility operators and others to easily create messages to charge customers a cancellation fee for reservations that were not fulfilled due to cancellations or no-shows.

[0123] (Note 20) An information processing method performed by a computer comprising a processor and a memory unit, wherein the computer executes a program described in any of the appendices 1 to 17. This allows facility operators and others to easily create messages to charge customers a cancellation fee for reservations that were not fulfilled due to cancellations or no-shows. [Explanation of Symbols]

[0124] 1 System, 501 PMS, 5011 Storage Unit, 5014 Control Unit, 5016 Input Device, 5018 Output Device, 511 OTA, 5111 Storage Unit, 5114 Control Unit, 5116 Input Device, 5118 Output Device, 521 Site Controller, 5211 Storage Unit, 5214 Control Unit, 5216 Input Device, 5218 Output Device, 10 Server, 101 Storage Unit, 104 Control Unit, 106 Input Device, 108 Output Device, 20 User Terminal, 201 Storage 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 memory unit, The aforementioned processor, A reservation acquisition step involves obtaining reservation information for multiple reservations from a reservation management service operated by an external company, and A reservation selection step that accepts an operation to select a predetermined reservation information from among the multiple reservation information obtained in the reservation acquisition step that does not satisfy the content related to the reservation, A customer identification step that identifies customer information relating to a customer who made a reservation for the predetermined reservation information selected in the reservation selection step, A creation step to create a message requesting a cancellation fee for the predetermined reservation information based on the predetermined reservation information selected in the reservation selection step and the customer information identified in the customer identification step, A notification step in which the message created in the creation step is notified to the customer identified based on the customer information identified in the customer identification step, A program that executes this task.

2. The aforementioned reservation acquisition step is a step of acquiring the reservation information from multiple reservation management services operated by different external businesses. The aforementioned processor A list presentation step which presents a list of the multiple reservation information obtained in the reservation acquisition step, Execute, The aforementioned reservation selection step is a step in which the selection operation is received for the multiple reservation information presented in the list in the aforementioned list presentation step. The program according to claim 1.

3. The aforementioned 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. The program according to claim 2.

4. The aforementioned list presentation step is a step of presenting a list of reservation information obtained from multiple reservation management services operated by different external businesses, in a manner that allows for the identification of duplicate reservation information. The program according to claim 3.

5. The aforementioned list presentation step is a step of presenting a list of reservation information obtained from multiple reservation management services operated by different external businesses, after excluding duplicate reservation information. The program according to claim 3.

6. The aforementioned list presentation step is a step of presenting only one reservation information item that is identified according to the reservation management service that is the source of the reservation information, from among the multiple duplicate reservation information items. The program according to claim 5.

7. The aforementioned list presentation step is a step of presenting only the reservation information with the highest priority among the multiple duplicate reservation information, according to the priority order of the property management system, site controller, and online travel agent system. The program according to claim 6.

8. The aforementioned list presentation step is to present a list of reservation information excluding the reservation information for which the customer who made the reservation has paid the cancellation fee. The program according to claim 3.

9. The aforementioned list presentation step involves, among the reservation information obtained from multiple reservation management services operated by different external businesses, excluding all duplicate reservation information if at least one of the duplicate reservation information entries has been for which a cancellation fee has been paid by the customer, and then presenting the list. The program according to claim 8.

10. The aforementioned list presentation step is to present a list of duplicate reservation information obtained from multiple reservation management services operated by different external businesses, in a manner that allows for identification of the duplicate reservation information if, among the duplicate reservation information, a cancellation fee has been paid by the customer for at least one of the duplicate reservation information entries. The program according to claim 8.

11. The aforementioned list presentation step is a step in which, if the cancellation fee amounts calculated for at least two or more reservation information entries among the reservation information obtained from multiple reservation management services operated by different external businesses do not match, the two or more reservation information entries are presented in a manner that allows for identification of the two or more reservation information entries. The program according to claim 8.

12. The customer information identified in the customer identification step includes the name and contact information of the customer who made the reservation. The reservation information obtained in the aforementioned reservation acquisition step includes information on the reservation amount, reservation date and time, and cancellation date and time related to the reservation. The program according to claim 1.

13. The aforementioned processor A terms and conditions acquisition step to acquire a cancellation policy that specifies the cancellation conditions for the predetermined reservation information selected in the reservation selection step, A calculation step to calculate 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, Execute, The creation step is to create a message that charges a cancellation fee to the customer who made the reservation for the specified reservation information, including the cancellation fee calculated in the calculation step. The program according to claim 12.

14. The aforementioned processor A fee presentation step in which the cancellation fee calculated in the calculation step is presented to the user, Execute, The creation step is a step in which the user creates a message requesting a cancellation fee based on the cancellation fee presented in the fee presentation step. The program according to claim 13.

15. The creation step is to create a message that automatically charges a cancellation fee based on the cancellation fee calculated in the calculation step. The program according to claim 13.

16. The aforementioned processor A terms and conditions acquisition step for acquiring a cancellation policy that specifies the cancellation conditions for the multiple reservation information acquired in the aforementioned reservation acquisition step, A calculation step in which the cancellation fee for the multiple reservation information is calculated 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, A candidate presentation step presents candidate reservation information that, based on the cancellation fee calculated in the calculation step, will be used to create a message requesting the cancellation fee in the creation step. Execute The program according to claim 1.

17. The notification step is a step in which, if the customer has not paid the cancellation fee after a predetermined period has elapsed since the notification step in which the customer was notified of the message, the customer is notified of the message again. The program according to claim 1.

18. An information processing device comprising a processor and a memory unit, The processor executes the program according to any one of claims 1 to 17. Information processing device.

19. A method for manufacturing an information processing system including an information processing device comprising a processor and a memory unit, The information processing device is provided with the program according to any one of claims 1 to 17. A method for manufacturing information processing systems.

20. An information processing method performed by a computer comprising a processor and a memory unit, The computer executes the program described in any one of claims 1 to 17. Information processing methods.

Images