Accounts receivable purchase system, accounts receivable purchase method, and program
The accounts receivable purchasing system addresses the challenge of purchasing receivables based on future sales forecasts, allowing for efficient conversion into cash through on-site and advance payment information acquisition, forecasting, and client invitations, thereby facilitating financing based on predicted revenue.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-09-11
- Publication Date
- 2026-03-24
AI Technical Summary
Existing reservation platforms lack a system to efficiently purchase accounts receivable based on the predicted future sales of facilities or stores, limiting the ability to provide financing services proportional to future sales.
An accounts receivable purchasing system that acquires on-site and advance payment information from reservation systems, forecasts future sales, and invites clients to purchase accounts receivable services, enabling the conversion of these receivables into cash through debt collection and funding provision.
Enables the purchase of accounts receivable in proportion to future sales, facilitating financing based on predicted revenue, thereby providing a service that converts receivables into cash for facility or store operators.
Smart Images

Figure 2026052547000001_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to an accounts receivable purchase system, an accounts receivable purchase method, and a program.
Background Art
[0002] Based on information regarding an online store, the future sales of the store are predicted, and by purchasing accounts receivable corresponding to the predicted future sales amount from the store, financing is provided to the store. Regarding the technology for predicting the future sales of a store, an information processing apparatus that appropriately predicts future trends in a physical store is known (see, for example, Patent Document 1).
Prior Art Documents
Patent Documents
[0003]
Patent Document 1
Summary of the Invention
Problems to be Solved by the Invention
[0004] On a reservation platform, a customer can make reservations for facilities or stores such as travel, hotels, restaurants, beauty salons, etc. A reservation platform is a software program for automating reservations and reservation management. Based on reservations made on the reservation platform, it is preferable to be able to provide a service for purchasing accounts receivable corresponding to the future sales amount of the facility or store.
[0005] An object of the present invention is to provide an accounts receivable purchase system, an accounts receivable purchase method, and a program that can provide a service for purchasing accounts receivable corresponding to the future sales amount of a facility or store.
Means for Solving the Problems
[0006] One aspect of the present invention is an accounts receivable purchasing system comprising: an acquisition unit that acquires on-site payment information from a reservation system for reserving a facility or store; and an invitation processing unit that performs processing to invite a client to an accounts receivable purchasing service that purchases the future accounts receivable of a client operating a facility or store, based on the on-site payment information acquired by the acquisition unit.
[0007] One aspect of the present invention is a computer-operated method for purchasing accounts receivable, which involves obtaining on-site payment information from a reservation system for reserving a facility or store, and, based on the obtained on-site payment information, inviting the client to an accounts receivable purchase service that purchases the future accounts receivable of the client operating the facility or store.
[0008] One aspect of the present invention is a program that causes a computer to obtain on-site payment information from a reservation system for reserving facilities or stores, and to perform a process of inviting a client to an accounts receivable purchase service that purchases the future accounts receivable of a client operating a facility or store, based on the obtained on-site payment information. [Effects of the Invention]
[0009] According to the present invention, it is possible to provide a service that purchases receivables in proportion to the future sales amount of a facility or store. [Brief explanation of the drawing]
[0010] [Figure 1] This figure shows an example configuration of the accounts receivable purchase system according to this embodiment. [Figure 2] This block diagram shows an example of an accounts receivable purchasing device and a reservation system included in the accounts receivable purchasing system according to this embodiment. [Figure 3] This figure shows an example 1 of the operation of the accounts receivable purchase system according to this embodiment. [Figure 4] This figure shows an example 2 of the operation of the accounts receivable purchase system according to this embodiment. [Figure 5] This figure shows example 3 of the operation of the accounts receivable purchase system according to this embodiment. [Modes for carrying out the invention]
[0011] Next, the accounts receivable purchase system, accounts receivable purchase method, and program of this embodiment will be described with reference to the drawings. The embodiments described below are merely examples, and the embodiments to which the present invention is applied are not limited to the embodiments described below. In all the figures used to illustrate the embodiments, components with the same function are given the same reference numerals, and repeated explanations are omitted. Furthermore, in this application, "based on XX" means "based on at least XX," and includes cases where it is based on another element in addition to XX. Also, "based on XX" is not limited to cases where XX is used directly, but also includes cases where it is based on something that has been calculated or processed from XX. "XX" is any element (for example, any information).
[0012] (Embodiment) Embodiments of the present invention will be described below with reference to the drawings. Figure 1 shows an example of the configuration of the accounts receivable purchase system according to this embodiment. Accounts Receivable Purchase System 1 provides a service (hereinafter referred to as the "Accounts Receivable Purchase Service") that purchases accounts receivable and converts them into cash quickly. Accounts receivable include those generated when customers (hereinafter also referred to as "Users") make reservations for travel, hotels, restaurants, beauty salons, and other facilities or stores on the reservation platform.
[0013] The accounts receivable purchasing system 1 includes an accounts receivable purchasing device 100 and a reservation system 200. Figure 1 shows the accounts receivable purchasing device 100 and the reservation system 200, as well as user terminals 10-1 to 10-n (where n is an integer n>0) and client terminals 50-1 to 50-m (where m is an integer m>0).
[0014] User terminals 10-1 to 10-n and reservation system 200 can communicate with each other via communication network NW1. Client terminals 50-1 to 50-m, accounts receivable purchase device 100 and reservation system 200 can communicate with each other via communication network NW2. Communication network NW1 and communication network NW2 include the Internet, WAN (Wide Area Network), LAN (Local Area Network), public line, provider device, dedicated line, wireless base station, etc. Communication network NW1 and communication network NW2 may be composed of the same communication network.
[0015] User terminals 10-1 to 10-n are terminal devices used by users U1 to Un respectively. As user terminals 10-1 to 10-n, for example, stationary computer devices may be used, or portable computer devices such as smartphones and tablet computers (tablet PCs) may be used.
[0016] An example of users U1 to Un is a person who reserves a facility or store on a reservation platform. An example of a facility is travel, hotel, and an example of a store is a restaurant, beauty salon. Hereinafter, any one of user terminals 10-1 to 10-n is described as user terminal 10, and any one of users U1 to Un is described as user U.
[0017] Client terminals 50-1 to 50-m are terminal devices used by clients C1 to Cm respectively. As client terminals 50-1 to 50-m, for example, stationary computer devices may be used, or portable computer devices such as smartphones and tablet computers (tablet PCs) may be used.
[0018] An example of clients C1 to Cm is a person who operates a facility or a store. Clients C1 to Cm may be a person who operates a plurality of facilities or stores. Clients C1 to Cm do not have to be natural persons and may be a corporation (business operator) that operates one or more facilities or stores. Hereinafter, among client terminals 50-1 to 50-m, any client terminal is referred to as client terminal 50, and any client among clients C1 to Cm is referred to as client C.
[0019] The reservation system 200 provides a user U with a service (hereinafter referred to as "reservation service") for making a reservation and reservation management of a facility or a store on a reservation platform. The user U uses the user terminal 10 to make a reservation of a facility or a store on the reservation platform. The user U can settle the payment to the client C who operates the reserved facility or store by paying in advance on the reservation platform by credit card, cashless payment, etc. (hereinafter referred to as "advance settlement"), or by paying at the location of the facility or store, etc. (hereinafter referred to as "on-site settlement"). Cashless payment includes QR (Quick Response) (registered trademark) settlement, deferred payment (such as BNPL (Buy Now Pay Later)).
[0020] An example of on-site settlement includes those by credit card, electronic money, cashless settlement service using a QR (Quick Response) code, those by QR settlement, those by mobile payment, and those by cash. Also, the user U can combine advance settlement and on-site settlement for the payment to the client C who operates the reserved facility or store.
[0021] The accounts receivable purchasing device 100 provides accounts receivable purchasing services to client C. The following describes the case in which the accounts receivable purchasing system 1 provides accounts receivable purchasing services to client C. When user U makes payment to client C, which operates the facility or store reserved by user U, either in advance, on-site, or both, the accounts receivable purchasing system 1 "evaluates" or "assesssses" the amount to be paid, converts it into cash, and provides it to client C. Subsequently, the accounts receivable purchasing device 100 collects the debt by means of debt collection, such as issuing an invoice to client C.
[0022] The accounts receivable purchasing device 100 and reservation system 200 included in the accounts receivable purchasing system 1 will be described in detail below. Figure 2 is a block diagram showing an example of the accounts receivable purchasing device and reservation system included in the accounts receivable purchasing system according to this embodiment.
[0023] (Accounts receivable purchasing device 100) The accounts receivable purchasing device 100 includes a communication unit 102, an acquisition unit 103, an invitation processing unit 104, a forecasting unit 105, a purchasing processing unit 106, a debt collection entrustment processing unit 107, a collection processing unit 108, a calculation unit 109, and a storage unit 110. As the accounts receivable purchasing device 100, for example, a stationary computer device may be used, or a portable computer device such as a smartphone or a tablet computer (tablet PC) may be used.
[0024] The communication unit 102 is implemented by a communication module. The communication unit 102 communicates with external communication devices via the communication network NW2. The communication unit 102 communicates using a communication method such as a wired LAN. Alternatively, the communication unit 102 may communicate using a wireless communication method such as wireless LAN, Bluetooth®, or LTE (Long Term Evolution)®.
[0025] The storage unit 110 is implemented using HDD (Hard Disk Drive), flash memory, RAM (Random Access Memory), ROM (Read Only Memory), etc. The storage unit 110 stores client registration information and accounts receivable forecast and provision amount information. The client registration information includes client identification information of clients using the accounts receivable purchase service. The accounts receivable forecast and provision amount information includes information that associates the client identification information of clients using the accounts receivable purchase service with information indicating the forecast amount of accounts receivable held against that client and information indicating the amount of funds that can be provided to that client. The storage unit 110 may be implemented in the cloud.
[0026] All or part of the acquisition unit 103, invitation processing unit 104, prediction unit 105, purchase processing unit 106, debt collection entrustment processing unit 107, collection processing unit 108, and calculation unit 109 are functional units (hereinafter referred to as software functional units) that are realized by a processor such as a CPU (Central Processing Unit) executing a program stored in the storage unit 110.
[0027] Furthermore, all or part of the acquisition unit 103, invitation processing unit 104, prediction unit 105, purchase processing unit 106, debt collection entrustment processing unit 107, collection processing unit 108, and calculation unit 109 may be implemented by hardware such as LSI (Large Scale Integration), ASIC (Application Specific Integrated Circuit), or FPGA (Field-Programmable Gate Array), or by a combination of software functions and hardware.
[0028] (Reservation system 200) The reservation system 200 includes a communication unit 202, an acquisition unit 203, a billing processing unit 205, a creation unit 206, and a storage unit 210. The reservation system 200 may be, for example, a stationary computer device, or a portable computer device such as a smartphone or a tablet computer (tablet PC).
[0029] The communication unit 202 is implemented by a communication module. The communication unit 202 communicates with external communication devices via communication networks NW1 and NW2. The communication unit 202 communicates using a communication method such as wired LAN. Alternatively, the communication unit 202 may communicate using a wireless communication method such as wireless LAN, Bluetooth®, or LTE®.
[0030] The storage unit 210 is implemented using an HDD, flash memory, RAM, ROM, etc. The storage unit 210 stores pre-payment information and on-site payment information. The pre-payment information is information that associates user U's user identification information, the client identification information of the client operating the facility or store where user U made the pre-payment, pre-payment identification information, and information indicating the pre-payment amount. The on-site payment information is information that associates user U's user identification information, the client identification information of the client operating the facility or store where user U made the on-site payment, on-site payment identification information, and information indicating the on-site payment amount. The storage unit 210 may also be implemented in the cloud.
[0031] All or part of the acquisition unit 203, the billing processing unit 205, and the creation unit 206 are functional units (hereinafter referred to as software functional units) that are realized by a processor such as a CPU executing a program stored in the storage unit 210. Furthermore, all or part of the acquisition unit 203, the billing processing unit 205, and the creation unit 206 may be implemented by hardware such as an LSI, ASIC, or FPGA, or by a combination of software functions and hardware.
[0032] (Operation of Accounts Receivable Purchase System 1) The operation of the accounts receivable purchasing system 1 will be described with reference to Figures 3 to 5. Figure 3 is a diagram showing example 1 of the operation of the accounts receivable purchasing system according to this embodiment. Referring to Figure 3, the process by which the accounts receivable purchasing device 100 invites client C to the accounts receivable purchasing service will be described.
[0033] As an example, let's consider a case where user U uses user terminal 10 to reserve a facility on the reservation platform and makes payment to client C, which operates the reserved facility, via on-site payment.
[0034] (Step S1-1) In the reservation system 200, the acquisition unit 203 acquires local payment information. The local payment information includes client identification information of client C, which operates the facility where user U made the local payment, local payment identification information, and information indicating the local payment amount. For example, if user U makes a payment at a facility, client C, which operates the facility, may use client terminal 50 to create on-site payment information including client C's client identification information, user U's user identification information, on-site payment identification information, and information indicating the on-site payment amount, and send it to reservation system 200.
[0035] In this case, in the reservation system 200, the communication unit 202 receives local payment information transmitted by the client terminal 50. The acquisition unit 203 acquires the local payment information from the communication unit 202. The acquisition unit 203 acquires the client identification information of client C, the user identification information of user U, the local payment identification information, and information indicating the local payment amount included in the acquired local payment information, associates the acquired client identification information of client C, the user identification information of user U, the local payment identification information, and information indicating the local payment amount, and stores them in the local payment information included in the storage unit 210.
[0036] (Step S2-1) In the reservation system 200, the creation unit 206 acquires local settlement information from the acquisition unit 203. The creation unit 206 acquires client identification information, local settlement identification information, and information indicating the local settlement amount included in the acquired local settlement information, and creates settlement information including the acquired client identification information, local settlement identification information, and information indicating the local settlement amount. The communication unit 202 acquires the settlement information from the creation unit 206 and transmits it to the accounts receivable purchase device 100.
[0037] (Step S3-1) In the accounts receivable purchasing device 100, the communication unit 102 receives settlement information transmitted by the reservation system 200. The acquisition unit 103 acquires the settlement information from the communication unit 102 and obtains the client identification information, local settlement identification information, and information indicating the local settlement amount contained in the acquired settlement information. The acquisition unit 103 associates the acquired client identification information, local settlement identification information, and information indicating the local settlement amount and stores them in the storage unit 110. The forecasting unit 105 acquires client identification information, local settlement identification information, and information indicating the local settlement amount from the acquisition unit 103. Based on the acquired local settlement identification information and information indicating the local settlement amount, the forecasting unit 105 forecasts future accounts receivable. For example, based on the information indicating the local settlement amount, the forecasting unit 105 forecasts future accounts receivable by predicting how much sales will be generated over a predetermined period in the future, for example, two years. Here, two years is just an example and can be changed as appropriate. Furthermore, based on the forecasted amount of accounts receivable, the forecasting unit 105 forecasts the amount of funds that can be provided to the client. The forecasting unit 105 associates the client identification information, the information indicating the forecasted amount of accounts receivable, and the information indicating the amount of funds that can be provided to the client, and stores them in the accounts receivable forecast amount and provision amount information contained in the storage unit 110.
[0038] (Step S4-1) In the accounts receivable purchasing device 100, the invitation processing unit 104 obtains client identification information, local settlement identification information, and information indicating the local settlement amount from the acquisition unit 103, and determines whether the acquired client identification information is included in the client registration information stored in the storage unit 110. If the client identification information is not included in the client registration information, the invitation processing unit 104 performs a process to invite the client to the accounts receivable purchasing service. For example, the invitation processing unit 104 creates an invitation information notification request that includes information for inviting the client to the accounts receivable purchasing service.
[0039] (Step S5-1) In the accounts receivable purchasing device 100, the communication unit 102 receives an invitation information notification request from the invitation processing unit 104 and transmits it to the reservation system 200. (Step S6-1) In the reservation system 200, the communication unit 202 receives an invitation information notification request transmitted by the accounts receivable purchase device 100. The creation unit 206 obtains the invitation information notification request from the communication unit 202 and obtains the information for inviting the client to the accounts receivable purchase service included in the obtained invitation information notification request. The creation unit 206 creates an invitation information notification addressed to client C, which includes the information for inviting the client to the obtained accounts receivable purchase service.
[0040] (Step S7-1) In the reservation system 200, the communication unit 202 receives an invitation information notification from the creation unit 206 and transmits it to the client terminal 50. (Step S8-1) The client terminal 50 receives an invitation information notification sent by the reservation system 200.
[0041] (Step S9-1) The client terminal 50 acquires and outputs information for inviting the client to the accounts receivable purchase service included in the received invitation notification. The client terminal 50 may display the information for inviting the client to the accounts receivable purchase service on a display unit (not shown), or it may output the information for inviting the client to the accounts receivable purchase service by voice. Client C decides whether or not to accept the invitation to the accounts receivable purchase service based on the information provided to invite the client to the service. The following explanation continues regarding the case where Client C accepts the invitation to the accounts receivable purchase service and applies to have their accounts receivable purchased.
[0042] (Step S10-1) When client C requests the purchase of accounts receivable, client terminal 50 creates an accounts receivable purchase application that includes client C's client identification information and information for requesting the purchase of accounts receivable. Client terminal 50 transmits the created accounts receivable purchase application to accounts receivable purchase device 100.
[0043] (Step S11-1) In the accounts receivable purchasing device 100, the communication unit 102 receives an accounts receivable purchasing application transmitted by the client terminal 50. The invitation processing unit 104 obtains the accounts receivable purchasing application from the communication unit 102 and obtains the client identification information and information for applying to purchase accounts receivable included in the obtained accounts receivable purchasing application. The invitation processing unit 104 registers the obtained client identification information in the client registration information stored in the storage unit 110.
[0044] (Step S12-1) In the accounts receivable purchasing device 100, the forecasting unit 105 obtains information indicating the amount of funds that can be provided to a client associated with the client identification information from the accounts receivable forecast amount provision information in the storage unit 110. The forecasting unit 105 creates provision fund amount information that includes the client identification information and information indicating the amount of funds that can be provided to the client. (Step S13-1) In the accounts receivable purchasing device 100, the communication unit 102 obtains information on the amount of funds to be provided from the forecasting unit 105 and transmits it to the client terminal 50.
[0045] (Step S14-1) The client terminal 50 receives the information on the amount of funds that can be provided transmitted by the accounts receivable purchase device 100 and outputs information indicating the amount of funds that can be provided to the client, which is included in the information on the amount of funds that can be provided. The client terminal 50 may display the information indicating the amount of funds that can be provided to the client on a display unit (not shown), or it may output the information indicating the amount of funds that can be provided to the client by voice. Client C decides whether or not to request the purchase of accounts receivable based on the information output by client terminal 50 indicating the amount of funds that can be provided to the client. The following explanation continues regarding the case where client C decides to request the purchase of accounts receivable. Client terminal 50 creates an accounts receivable purchase request that includes client identification information and information for requesting the purchase of accounts receivable.
[0046] (Step S15-1) The client terminal 50 sends the created accounts receivable purchase request to the accounts receivable purchase device 100. (Step S16-1) In the accounts receivable purchasing device 100, the communication unit 102 receives an accounts receivable purchasing request transmitted by the client terminal 50. The purchasing processing unit 106 acquires the accounts receivable purchasing request from the communication unit 102. Based on the client identification information included in the acquired accounts receivable purchasing request, the purchasing processing unit 106 acquires information indicating the predicted amount of accounts receivable from the accounts receivable forecast amount provision information included in the storage unit 110. Based on the acquired information indicating the predicted amount of accounts receivable, the purchasing processing unit 106 confirms the purchase of accounts receivable.
[0047] (Step S17-1) In the accounts receivable purchasing device 100, the purchasing processing unit 106 creates an accounts receivable purchasing response that includes information notifying client C that the purchase of accounts receivable has been confirmed. (Step S18-1) In the accounts receivable purchase device 100, the communication unit 102 obtains an accounts receivable purchase response from the purchase processing unit 106 and transmits it to the client terminal 50.
[0048] (Step S19-1) The client terminal 50 receives the accounts receivable purchase response sent by the accounts receivable purchase device 100.
[0049] (Step S20-1) The client terminal 50 acquires and outputs information notifying that the purchase of accounts receivable included in the received accounts receivable purchase response has been confirmed. The client terminal 50 may display the information notifying that the purchase of accounts receivable has been confirmed on a display unit (not shown), or it may output the information notifying that the purchase of accounts receivable has been confirmed by voice. Client C can learn that the purchase of accounts receivable has been finalized based on information notifying them that the purchase of accounts receivable has been finalized.
[0050] (Step S21-1) In the accounts receivable purchasing device 100, the purchasing processing unit 106 provides funds to client C. (Step S22-1) In the accounts receivable purchasing device 100, the collection processing unit 108 obtains client identification information from the purchasing processing unit 106 that has confirmed the purchase of accounts receivable, and performs a process to collect accounts receivable from client C based on the acquired client identification information. For example, the collection processing unit 108 may create an invoice to collect accounts receivable from client C and send the created invoice to the client terminal 50. In this case, the collection processing unit 108 may also verify that client C has made a payment based on the invoice.
[0051] The flowchart in Figure 3 describes a case where user U reserves a facility on the reservation platform using user terminal 10, but this is not the only example. For example, it can also be applied to a case where user U reserves a store instead of a facility on the reservation platform using user terminal 10. Furthermore, this applies not only when user U makes a payment on-site, but also when they make a payment in advance. In this case, the acquisition unit 203 in the reservation system 200 acquires the advance payment information. The advance payment information includes the client identification information of client C, which operates the facility for which user U made the advance payment, and information indicating the advance payment amount.
[0052] For example, when user U makes a prepayment, the reservation system's acquisition unit 203 acquires client identification information of client C, user identification information of user U, prepayment identification information, and information indicating the prepayment amount. The acquired client identification information of client C, user identification information of user U, prepayment identification information, and information indicating the prepayment amount are associated and stored in the prepayment information of the storage unit 210. The creation unit 206 acquires client identification information, prepayment identification information, and information indicating the prepayment amount from the prepayment information of the storage unit 210, and creates settlement information including the acquired client identification information, prepayment identification information, and information indicating the prepayment amount. The communication unit 202 acquires the settlement information from the creation unit 206 and transmits it to the accounts receivable purchase device 100. Furthermore, this also applies when user U uses a combination of on-site payment and advance payment.
[0053] The flowchart in Figure 3 describes a case in which, in steps S5-1 to S7-1, information to invite client C to the accounts receivable purchase service is notified from the accounts receivable purchase device 100 to the client terminal 50 via the reservation system 200. However, this is not the only example. For example, information to invite client C to the accounts receivable purchase service may be sent from the accounts receivable purchase device 100 to the client terminal 50 without going through the reservation system 200. In this case, the invitation processing unit 104 in the accounts receivable purchase device 100 creates an invitation information notification that includes information to invite client C to the accounts receivable purchase service. The communication unit 102 receives the invitation information notification request from the invitation processing unit 104 and sends it to the client terminal 50.
[0054] According to the flowchart shown in Figure 3, when User U makes a payment to Client C, which operates the facility, via on-site settlement, the accounts receivable purchasing device 100 can notify Client C via the reservation system 200 with information to invite Client C to the accounts receivable purchasing service. This allows User U to inform Client C that the payment made to Client C via on-site settlement can be "evaluated" or "assessed," converted into cash, and provided to Client C.
[0055] Furthermore, if Client C accepts the invitation to the accounts receivable purchase service and applies to have its accounts receivable purchased, the payment to Client C via local settlement can be converted into cash and provided to Client C.
[0056] Figure 4 shows an example 2 of the operation of the accounts receivable purchasing system according to this embodiment. Referring to Figure 4, the processing when client C, who is already registered in the client registration information, applies to purchase payments for past sales and reservations in the accounts receivable purchasing device 100 will be explained.
[0057] (Step S1-2) In the reservation system 200, the creation unit 206 acquires past sales information and reservation information of client C. Past sales information includes sales information for a predetermined period in the past of facilities operated by client C. Sales include either sales by advance payment or sales by on-site payment, or both. Reservation information includes reservation information for facilities operated by client C. The creation unit 206 creates accounts receivable information, which includes client identification information of client C and the acquired past sales information and reservation information of client C. (Step S2-2) In the reservation system 200, the communication unit 202 obtains accounts receivable information from the creation unit 206 and transmits it to the accounts receivable purchase device 100.
[0058] (Step S3-2) In the accounts receivable purchasing device 100, the communication unit 102 receives accounts receivable information transmitted by the client terminal 50. The forecasting unit 105 obtains the accounts receivable information from the communication unit 102 and obtains the client identification information included in the obtained accounts receivable information, as well as the past sales information and reservation information of client C. The forecasting unit 105 forecasts future accounts receivable based on the obtained past sales information and reservation information of client C. For example, the forecasting unit 105 may forecast accounts receivable for a predetermined future period, for example, two years. Here, two years is just an example and can be changed as appropriate. Furthermore, the forecasting unit 105 forecasts the amount of funds that can be provided to the client based on the forecast amount of accounts receivable. The forecasting unit 105 associates client identification information, information indicating the forecast amount of accounts receivable, and information indicating the amount of funds that can be provided to the client, and stores this information in the accounts receivable forecast amount and provision amount information contained in the storage unit 110.
[0059] (Step S4-2) In the accounts receivable purchasing device 100, the forecasting unit 105 obtains information indicating the amount of funds that can be provided to the client associated with the client identification information from the accounts receivable forecast amount provision information in the storage unit 110. The forecasting unit 105 creates provision fund amount information that includes the client identification information and information indicating the amount of funds that can be provided to the client. (Step S5-2) In the accounts receivable purchasing device 100, the communication unit 102 obtains information on the amount of funds to be provided from the forecasting unit 105 and transmits it to the client terminal 50.
[0060] (Step S6-2) The client terminal 50 receives the accounts receivable forecast amount information transmitted by the accounts receivable purchase device 100. The client terminal 50 acquires and outputs information indicating the forecast amount of accounts receivable included in the acquired accounts receivable forecast amount information. The client terminal 50 may display the information indicating the forecast amount of accounts receivable on a display unit (not shown), or it may output the information indicating the forecast amount of accounts receivable by voice. Client C decides whether or not to request the purchase of accounts receivable based on the information indicating the estimated amount of accounts receivable output by client terminal 50. The following explanation continues regarding the case where client C decides to request the purchase of accounts receivable. Client terminal 50 creates an accounts receivable purchase request that includes client identification information and information for requesting the purchase of accounts receivable.
[0061] (Step S7-2) The client terminal 50 sends the created accounts receivable purchase request to the accounts receivable purchase device 100. (Step S8-2) In the accounts receivable purchasing device 100, the communication unit 102 receives the accounts receivable purchasing request transmitted by the client terminal 50. The purchasing processing unit 106 acquires the accounts receivable purchasing request from the communication unit 102. Based on the client identification information included in the acquired accounts receivable purchasing request, the purchasing processing unit 106 acquires information indicating the predicted amount of accounts receivable from the accounts receivable prediction value information stored in the storage unit 110. Based on the acquired information indicating the predicted amount of accounts receivable, the purchasing processing unit 106 confirms the purchase of accounts receivable.
[0062] (Step S9-2) In the accounts receivable purchasing device 100, the purchasing processing unit 106 creates an accounts receivable purchasing response that includes information notifying client C that the purchase of accounts receivable has been confirmed. (Step S10-2) In the accounts receivable purchase device 100, the communication unit 102 receives an accounts receivable purchase response from the purchase processing unit 106 and transmits it to the client terminal 50.
[0063] (Step S11-2) The client terminal 50 receives the accounts receivable purchase response sent by the accounts receivable purchase device 100. (Step S12-2) The client terminal 50 receives and outputs information notifying that the purchase of accounts receivable has been confirmed, which is included in the received accounts receivable purchase response. The client terminal 50 may display the information notifying that the purchase of accounts receivable has been confirmed on a display unit (not shown), or it may output the information notifying that the purchase of accounts receivable has been confirmed by voice. Based on the information notifying that the purchase of accounts receivable has been confirmed, client C can learn that the purchase of accounts receivable has been confirmed.
[0064] (Step S13-1) In the accounts receivable purchasing device 100, the purchasing processing unit 106 provides funds to client C. (Step S14-2) In the accounts receivable purchasing device 100, the collection processing unit 108 obtains client identification information and information indicating the amount of accounts receivable purchased from the purchasing processing unit 106, and performs a process to collect accounts receivable from client C based on the obtained client identification information and information indicating the amount of accounts receivable purchased. For example, the collection processing unit 108 may create an invoice to collect accounts receivable from client C and send the created invoice to the client terminal 50. In this case, the collection processing unit 108 may also verify that client C has made a payment based on the invoice.
[0065] In the flowchart shown in Figure 4, step S1-2 describes a case where the creation unit 206 acquires past sales information and reservation information of client C and creates accounts receivable information including client identification information of client C and the acquired past sales information and reservation information of client C. However, the example is not limited to this. For example, the creation unit 206 may be configured to acquire either the past sales information or reservation information of client C and create accounts receivable information including client identification information of client C and the acquired past sales information or reservation information of client C.
[0066] According to the flowchart shown in Figure 4, the accounts receivable purchasing device 100 can "evaluate" or "assess" the payments to be made by client C from past sales and reservations, convert them into cash, and provide the cash to client C.
[0067] Figure 5 shows an example 3 of the operation of the accounts receivable purchasing system according to this embodiment. Referring to Figure 5, we will now explain the case in which the accounts receivable purchasing device 100 entrusts the collection of accounts receivable to client C when the purchase of accounts receivable is confirmed.
[0068] (Step S1-3) In the accounts receivable purchasing device 100, the accounts receivable collection outsourcing processing unit 107 enters into an accounts receivable collection outsourcing agreement with client C. (Step S2-3) When user U makes a reservation on the reservation platform for a facility operated by client C and makes a prepayment, user terminal 10 creates information indicating prepayment identification information and the prepayment amount, and when user U makes a payment on-site, user terminal 10 creates information indicating on-site payment identification information and the on-site payment amount. User terminal 10 creates payment information including client C's client identification information and at least one of the information indicating the prepayment amount and the information indicating the on-site payment identification information and the on-site payment amount, and transmits it to the reservation system 200.
[0069] (Step S3-3) In the reservation system 200, the communication unit 202 receives payment information transmitted by the user terminal 10. The acquisition unit 203 acquires the payment information from the communication unit 202. The creation unit 206 acquires the payment information from the acquisition unit 203 and obtains the client identification information of client C included in the acquired payment information, and at least one of the information indicating the prepayment identification information and prepayment amount, and the information indicating the local payment identification information and local payment amount. The creation unit 206 creates accounts receivable information including the client identification information and at least one of the information indicating the prepayment identification information and prepayment amount, and the information indicating the local payment identification information and local payment amount.
[0070] (Step S4-3) In the reservation system 200, the communication unit 202 obtains accounts receivable information from the creation unit 206 and transmits it to the accounts receivable purchase device 100.
[0071] (Step S5-3) In the accounts receivable purchasing device 100, the communication unit 102 receives accounts receivable information transmitted by the reservation system 200. The calculation unit 109 obtains the accounts receivable information from the communication unit 102 and obtains the client identification information included in the obtained accounts receivable information, and at least one of the pre-payment identification information and information indicating the pre-payment amount, and the local payment identification information and information indicating the local payment amount. The calculation unit 109 calculates the withdrawal amount based on at least one of the obtained pre-payment identification information and information indicating the pre-payment amount, and the local payment identification information and information indicating the local payment amount.
[0072] For example, the calculation unit 109 derives the withdrawal amount from at least one of the pre-settlement identification information and information indicating the pre-settlement amount, and the local settlement identification information and information indicating the local settlement amount. Withdrawal is the settlement of sales after the purchase of accounts receivable based on a predetermined withdrawal rate, and the withdrawal amount is the amount settled based on the accounts receivable and the withdrawal rate. Based on the derived accounts receivable and the predetermined withdrawal rate, the calculation unit 109 calculates the withdrawal amount, for example, by multiplying the accounts receivable by the withdrawal amount. The calculation unit 109 associates the client identification information and the information indicating the withdrawal amount and stores them in the storage unit 110.
[0073] (Step S6-3) In the accounts receivable purchasing device 100, the calculation unit 109 creates withdrawal amount information including client identification information and information indicating the withdrawal amount. (Step S7-3) In the accounts receivable purchasing device 100, the communication unit 102 obtains the withdrawal amount information from the calculation unit 109 and transmits it to the reservation system 200. (Step S8-3) In the reservation system 200, the communication unit 202 receives the withdrawal amount information transmitted by the accounts receivable purchase device 100. The creation unit 206 obtains the withdrawal amount information from the communication unit 202 and obtains the client identification information and information indicating the withdrawal amount contained in the obtained withdrawal amount information. Based on the obtained client identification information and information indicating the withdrawal amount, the creation unit 206 creates billing information including information indicating the withdrawal amount.
[0074] (Step S9-3) In the reservation system 200, the communication unit 202 obtains billing information from the creation unit 206 and transmits it to the client terminal 50. (Step S10-3) The client terminal 50 receives the billing information transmitted by the reservation system 200 and obtains the client identification information and information indicating the withdrawal amount contained in the received billing information. Based on the obtained billing information, client C pays at least one of the prepayment amount and the on-site payment amount. The client terminal 50 creates a billing response that includes information indicating that the payment has been completed.
[0075] (Step S11-3) The client terminal 50 sends the created billing response to the reservation system 200. (Step S12-3) In the reservation system 200, the communication unit 202 receives the billing response transmitted by the client terminal 50. The billing processing unit 205 obtains the billing response from the communication unit 202. Based on the obtained billing response, the billing processing unit 205 deducts the withdrawal amount. The deducted withdrawal amount is paid to the accounts receivable purchase device 100.
[0076] The flowchart in Figure 5 describes a case in which, in steps S7-3 to S9-3, information indicating the withdrawal amount is notified from the accounts receivable purchasing device 100 to the client terminal 50 via the reservation system 200. However, the case is not limited to this example. For example, information indicating the withdrawal amount may be notified from the accounts receivable purchasing device 100 to the client terminal 50 without going through the reservation system 200. In this case, the calculation unit 109 in the accounts receivable purchasing device 100 creates a billing notice that includes client identification information and information indicating the withdrawal amount. The communication unit 102 receives the billing notice from the calculation unit 109 and transmits it to the client terminal 50.
[0077] The flowchart in Figure 5 describes the case in step S11-3 where information indicating that payment has been completed is notified from the client terminal 50 to the reservation system 200, but this is not the only example. For example, information indicating that payment has been completed may be notified from the client terminal 50 to the accounts receivable purchase device 100. In this case, the client terminal 50 creates a billing response that includes information indicating that payment has been completed and sends it to the accounts receivable purchase device 100.
[0078] The flowchart in Figure 5 describes a case in step S8-3 where the creation unit 206 in the reservation system 200 creates billing information including information indicating the withdrawal amount based on client identification information and information indicating the withdrawal amount. However, the example is not limited to this. For example, the creation unit 206 may create billing information that includes information indicating reservation platform usage receivables in addition to information indicating the withdrawal amount. An example of reservation platform usage receivables is advertising fees for the reservation platform. By configuring it in this way, the reservation system 200 can collect the withdrawal amount together with the reservation platform usage receivables, thereby improving the receivables recovery rate compared to when the reservation platform usage receivables and withdrawal amounts are collected separately.
[0079] According to the flowchart shown in Figure 5, the accounts receivable purchasing device 100 can entrust the collection of accounts receivable to client C, thereby reducing the processing load for collecting accounts receivable compared to a case where the collection of accounts receivable is not entrusted to client C.
[0080] In the embodiment described above, when the collection processing unit 108 collects accounts receivable from client C, it may collect them by any of the following methods: direct debit, credit card payment, or bank transfer. In addition, it may collect them by convenience store payment (payment at a convenience store (collection agency)), payment agency, Business Payments Solution Provider (BPSP), the Zengin Association standard format for transfers via internet banking, or external transfer. Examples of external transfers include transfers made at bank counters or transfers made using automated teller machines (ATMs).
[0081] This embodiment describes an example of the configuration and effects of the accounts receivable purchasing system 1. (1-1) According to the accounts receivable purchase system 1 of this embodiment, the accounts receivable purchase device 100 includes an acquisition unit 103 that acquires on-site settlement information from a reservation system 200 for reserving a facility or store, and an invitation processing unit 104 that performs processing to invite client C to an accounts receivable purchase service that purchases future accounts receivable from a client that operates a facility or store, based on the on-site settlement information acquired by the acquisition unit 103.
[0082] By configuring it in this way, the accounts receivable purchasing device 100 can perform a process to invite client C, which operates the facility, to the accounts receivable purchasing service when user U makes a payment to client C, which operates the facility, through on-site settlement. In this way, client C can be informed that the payment made through on-site settlement can be "evaluated" or "assessed," converted into cash, and provided to client C.
[0083] (1-2) In the accounts receivable purchasing device 100, the invitation processing unit 104 performs a process to invite client C to the accounts receivable purchasing service based on the client identification information of client C that operates the facility or store where the local payment was made, which is included in the local payment information. By configuring it in this way, the local settlement information can include the client identification information of client C, which operates the facility or store where the local settlement took place. Therefore, the accounts receivable purchasing device 100 can perform a process to invite client C to the accounts receivable purchasing service based on the client identification information included in the local settlement information.
[0084] (1-3) The accounts receivable purchasing device 100 further includes a forecasting unit 105 that forecasts future accounts receivable of client C based on local settlement information acquired by the acquisition unit 103, and a purchasing processing unit 106 that performs processing to purchase accounts receivable of client C based on the future accounts receivable forecasted by the forecasting unit 105. By configuring it in this way, the accounts receivable purchasing device 100 can predict client C's future accounts receivable based on local settlement information, and can then purchase client C's accounts receivable based on the predicted future accounts receivable.
[0085] (1-4) In the accounts receivable purchasing device 100, the acquisition unit 103 further acquires pre-payment information from the reservation system 200. The forecasting unit 105 further forecasts the future accounts receivable of client C based on the pre-payment information acquired by the acquisition unit 103. By configuring it in this way, the accounts receivable purchasing device 100 can predict client C's future accounts receivable based on advance settlement information in addition to local settlement information, and can then purchase client C's accounts receivable based on the predicted future accounts receivable.
[0086] (1-5) The accounts receivable purchasing device 100 further includes a collection processing unit 108 that processes accounts receivable from client C. By configuring it in this way, the accounts receivable purchasing device 100 can process the collection of accounts receivable that it has purchased from client C. For example, the collection processing unit 108 collects the accounts receivable that it has purchased from client C by billing based on the amount paid to client C through local settlement.
[0087] (2-1) According to the accounts receivable purchase system 1 of this embodiment, the accounts receivable purchase device 100 includes an acquisition unit 103 that acquires reservation information from a reservation system 200 for reserving facilities or stores, and a purchase processing unit 106 that performs processing to purchase future accounts receivable generated in the reservation system 200 based on the reservation information acquired by the acquisition unit 103. By configuring it in this way, the accounts receivable purchasing device 100 can acquire reservation information from the reservation system 200 for reserving facilities or stores, and based on the acquired reservation information, it can perform the process of purchasing future accounts receivable generated by the reservation system 200.
[0088] (2-2) In the accounts receivable purchasing device 100, the purchasing processing unit 106 performs the process of purchasing future accounts receivable that will arise in the reservation system 200 based on the client identification information of client C, which operates the facility or store where the reservation was made, as included in the reservation information. By configuring it in this way, the accounts receivable purchasing device 100 can include client identification information of client C, which operates the facility or store where the reservation was made, in the reservation information. Therefore, based on the client identification information of client C included in the reservation information, it can purchase future accounts receivable that will arise in the reservation system 200 as a result of the reservation of the facility or store operated by client C.
[0089] (2-3) The accounts receivable purchasing device 100 further includes a prediction unit 105 that predicts future accounts receivable of the reservation system 200 based on the reservation information acquired by the acquisition unit 103. The purchasing processing unit 106 performs the process of purchasing future accounts receivable that will arise in the reservation system 200 based on the future accounts receivable predicted by the prediction unit 105. By configuring it in this way, the accounts receivable purchasing device 100 can predict client C's future accounts receivable based on reservation information, and can then purchase client C's accounts receivable based on the predicted future accounts receivable.
[0090] (2-4) In the accounts receivable purchasing device 100, the acquisition unit 103 further acquires local settlement information from the reservation system 200. The purchasing processing unit 106 then performs a process to purchase future accounts receivable that will arise in the reservation system 200, based on the local settlement information acquired by the acquisition unit 103. By configuring it in this way, the accounts receivable purchasing device 100 can acquire not only reservation information from the reservation system 200 but also local settlement information. Based on the acquired local settlement information, it can then perform the process of purchasing future accounts receivable generated in the reservation system 200.
[0091] (2-5) The accounts receivable purchasing device 100 further includes a forecasting unit 105 that forecasts future accounts receivable of the reservation system 200 based on the local settlement information acquired by the acquisition unit 103. The purchasing processing unit 106 performs the process of purchasing future accounts receivable from clients that will arise in the reservation system 200 based on the future accounts receivable forecasted by the forecasting unit 105. By configuring it in this way, the accounts receivable purchasing device 100 can predict future accounts receivable from the reservation system 200 based on reservation information as well as on-site settlement information. Based on the predicted future accounts receivable, it can purchase future accounts receivable from client C that will arise in the reservation system 200.
[0092] (2-6) The accounts receivable purchasing device 100 further includes a collection processing unit 108 that processes accounts receivable from the reservation system 200. By configuring it in this way, the accounts receivable purchasing device 100 can process the collection of future accounts receivable that will arise in the reservation system 200 that has performed the purchasing process.
[0093] (3-1) According to the accounts receivable purchase system 1 of this embodiment, the accounts receivable purchase device 100 includes an acquisition unit 103 that acquires reservation information from a reservation system 200 for reserving a facility or store, a purchase processing unit 106 that performs processing to purchase future accounts receivable from client C, which operates the facility or store, based on the reservation information acquired by the acquisition unit 103, and an accounts receivable collection entrustment processing unit 107 that performs processing to entrust the collection of accounts receivable to client C. By configuring it in this way, when the accounts receivable purchasing device 100 processes the purchase of future accounts receivable from client C based on reservation information obtained from the reservation system 200, it can entrust the collection of accounts receivable to client C. Therefore, compared to when the collection of accounts receivable is not entrusted to client C, the processing load for collecting accounts receivable can be reduced.
[0094] (3-2) In the accounts receivable purchasing device 100, the purchasing processing unit 106 performs the process of purchasing future accounts receivable from client C based on the client identification information of client C, which operates the facility or store where the reservation was made, as included in the reservation information. By configuring it in this way, the accounts receivable purchasing device 100 can include client identification information of client C, which operates the facility or store where the reservation was made, in the reservation information. Therefore, it can purchase future accounts receivable from client C based on the client identification information included in the reservation information.
[0095] (3-3) The accounts receivable purchasing device 100 further includes a calculation unit 109 that acquires information indicating accounts receivable from client C and calculates a withdrawal amount based on the acquired information indicating accounts receivable. The purchasing processing unit 106 performs the process of purchasing client C's future accounts receivable based on the withdrawal amount calculated by the calculation unit 109. By configuring it in this way, the accounts receivable purchasing device 100 can calculate the withdrawal amount based on information indicating accounts receivable obtained from client C. Therefore, the accounts receivable purchasing device 100 can purchase future accounts receivable from client C based on the calculated withdrawal amount.
[0096] (3-4) The accounts receivable purchasing device 100 further includes a collection processing unit 108 that processes accounts receivable. By configuring it in this way, the accounts receivable purchasing device 100 can process the collection of future accounts receivable from clients whose accounts receivable have been purchased.
[0097] (3-5) In the accounts receivable purchasing device 100, the collection processing unit 108 collects the withdrawal amount based on the accounts receivable collected by the reservation system 200 from client C. By configuring it in this way, the accounts receivable purchasing device 100 can recover the withdrawal amount from the accounts receivable collected by the reservation system 200.
[0098] (3-6) In the accounts receivable purchasing device 100, the receivables collected by the reservation system 200 from client C include the receivables that the reservation system 200 has against client C. By configuring it in this way, the reservation system 200 can collect the withdrawal amount along with the receivables it has from client C, thus improving the receivables recovery rate compared to when the reservation system 200 collects the receivables and withdrawal amounts separately from client C.
[0099] (4-1) The accounts receivable purchase system 1 according to this embodiment includes a purchase processing unit 106 that processes the purchase of accounts receivable from client C, which operates a facility or store; a collection processing unit 108 that processes the collection of accounts receivable from user U, which has used the facility or store; and a billing processing unit 205 that bills for the accounts receivable collected by the collection processing unit 108 and the settlement amount that client C settles with the business operator. By configuring it in this way, the accounts receivable purchasing system 1 can collect accounts receivable along with the settlement amount that client C settles with the business operator, thus improving the collection rate compared to when settlement amounts and accounts receivable are collected separately. An example of a business operator is the operator of the reservation system 200.
[0100] (4-2) The accounts receivable purchasing device 100 further includes an acquisition unit 103 that acquires reservation information from a reservation system 200 for reserving facilities or stores. The purchasing processing unit 106 performs the process of purchasing the accounts receivable of client C based on the client identification information of client C included in the reservation information acquired by the acquisition unit 103. By configuring it in this way, the reservation information can include the client identification information of client C, so the accounts receivable purchasing device 100 can purchase the accounts receivable of client C based on the client identification information included in the reservation information.
[0101] (4-3) The accounts receivable purchasing device 100 is further equipped with a calculation unit 109 that calculates the withdrawal amount based on the accounts receivable collected by the collection processing unit 108. The billing processing unit 205 bills for the withdrawal amount calculated by the calculation unit 109 and the settlement amount that client C settles with the business operator. By configuring it in this way, the reservation system 200 can collect the withdrawal amount along with the settlement amount that client C settles with the service provider. Therefore, compared to a case where the reservation system 200 collects the settlement amount that client C settles with the service provider and the withdrawal amount separately, it can improve the debt collection rate.
[0102] (4-4) In the accounts receivable purchasing device 100, the collection processing unit 108 collects the withdrawal amount based on the accounts receivable collected from client C by the reservation system 200, which reserves facilities or stores based on the withdrawal amount. By configuring it in this way, the accounts receivable purchasing device 100 can collect the withdrawal amount based on the accounts receivable collected by the reservation system 200.
[0103] While embodiments and modifications of the present invention have been described in detail above with reference to the drawings, the specific configuration is not limited to these embodiments and may include design changes and the like that do not depart from the spirit of the present invention. For example, a computer program to implement the functions of each of the above-mentioned devices may be recorded on a computer-readable recording medium, and the program recorded on this recording medium may be loaded into a computer system and executed. The term "computer system" here may include hardware such as an operating system and peripheral devices.
[0104] Furthermore, "computer-readable recording media" refers to writable non-volatile memory such as flexible disks, magneto-optical disks, ROMs, and flash memory, portable media such as DVDs (Digital Versatile Discs), and storage devices such as hard disks built into computer systems. Furthermore, "computer-readable recording media" also includes volatile memory (such as DRAM (Dynamic Random Access Memory)) within computer systems that act as servers or clients when programs are transmitted via communication networks such as the Internet or communication lines such as telephone lines, which retain programs for a certain period of time.
[0105] Furthermore, the above program may be transmitted from a computer system that stores the program in a memory device or the like to another computer system via a transmission medium or by transmission waves within the transmission medium. Here, the "transmission medium" for transmitting the program refers to a medium that has the function of transmitting information, such as a communication network (communication network) such as the Internet or a communication line (communication line) such as a telephone line. Furthermore, the above program may be intended to implement some of the functions described above. It may also be a so-called differential file (differential program) that can implement the aforementioned functions in combination with programs already recorded in the computer system. [Explanation of Symbols]
[0106] 1…Accounts receivable purchase system, 10, 10-1~10-n…User terminals, 50, 50-1~50-n…Client terminals, 100…Accounts receivable purchase system, 102…Communication unit, 103…Acquisition unit, 104…Invitation processing unit, 105…Prediction unit, 106…Purchase processing unit, 107…Accounts collection entrustment processing unit, 108…Collection processing unit, 109…Calculation unit, 110…Storage unit, 200…Reservation system, 202…Communication unit, 203…Acquisition unit, 205…Invoice processing unit, 206…Creation unit, 210…Storage unit
Claims
1. An acquisition unit that obtains on-site payment information from a reservation system for booking a facility or store, An invitation processing unit performs the process of inviting a client to an accounts receivable purchase service that purchases the future accounts receivable of a client operating a facility or store, based on the local settlement information acquired by the acquisition unit, A receivables purchase system equipped with the necessary features.
2. The accounts receivable purchase system according to claim 1, wherein the invitation processing unit performs a process of inviting a client to the accounts receivable purchase service based on the client identification information of the client operating the facility or store where the local payment was made, as included in the local payment information.
3. If the aforementioned client accepts the invitation, the forecasting unit predicts the client's future accounts receivable based on the local settlement information acquired by the acquisition unit, Based on the future accounts receivable predicted by the forecasting unit, a purchase processing unit performs the process of purchasing the client's accounts receivable, The accounts receivable purchase system according to claim 1, further comprising the features described above.
4. The acquisition unit further acquires prepayment information from the reservation system, The accounts receivable purchase system according to claim 3, wherein the prediction unit further predicts the client's future accounts receivable based on the pre-settlement information acquired by the acquisition unit.
5. A collection processing unit performs the process of collecting the accounts receivable from the aforementioned client. The accounts receivable purchase system according to claim 1, further comprising the features described above.
6. Obtain on-site payment information from the reservation system used to book a facility or store. Based on the acquired local settlement information, the system performs a process to invite the client to a accounts receivable purchase service that purchases the future accounts receivable of the client operating the facility or store. A computer-based method for purchasing accounts receivable.
7. On the computer, The system for booking a facility or store retrieves on-site payment information. Based on the acquired local settlement information, the system will initiate a process to invite the client to a receivables purchase service that purchases the future receivables of the client operating the facility or store. program.
Citation Information
Patent Citations
Information processing device, information processing method, and information processing program
JP7198956B1