Funding systems and programs

Abstract

This allows for the effective and flexible use of each store's funding framework in providing funds for future sales, thereby improving convenience for users. [Solution] The funding system comprises a reception unit that receives funding applications from businesses operating business entities, and a sales selection unit that selects, based on a selection operation by the business entity, whether to provide funding based on a first sales forecast based on the business entity's first sales or a second sales forecast based on the business entity's second sales.

Description

Technical Field

[0001] The present invention relates to a funding system and a program.

Background Art

[0002] Conventionally, a system for providing funds based on the predicted sales value of a store or the like has been proposed (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] In such a funding system, it is preferable that the funding limit for each store can be utilized effectively and flexibly.

[0005] An object of the present invention is to provide a funding system and a program that can effectively and flexibly utilize the funding limit for each store in providing funds for the future sales of a store, and can improve the convenience for users.

Means for Solving the Problems

[0006] (1) One aspect of the present invention is a funding system including a reception unit that receives an application for funding from an operator who manages an enterprise, and a sales selection unit that selects whether to provide funding based on either a first sales prediction based on the first sales of the enterprise or a second sales prediction based on the second sales of the enterprise, based on a selection operation by the operator. (2) One aspect of the present invention is a funding system described in (1) above, further comprising a proposal unit that proposes to the business operator an amount of funding calculated based on the first sales forecast and an amount of funding calculated based on the second sales forecast. (3) In one aspect of the present invention, in the funding system described in (1) above, the first sales are sales made by cashless payment, and the second sales are sales made by cashless payment and sales made by cash payment. (4) One aspect of the present invention is a program for a computer to perform the following actions: receive an application for funding from a business operator operating a business entity; and select, based on a selection operation by the business operator, whether to provide funding on a first sales forecast based on the business entity's first sales or a second sales forecast based on the business entity's second sales. [Effects of the Invention]

[0007] According to the present invention, when providing funds for the future sales of stores, the funding limits for each store can be used effectively and flexibly, thereby improving convenience for users. [Brief explanation of the drawing]

[0008] [Figure 1] This figure shows an example of a funding scheme for a funding system according to an embodiment of the present invention. [Figure 2] This figure shows an example of a fund recovery scheme for a fund provision system according to an embodiment of the present invention. [Figure 3] This figure shows an example of the device configuration of a funding system according to an embodiment of the present invention. [Figure 4] This figure shows an example of the functional configuration of a fund provision management device according to an embodiment of the present invention. [Figure 5] This figure shows an example of the operation flow (part 1 and part 2) of a funding system according to an embodiment of the present invention. [Figure 6] This figure shows an example of funding framework information according to an embodiment of the present invention. [Figure 7] It is a diagram showing an example of a fund - providing condition input screen according to an embodiment of the present invention. [Figure 8] It is a diagram showing an example of an application content display screen according to an embodiment of the present invention. [Figure 9] It is a diagram showing an example of a deposit account candidate screen according to an embodiment of the present invention. [Figure 10] It is a diagram showing an example of an application completion screen according to an embodiment of the present invention. [Figure 11] It is a diagram showing an example of an examination status display screen according to an embodiment of the present invention. [Figure 12] It is a diagram showing an example of the flow of the operation of a fund - providing system (Part 3) according to an embodiment of the present invention. [Figure 13] It is a diagram showing an example of a deposit information display screen according to an embodiment of the present invention. [Figure 14] It is a diagram showing an example of the flow of the operation of a fund - providing system (Part 4) according to an embodiment of the present invention. [Figure 15] It is a diagram showing an example of a debit confirmation screen according to an embodiment of the present invention. [Figure 16] It is a diagram showing an example of a claim confirmation screen according to an embodiment of the present invention. [Figure 17] It is a diagram showing an example of the correspondence relationship between the deposit amount and the debit amount in a fund - providing contract according to an embodiment of the present invention. [Figure 18] It is a diagram showing an example of a debit completion screen according to an embodiment of the present invention. [Figure 19] It is a diagram showing an example of a payment completion screen according to an embodiment of the present invention.

Embodiments for Carrying Out the Invention

[0009] Hereinafter, embodiments of the present invention will be described in detail 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 following embodiments. In all the drawings for explaining the embodiments, those having the same function are denoted by the same reference numerals, and repeated explanations are omitted. In addition, as used in this application, "based on XX" means "at least based on XX", and includes cases where it is based on another element in addition to XX. Also, "based on XX" is not limited to the case of directly using XX, and includes cases where it is based on something obtained by performing operations or processing on XX. "XX" is an arbitrary element (for example, arbitrary information).

[0010] (Embodiment) The funding system 1 according to this embodiment provides funds to the business operator CL1 and recovers the provided funds. Specifically, the funding system 1 provides funds to the business operator CL1 in a lump sum and recovers the provided funds in a divided manner. Hereinafter, the funding scheme and the fund recovery scheme according to this embodiment will be described while referring to FIGS. 1 and 2. The funding system 1 according to this embodiment includes the business operator CL1, the fund provider A1, and the settlement service provider B1. First, each of the business operator CL1, the fund provider A1, and the settlement service provider B1 will be described.

[0011] The funding system 1 of this embodiment provides an amount corresponding to a part of the future sales of a store to the business operator based on the application of the business operator who operates one or more stores. In this embodiment, the business operator is also referred to as a user of the funding service, an applicant for the funding contract, or simply a user or a customer.

[0012] In this embodiment, the store broadly includes an organization for which future sales can be expected. For example, the "store" as used in this embodiment includes, in addition to general merchandise retail stores, accommodation facilities such as inns and hotels, food and beverage providing facilities such as restaurants and izakayas, information providing facilities such as travel, real estate, job hunting, wedding venue introduction, and learning schools, article rental facilities such as car rental and equipment rental, buying and selling facilities for used goods, experience providing facilities such as amusement parks, and the like. Also, the "store" may be a virtual store configured on the network in addition to a so-called physical store.

[0013] Payment service provider B1 provides payment methods, such as online payment services, to its merchant, business CL1. Payment service provider B1 provides electronic payment services, such as QR code payments and electronic money payments. Customers of the businesses operated by business CL1 make payments to business CL1 using electronic payment services such as QR code payments and electronic money payments provided by payment service provider B1. Business CL1 can also receive payments from customers using online payment services without having to process payments at payment terminals installed in the business's stores or facilities, using the payment methods provided by payment service provider B1. For convenience, in this embodiment, payments made by business CL1's customers through payment terminals in stores or facilities are referred to as "offline payments," and payments completed online without using payment terminals are referred to as "online payments." Typical examples of online payments include services that allow payment to be completed when making reservations for travel, beauty salons, restaurants, etc.

[0014] Business operator CL1 may accept payments from customers using multiple payment methods. For example, the revenue of the business operated by business operator CL1 may include both online and offline payment revenue.

[0015] Funder A1 provides funds to business operator CL1. Funder A1 also recovers the funds provided from business operator CL1. Funder A1 determines the amount of funds to provide based on the usage of payment service provider B1. Funder A1 recovers a portion of the sales that business operator CL1 earns using the electronic payment service from payment service provider B1. Specifically, Funder A1 purchases the receivables associated with business operator CL1's sales (business operator CL1's future receivables) and provides (a portion of) the purchased receivables to business operator CL1 as funds. If business operator CL1 operates multiple businesses, Funder A1 may purchase the receivables related to those multiple businesses, and if business operator CL1 supports multiple payment methods, Funder A1 may purchase the receivables corresponding to each of those multiple payment methods.

[0016] Note that Fund provider A1 and payment service provider B1 may be operated by different businesses or by the same business. If fund provider A1 and payment service provider B1 are operated by the same business, fund provider A1 and payment service provider B1 shall be considered the same, and Figures 1 and 2 shall be interpreted as transactions between business CL1 and fund provider A1 (or payment service provider B1).

[0017] [Funding scheme] Figure 1 shows an example of a funding scheme for the funding system according to this embodiment. The funding scheme is carried out in the following steps, for example, (1) to (5). In Figure 1, the cash flow is shown by solid arrows. Note that steps (1) to (5) do not specify the timeline of the processing performed by the funding system 1 according to this embodiment.

[0018] (1) Funder A1 first conducts a preliminary assessment of business operator CL1. Funder A1 inquires with payment service provider B1 about one or more of business operator CL1's past sales or reservations for the business.

[0019] (2) Funder A1 conducts a preliminary assessment of business CL1 by forecasting future sales for a specified period of time based on one or more past sales or reservations for the business. The specified period of time is, for example, two years. The specified period of time may be shorter or longer than two years.

[0020] Based on the preliminary assessment, the maximum amount of funding that can be provided to business operator CL1 is calculated. Specifically, funder A1 predicts the amount of future receivables of business operator CL1 based on the sales performance that business operator CL1 holds from payment service provider B1, and calculates the maximum amount of funding that can be provided. Funder A1 may also simplify the assessment process after receiving a funding application from business operator CL1 by only offering funding to business operator CL1 that meets the screening criteria during the preliminary assessment process.

[0021] (3) Business operator CL1 will bill customer CS1 in the future through its business. Business operator CL1's future receivables are receivables related to sales that business operator CL1 will obtain by billing customer CS1 in the future (future accounts receivable).

[0022] Funder A1 presents candidate funding amounts to business operator CL1 based on the upper limit of funding calculated in the preliminary assessment process in (1).

[0023] (4) Business operator CL1 will notify funder A1 of the amount it wishes to provide within the amount offered. This means that business operator CL1 will sell a portion of its future sales receivables (future receivables) to funder A1. Funder A1 may purchase (a portion of) the future receivables directly from business operator CL1 or from payment service provider B1. The amount of the future receivables to be sold may be the same as the amount of funding provided, or it may be the amount of funding provided plus a fee.

[0024] (5) Fund provider A1 provides funds to business operator CL1 as consideration for future receivables sold by business operator CL1.

[0025] [Fund recovery scheme] Figure 2 shows an example of a fund recovery scheme for the fund provision system according to this embodiment. The fund provision scheme is carried out in the following steps, for example, (1) to (6). In Figure 2, the cash flow is shown by solid arrows. Note that steps (1) to (6) do not specify the timeline of the processing performed by the fund provision system 1 according to this embodiment.

[0026] (1) Funder A1 entrusts business operator CL1 with the collection of future receivables that funder A1 has purchased.

[0027] (2) Business operator CL1 will bill customer CS1 through its business operations. This billing will generate a receivable (accounts receivable) related to sales.

[0028] (3) Payment service provider B1 provides information on the accounts receivable that have been generated to funder A1.

[0029] (4) Fund provider A1 calculates the withdrawal amount. Fund provider A1 calculates the withdrawal amount by determining, for example, the withdrawal rate and the withdrawal frequency (for example, three times a month). The withdrawal rate and withdrawal frequency may be determined between business operator CL1 and fund provider A1.

[0030] (5) Fund provider A1 requests payment of the withdrawal amount from business operator CL1.

[0031] (6) Fund provider A1 will deduct from business operator CL1's sales according to the deduction rate determined at the time of funding. For example, fund provider A1 will receive from business operator CL1's account an amount equal to the sales of business operator CL1 multiplied by the deduction rate determined at the time of funding. At this time, fund provider A1 may also collect an amount equivalent to a commission in addition to the above amount from business operator CL1's account.

[0032] Furthermore, steps (5) and (6) in the fund recovery scheme are repeated based on the withdrawal frequency (e.g., three times a month) determined at the time of fund provision. The fund recovery scheme process ends when business operator CL1 has paid fund provider A1 the amount received plus a fee.

[0033] [Configuration of the funding system] Figure 3 shows an example of the device configuration of the fund provision system 1 of this embodiment. The fund provision system 1 comprises a user terminal device 10, a fund provision management device 20, and a user information server 30.

[0034] The user terminal device 10 is a computer device such as a personal computer, tablet, or smartphone. The user terminal device 10 includes a display unit 11 and an operation unit 12. The display unit 11, for example, is equipped with a liquid crystal display and displays various images. In the following description, the display of an image by the display unit 11 is also referred to as presenting an image to the user. The control unit 12, for example, is equipped with a touch panel and detects user operations.

[0035] The user terminal device 10 includes an arithmetic unit 100 and a storage unit 150. The arithmetic unit 100 includes, for example, a central processing unit (CPU), and operates based on programs and data stored in the storage unit 150, providing various functions. The storage unit 150 is composed of, for example, a hard disk drive or semiconductor memory (flash memory, RAM, ROM), and stores various types of information, such as programs and data read by the arithmetic unit 100. The storage unit 150 may also be implemented by a virtual storage device, such as a cloud server, located outside the user terminal device 10.

[0036] The fund management device 20 is a computer device operated by the organization (for example, a funding company) that operates the fund provision system 1.

[0037] The fund provision management device 20 comprises a calculation unit 200 and a storage unit 250. The arithmetic unit 200 includes, for example, a central processing unit (CPU), and operates based on programs and data stored in the storage unit 250, providing various functions.

[0038] Figure 4 shows an example of the functional configuration of the fund provision management device 20 of this embodiment. The calculation unit 200 of this embodiment includes, as its functional units, a reception unit 201, a calculation unit 202, a proposal unit 203, a sales selection unit 204, a payment method selection unit 205, an account selection unit 206, a confirmation unit 207, a fund provision processing unit 208, and a display control unit 209.

[0039] The storage unit 250 is composed of, for example, a hard disk drive or semiconductor memory (flash memory, RAM, ROM), and stores various types of information, such as programs and data read by the arithmetic unit 200. The storage unit 250 may also be implemented by a virtual storage device, such as a cloud server, located outside the fund management device 20.

[0040] Returning to Figure 3, the user terminal device 10 and the fund management device 20 described above can communicate with each other via network NT1. Network NT1 includes the internet, WAN (Wide Area Network), LAN (Local Area Network), public lines, provider equipment, dedicated lines, wireless base stations, etc.

[0041] Furthermore, the user terminal device 10 or the user information server 30 may also have some of the functions of the fund management device 20 described below.

[0042] The user information server 30 is configured, for example, as a cloud server and manages various types of user information.

[0043] In one example of this embodiment, the user utilizes the sales settlement system 2 at the store. For example, the sales settlement system 2 comprises a settlement server 50 and a store terminal device 60. The settlement server 50 and the store terminal device 60 are connected by a network NT2. The store terminal devices 60 are, for example, placed in each store. For example, if a user operates k stores (where k is a natural number), then k store terminal devices 60, from store terminal device 60-1 to store terminal device 60-k, are connected to the sales settlement system 2. In the following description, when the k devices from store terminal device 60-1 to store terminal device 60-k are not distinguished, they are collectively referred to as store terminal devices 60.

[0044] The store terminal device 60 includes devices that have the function of performing cashless payments, devices that have the function of performing cash payments, and devices that have the function of performing both cashless payments and cash payments. The store terminal device 60 may also have a point-of-sale information management function.

[0045] This sales settlement system 2 records, for example, logs of cash deposits for each store (i.e., logs of sales amounts for each store) when the price of goods is paid by cashless payment. Furthermore, the sales settlement system 2 also records, for example, logs of cash deposits for each store (i.e., logs of sales amounts for each store) when the price of goods is paid in cash.

[0046] In the sales settlement system 2 of this embodiment, the transaction account of the financial institution into which the store's sales proceeds are deposited is linked to each store terminal device 60. For example, a store operated by a user may occupy multiple floors of a building, with a store terminal device 60 installed on each floor. In this case, a trading account is linked to each store terminal device 60 installed on each floor, i.e., each floor. Furthermore, a user may operate multiple types of businesses, such as restaurants, retail stores, and service providers like hotels and beauty salons. In this case, a separate transaction account is linked to each store terminal device 60 installed in each store, i.e., each store individually.

[0047] In this embodiment, the transaction accounts linked to each store, the store terminal devices 60 (payment terminals) installed at each store, and the payment accounts linked to the payment terminals are collectively referred to as payment methods. These payment methods are linked to identification information that identifies the user (for example, the user ID of sales settlement system 2). In other words, in this embodiment, multiple payment methods are linked to identification information that identifies the user.

[0048] Funding system 1 can communicate with sales settlement system 2 via network NT3. The user information server 30 of funding system 1 acquires logs recorded by sales settlement system 2. These logs contain information on the sales amount for each user's store terminal device 60 (i.e., payment terminal). In the following description, the information on the sales amount for each user's store will also be simply referred to as "sales information".

[0049] The funding system 1 of this embodiment provides funds to users, collects funds from users, and collects fees in the following four stages. (i) Setting of funding framework (b) Acceptance and review of applications for funding (h) Provision of funds (ii) Deduction from sales proceeds

[0050] The funding system 1 of this embodiment can simultaneously enter into multiple funding agreements C for the sales of a single business entity (for example, a store). Hereinafter, a business entity may be referred to as a "facility" or a "store." In other words, "facility" and "store" are examples of business entities.

[0051] [Operation Flow of Funding System 1] Figure 5 shows an example of the operation flow (part 1 and part 2) of the funding system 1 of this embodiment.

[0052] [(i) Setting of funding framework] Step S311: The user information server 30 provides sales information to the fund provision management device 20. Step S211: The fund provision management device 20 obtains sales information from the user information server 30. Step S212: The fund management device 20 calculates the fund allocation limit FL based on sales information. The fund management device 20 uses a predetermined algorithm to make future sales forecasts for each store based on the user's store-specific sales information (i.e., past sales performance). The fund management device 20 calculates the fund allocation limit FL for each store based on the sales forecast results. The fund management device 20 stores the calculated fund allocation limit FL as fund allocation limit information 301 in the storage unit 250.

[0053] In the following explanation, the upper limit of the FL (Funding Limit) for a particular store is also referred to as the store-specific upper limit FL1. In other words, the fund management device 20 calculates the store-specific upper limit FL1 based on sales information.

[0054] Here, the sales information includes sales categorized by sales type. In this embodiment, there are two types of sales: first sales and second sales. First sales are sales made solely through cashless payments. Second sales are sales that combine cashless payments and cash payments.

[0055] The fund management device 20 calculates a fund allocation limit FL2 based solely on sales made via cashless payment, and a fund allocation limit FL3 based on both sales made via cashless payment and sales made via cash payment, respectively, when the sales information includes a second sales transaction. The fund management device 20 calculates a fund allocation limit FL based solely on sales made via cashless payment, when the sales information includes a first sales transaction. The fund management device 20 calculates a fund allocation limit FL based solely on sales made via cash payment, when the sales information includes sales made via cash payment. In the following explanation, either the per-store maximum fund allocation limit FL2 or the per-store maximum fund allocation limit FL3 may be simply referred to as the per-store maximum fund allocation limit FL1.

[0056] Figure 6 shows an example of the funding limit information 301 in this embodiment. The funding limit information 301 stores the user ID, store ID, account ID, and store-specific maximum funding limit FL1 (store-specific maximum funding limit FL2, or store-specific maximum funding limit FL3), which are associated with each store.

[0057] A user ID is information that identifies an individual user. For example, a user ID is information associated with the login name for funding system 1. User ID:U001 is the user ID that identifies the first user. User ID:Un(n is a natural number) is the user ID that identifies the nth user (i.e., the nth user).

[0058] A store ID is information that identifies an individual store. Store ID: SP101 is the store ID that identifies the first store for the first user. Store ID: SPnm (where m is a natural number) is the store ID that identifies the m-th store for the n-th user (i.e., the m-th store).

[0059] An account ID is information that identifies the deposit account for the funds being provided. In the fund provision system 1 of this embodiment, each deposit account is associated with a store terminal device 60 (i.e., a payment terminal).

[0060] In one example of this embodiment, the user operates multiple business entities. In this case, the identification information that identifies each of the multiple business entities is linked to the user ID (identification information) that identifies the user. Each of these multiple entities is linked to a specific deposit account. In other words, the account ID is information that identifies the deposit account linked to each of these multiple entities. Furthermore, the deposit account and the trading account may be the same account. In this case, the account ID serves as both the information identifying the deposit account and the information identifying the trading account.

[0061] As an example of this embodiment, the per-store maximum funding limit FL2 for cashless payments only at store ID: SP101 (i.e., the first store of the first user) is per-store maximum funding limit FL2-101 (300,000 yen). Note that the amount of the per-store maximum funding limit FL2 is merely an example. The maximum fund allocation limit FL2 for store ID: SP102 (i.e., the first user's second store) is FL2-102 (200,000 yen). The maximum fund allocation limit FL2 for store ID: SP103 (i.e., the first user's third store) is FL2-103 (200,000 yen). Similarly, the per-store maximum funding limit FL2 for the store with store ID:SPnm (i.e., the mth store of the nth user) is per-store maximum funding limit FL2-nm.

[0062] As an example of this embodiment, the store-specific maximum funding limit FL3 for store ID: SP101 (i.e., the first store of the first user), which combines cashless payments and cash payments, is FL3-101 (600,000 yen). Note that the amount of the store-specific maximum funding limit FL3 is merely an example. The maximum fund allocation limit FL3 for store ID: SP102 (i.e., the first user's second store) is FL3-102 (300,000 yen). The maximum fund allocation limit FL3 for store ID: SP103 (i.e., the first user's third store) is FL3-103 (200,000 yen). Similarly, the per-store maximum funding limit FL3 for the store with store ID:SPnm (i.e., the mth store of the nth user) is per-store maximum funding limit FL3-nm.

[0063] As mentioned above, the per-store maximum funding limit FL1 (per-store maximum funding limit FL2, or per-store maximum funding limit FL3) is set based on the sales information of each store. Sales figures may differ between stores operated by the same user. As a result, even between stores operated by the same user, the per-store maximum funding limit FL1 (per-store maximum funding limit FL2, or per-store maximum funding limit FL3) may have different values. For example, the per-store maximum funding limit FL3 for store ID: SP201 (i.e., the second user's first store), which combines cashless payments and cash payments, is per-store maximum funding limit FL3 - 201 (500,000 yen). The per-store maximum funding limit FL3 for store ID: SP202 (i.e., the second user's second store) is per-store maximum funding limit FL3 - 202 (400,000 yen).

[0064] Furthermore, store sales may fluctuate depending on the type of store, season, weather, economic conditions, and the surrounding environment of the location. The fund provision management device 20 may be configured to update the store-specific maximum fund provision limit FL1 by reacquiring store sales at predetermined timings.

[0065] In addition to the example above, the timing for updating the store-specific maximum funding limit FL1 may also be configured to be calculated each time a user applies for funding, based on sales information for a period prior to that point.

[0066] Here, the fund provision management device 20 of this embodiment includes a calculation unit 202. This calculation unit 202 calculates a combined fund provision limit, i.e., a combined upper limit fund provision limit FL1A, which is the sum of the fund provision limits predetermined for each of several business entities. The combined upper limit fund provision limit FL1A for cashless payments only is referred to as the combined upper limit fund provision limit FL2A. The combined upper limit fund provision limit FL1A for cashless payments and cash settlements combined is referred to as the combined upper limit fund provision limit FL3A. In the following description, either the combined upper limit fund provision limit FL2A or the combined upper limit fund provision limit FL3A may be simply referred to as the combined upper limit fund provision limit FL1A.

[0067] In the example shown in Figure 6, the first user (User ID: U001) operates three stores: the first store (Store ID: SP101), the second store (Store ID: SP102), and the third store (Store ID: SP103). The maximum funding limit FL2 for each store is 300,000 yen for the first store, 200,000 yen for the second store, and 200,000 yen for the third store. In this case, the combined maximum funding limit FL2A, which is the sum of the maximum funding limits FL2 for the stores operated by the first user (i.e., the stores linked to the first user's User ID: U001), is 700,000 yen. In this example, the calculation unit 202 calculates the combined limit, assuming that the combined maximum funding limit FL2A for the first user (user ID: U001) is 700,000 yen. The same applies to the combined maximum funding limit FL3A.

[0068] [(b) Acceptance and review of applications for funding] Step S121: Returning to Figure 5, the user operates the user terminal device 10 to apply for funding. The user terminal device 10 notifies the funding management device 20 that the user has applied for funding.

[0069] Step S221: The receiving unit 201 of the fund provision management device 20 receives a fund provision application from a user. As described above, the user ID (identification information) of a user is linked to multiple business entities (for example, store IDs).

[0070] In other words, the reception unit 201 accepts applications for funding from users who possess identification information linked to multiple business entities.

[0071] In other words, reception desk 201 accepts applications for funding from businesses operating as entities.

[0072] Step S222: The fund provision management device 20 notifies the user terminal device 10 of the combined limit calculated in step S212 (i.e., the combined upper limit fund provision limit FL2A and the combined upper limit fund provision limit FL3A).

[0073] The proposal unit 203 of the fund provision management device 20 makes a fund provision proposal to the user based on the calculated combined limit (i.e., the combined upper limit fund provision limit FL2A and the combined upper limit fund provision limit FL3A). The fund provision proposal includes, for example, displaying the fund provision condition input screen P1 on the display unit 11 of the user terminal device 10.

[0074] Step S122: The user terminal device 10 receives the combined maximum fund provision limit FL2A and the combined maximum fund provision limit FL3A from the fund provision management device 20. The user terminal device 10 displays the fund provision condition input screen P1, which includes the received combined maximum fund provision limit FL2A and the combined maximum fund provision limit FL3A, on the display unit 11.

[0075] Figure 7 shows an example of the funding conditions input screen P1 of this embodiment. The funding conditions input screen P1 includes a store combined funding conditions display field P11, a usage amount selection field P12, a withdrawal rate selection field P13, a sales type selection field P14, a payment method selection field P15, and an application button P16.

[0076] The Store-Combined Funding Conditions Display Section P11 shows the funding conditions when funding is provided based on the user's current selections in the Funding Amount Selection Section P12 and the Withdrawal Rate Selection Section P13. The funding conditions include the amount of fees associated with the funding, and the simulation results of the withdrawal amount and timing.

[0077] For example, the combined store funding conditions display field P11 shows the combined upper limit funding amount FL1A (for example, 700,000 yen) calculated in step S212.

[0078] When a user changes their selection in the usage amount selection field P12 or the withdrawal rate selection field P13, the display content in the store combined funding conditions display field P11 is immediately updated to reflect the changes. In the example in Figure 7, the store combined funding conditions display field P11 shows the funding conditions when the usage amount is set to "700,000 yen" and the withdrawal rate is set to "25%".

[0079] In this embodiment, "withdrawal" refers to the process where, when the sales proceeds from the store are deposited into the user's account from the sales settlement system 2 contracted by the user, the organization operating the fund provision system 1 deducts a portion of the deposited amount as a fee for providing the funds. Here, the fee for providing the funds includes the amount recovered from the funds provided and a fee for providing the funds. In other words, the amount deposited into the user's deposit account is the amount after the withdrawal (i.e., the amount after the amount recovered from the funds and the fee have been deducted) of the sales proceeds from the store.

[0080] The P12 section for selecting the amount to be used presents options for the amount of funding to be received (i.e., the amount to be used). In the example shown in the diagram, four options are presented: 50,000 yen, 200,000 yen, 350,000 yen, and 700,000 yen.

[0081] The receiving unit 201 of the fund provision management device 20 accepts an amount selected from among several candidate amounts as the fund provision amount.

[0082] The spending amount selection field on page 12 should always display the maximum amount available at that time. If the user does not select the maximum amount, the difference between the maximum amount and the amount selected by the user will be considered the "unused amount."

[0083] In addition, depending on the type and number of stores operated by the user, the combined maximum funding limit FL1A may be excessive. In this case, the proposal unit 203 may propose funding using the lesser of the combined maximum funding limit FL1A calculated by the calculation unit 202 and the predetermined maximum funding limit as the maximum funding amount.

[0084] In other words, the proposal unit 203 may be configured to make proposals for funding based on a combined limit (for example, a combined upper limit funding limit FL1A) and a predetermined upper limit for funding. With the fund provision management device 20 configured in this way, when the fund provision limits for multiple business entities are combined, the risk of the fund provision amount becoming excessive and the withdrawal not being carried out smoothly can be reduced.

[0085] The fund provision management device 20 calculates the available amounts based on the unused portion of the combined maximum fund provision limit FL1A. For example, if the unused portion of the combined maximum fund provision limit FL1A is 700,000 yen, the available options will be the unused amount (700,000 yen), half the unused amount (350,000 yen), the minimum amount to be used (50,000 yen), and the median between half the amount and the minimum amount (200,000 yen).

[0086] Furthermore, the minimum amount to be used may vary based on the amount of unused funds within the combined maximum funding limit FL1A. For example, if the unused amount is less than a predetermined value (e.g., 200,000 yen), the funding management device 20 may calculate the minimum amount as 10,000 yen. For example, if the unused amount is 200,000 yen, the funding management device 20 may calculate the options as follows: the unused amount (200,000 yen), half of the unused amount (100,000 yen), the minimum amount (10,000 yen), and the median between half the amount and the minimum amount (45,000 yen, or rounded up to 50,000 yen). Generally, stores tend to want to provide as much funding as possible. Therefore, it is assumed that it would be more advantageous for users to offer a somewhat lump sum as an option for the amount to be used, including the maximum amount of funds available at that time. In other words, it is desirable to offer relatively high spending options to stores with a high combined spending limit (FL1A), and conversely, it is desirable to offer relatively low spending options to stores with a low combined spending limit (FL1A).

[0087] Additionally, it may be possible to set a minimum unit for the amount to be used. For example, if the minimum unit is set to 10,000 yen, it is not possible to set the amount to be used in units of 1,000 yen or less. The fund provision management device 20 calculates options to present as many choices as possible, but if the combined upper limit fund provision amount FL1A is small, there may be fewer than four options that can be presented to the user. For example, if the upper limit fund provision amount is only 30,000 yen, only three options can be presented: "10,000 yen," "20,000 yen," and "30,000 yen."

[0088] The withdrawal rate selection field P13 is a field that presents options for the withdrawal rate. In this embodiment, the "withdrawal rate" is the percentage deducted from the store's sales amount as funding costs. In other words, the "withdrawal rate" is a value represented by (funding costs / store's sales amount). For example, if the withdrawal rate is 25%, the funding costs are an amount equivalent to 25% of the store's sales amount.

[0089] In the example shown in the figure, the fund management device 20 displays two options for the withdrawal rate: "25%" and "70%". The withdrawal rate options can be arbitrarily set by the fund provider, or the withdrawal rate options can be calculated each time based on the expected sales of the store, which are estimated based on past sales information. For example, the fund management device 20 calculates the withdrawal rate at which the maximum amount of the amount of use (e.g., 700,000 yen) presented in the amount of use selection field P12 will be withdrawn within a predetermined period (e.g., 3 months) as the first option (e.g., 70%). The fund management device 20 also calculates the withdrawal rate at which the maximum amount of the amount of use (e.g., 700,000 yen) presented in the amount of use selection field P12 will be withdrawn within a predetermined period longer than the above period (e.g., 12 months) as the second option (e.g., 25%).

[0090] If the withdrawal rate is high, a large portion of the sales amount will be deducted to recover the funds received, which carries the risk of significantly reducing the amount deposited into the store's account as sales. On the other hand, there is the advantage of being able to reduce the fees associated with providing funds, so for stores with a certain level of business stability, choosing a high withdrawal rate can be very beneficial. Conversely, for stores that are not yet financially stable, or when using the service during off-season periods when sales are low, choosing a low withdrawal rate to secure the amount of sales deposited (although this will result in a longer withdrawal period and thus a higher total amount of fees) can be very beneficial.

[0091] The Sales Type Selection field P14 is a field that presents options for the sales type (First Sales or Second Sales). Either First Sales or Second Sales is selected as the sales type. In the illustrated example, First Sales (Sales by cashless payment only) is selected as the sales type in the Sales Type Selection field P14. The Sales Type Selection field P14 contains the Sales Type Selection Form P141. The Sales Type Selection Form P141 is an interactive image that accepts the user's operation to select a sales type. The Sales Type Selection Form P141 is, as an example, a pull-down menu.

[0092] The sales selection unit 204 selects, based on the business operator's selection operation, whether to provide funding based on a first sales forecast based on the business entity's first sales (for example, sales from cashless payments) or a second sales forecast based on the business entity's second sales (for example, both sales from cashless payments and sales from cash payments).

[0093] Sales from cashless payments are smaller than sales from both cashless and cash payments combined. Businesses can set smaller funding limits by choosing to provide funding based on sales forecasts (first sales forecast) derived from cashless payments (first sales). Therefore, businesses can easily adjust the size of their funding limits.

[0094] In the aforementioned store combined funding conditions display field P11, if "1st Sales" is selected in the sales type selection field P14, the amount of funding calculated based on the 1st Sales forecast will be displayed. On the other hand, in the store combined funding conditions display field P11, if "2nd Sales" is selected in the sales type selection field P14, the amount of funding calculated based on the 2nd Sales forecast will be displayed.

[0095] In other words, the proposal unit 203 proposes to the business operator the amount of funding calculated based on the first sales forecast and the amount of funding calculated based on the second sales forecast. This configuration allows the business operator to review the amount of funding and then choose whether to apply for funding based on the first or second sales forecast. Therefore, it improves convenience for the business operator. The screen for selecting the sales type may be displayed before the funding conditions input screen P1 is shown. In that case, the business operator will first select the sales type, and then confirm the funding amount on the funding conditions input screen P1.

[0096] Note that the sales type selection field P14 is displayed when both cashless payment and cash payment are accepted in the sales settlement system 2. The sales type selection field P14 is not displayed when only one of cashless payment or cash payment is accepted in the sales settlement system 2.

[0097] The payment method selection field P15 is a field that presents options for payment methods (invoice or payment from cashless sales). Either invoice or payment from cashless sales can be selected as the payment method. In the illustrated example, payment from cashless sales is selected as the payment method in the payment method selection field P15. The payment method selection field P15 includes the payment method selection form P151. The payment method selection form P151 is an interactive image that accepts the user's input to select a payment method. The payment method selection form P151 is, in example, a pull-down menu.

[0098] Note that the sales type selection form P141 and the payment method selection form P151 may be forms other than pull-down menus. The sales type selection form P141 and the payment method selection form P151 may also be radio buttons. Furthermore, when either the sales type selection form P141 or the payment method selection form P151 is selected, a pop-up may be displayed to allow the user to perform the selection operation.

[0099] The payment method selection unit 205 selects, based on the business operator's selection operation, whether to recover the funds provided to the business operator using the first recovery method or the second recovery method.

[0100] In this embodiment, the first collection method is collection via invoice. The second collection method is collection from sales managed by the settlement server 50. As will be explained later, in the case of payments from cashless sales, the amount collected by the funder is deducted from the payment service provider's account before the funds are deposited into the business's account on the specified date. Some businesses may find it more convenient to have the funds automatically deducted. On the other hand, some businesses may find it more convenient to receive an invoice and make the payment themselves rather than having the funds automatically deducted.

[0101] The application button P16 is an operation image that accepts the user's operation to confirm the funding conditions (amount to be used and withdrawal rate) and submit the application. When the display control unit 209 detects the user's operation on the application button P16, it displays the application details screen P2 on the display unit 11 of the user terminal device 10.

[0102] Figure 8 shows an example of the application details display screen P2 of this embodiment. The application details display screen P2 is a screen that displays the user's application for funding. The application details display screen P2 includes a total withdrawal amount display field P21, a deposit account selection field P22, a withdrawal schedule display field P23, and an application confirmation operation button P24.

[0103] The withdrawal amount display field P21 shows the total withdrawal amount. The withdrawal amount includes the amount of funds provided (i.e., the amount used) and the fees for providing the funds. The withdrawal amount display field P21 shows the total withdrawal amount and its breakdown (i.e., the amount used and the fees). In addition, the selected sales type and payment method are displayed in the withdrawal amount display field P21.

[0104] The deposit account selection field P22 is where users select a deposit account. Selecting a deposit account means choosing which of the deposit accounts linked to the user's store will receive the funds.

[0105] When the deposit account selection field P22 is operated, the display control unit 209 displays the deposit account candidate screen P221 on the display unit 11 of the user terminal device 10.

[0106] Figure 9 shows an example of the deposit account candidate screen P221 of this embodiment. The deposit account candidate screen P221 displays deposit accounts (i.e., deposit accounts for each store) based on the account ID of each store linked to the user ID. In this example of the embodiment, the deposit account candidate screen P221 displays a field showing the deposit account of the first store (first deposit account field P2211), a field showing the deposit account of the second store (second deposit account field P2212), and a field showing the deposit account of the third store (third deposit account field P2213).

[0107] The user selects the deposit account from the list of deposit accounts displayed on the deposit account candidate screen P221 to receive the funds (i.e., the account to which the funds will be deposited).

[0108] The account selection unit 206 selects the deposit account specified by the user from among the candidate deposit accounts for the fund recipient displayed on the application confirmation screen, and uses that as the deposit account for the fund recipient.

[0109] Returning to Figure 8, the withdrawal schedule display section P23 shows the dates on which withdrawals will be made. The start date of withdrawals, the end date of withdrawals, the withdrawal rate, the initial withdrawal amount, and the scheduled date of the initial withdrawal are displayed. The figure shows an example of the display when there are no other funding contracts C in place.

[0110] This example shows that the first withdrawal occurs after a specified period has elapsed from the date of application for funding. The specified period may be defined in funding agreement C. For example, funding agreement C stipulates that the specified period is 12 business days from the day following the date of application for funding. In this example, it shows that the first withdrawal occurs 12 business days after the day following the date of application for funding.

[0111] As described above, a direct debit refers to the process in the sales settlement system 2 where a fund provider deducts an amount corresponding to the amount of funds they have provided from the sales of a business entity (e.g., a store) operated by the user. The user's trading account will then receive the remaining amount after the amount corresponding to the fund provider has been deducted from the sales of the business entity (e.g., a store). The display control unit 209 displays the withdrawal schedule in the withdrawal schedule display field P23.

[0112] Furthermore, as shown in the figure, the display control unit 209 displays the withdrawal schedule in a calendar format showing the dates for each day of the week. The display control unit 209 can display various formats of withdrawal schedules in the withdrawal schedule display field P23.

[0113] The display control unit 209 may be configured to display the withdrawal schedule display field P23 based on user operations. For example, the display control unit 209 may not display the withdrawal schedule display field P23 on the initial screen of the application details display screen P2, but may display the withdrawal schedule display field P23 (for example, by displaying it as a pop-up) when the user performs a predetermined operation.

[0114] Returning to Figure 8, the application confirmation button P24 is an image of the operation performed by the user when confirming the application for funding. The application confirmation button P24 is performed by the user when the user accepts the contents shown on the application details display screen P2.

[0115] Step S123: When the user terminal device 10 detects a user action on the application confirmation button P24, it displays the application completion screen P3.

[0116] Figure 10 shows an example of the application completion screen P3 of this embodiment. The application completion screen P3 includes an application completion display field P31, a next application selection button P32, and a close button P33.

[0117] The application completion display section P31 is where information indicating that the funding application process has been completed is displayed. The "Next Application Selection" button (P32) is an image showing the operation performed when submitting another funding application. The close button P33 is an operation image used when you want to end the application process without submitting any other funding applications.

[0118] Furthermore, when the user terminal device 10 receives an operation from the user to accept the contents shown on the application details display screen P2, it transmits information to the fund provision management device 20 indicating that the fund provision conditions have been finalized.

[0119] Step S223: The receiving unit 201 of the fund provision management device 20 receives the application for fund provision. Specifically, the receiving unit 201 receives information transmitted from the user terminal device 10 in step S123 indicating that the fund provision conditions have been finalized.

[0120] The confirmation unit 207 confirms the application based on the application operation on the confirmation screen.

[0121] When the funding management device 20 accepts a funding application, the user terminal device 10 displays the application status screen P4 on the display unit 11.

[0122] Figure 11 shows an example of the review status display screen P4 of this embodiment. The review status display screen P4 includes an application details display field P41 and a status display field P42. The application details display field P41 is a field that shows the details of the funding conditions applied for. The status display field P42 is a field that shows what stage the review and payment procedures have progressed to.

[0123] [(h) Provision of funds] Figure 12 shows an example of the operation flow (part 3) of the funding system 1 of this embodiment. Step S231: If the funding application is approved, the funding management device 20 processes the deposit to the account specified by the user (for example, the deposit account selected in the deposit account selection field P22). Step S232: The fund management device 20 notifies the user terminal device 10 of the deposit result. Step S131: When the user terminal device 10 receives a notification of the deposit result from the fund management device 20, it displays a screen indicating that a notification of the deposit result has been received (for example, the deposit information display screen P5).

[0124] Figure 13 shows an example of the deposit information display screen P5 of this embodiment. The deposit information display screen P5 includes a deposit status display field P51 and a deposit account display field P52. The deposit status display section P51 shows the name of the store providing the funds, the deposit amount D, and that the transaction has progressed and the deposit has been completed. The deposit account information section on page 52 displays the name of the financial institution, branch name, account number, and other details of the deposit account.

[0125] [(ii) Deduction from sales proceeds] Figure 14 shows an example of the operation flow (part 4) of the funding system 1 of this embodiment. Step S341: The user information server 30 provides the fund management device 20 with sales information from the stores to which funds are provided. Step S241: The fund provision management device 20 obtains sales information from the user information server 30.

[0126] Step S242: The fund management device 20 calculates the amount to be debited in advance before deposit into the store (i.e., debit amount WD) or the amount to be billed on the invoice (i.e., billed amount CH) from the store's sales amount. The debit amount WD or billed amount CH is calculated by multiplying the total sales amount, which is the sum of the sales amounts of multiple stores, by the debit rate described above. For example, if the total sales amount for a predetermined period (e.g., 5 days) is 1 million yen and the debit rate is 25%, then the debit amount WD or billed amount CH for the total sales amount for that period is calculated to be 250,000 yen.

[0127] More specifically, the fund provision processing unit 208 of the fund provision management device 20 obtains the amount of funds provided (i.e., the deposit amount D1) in the fund provision contract C that the user has entered into.

[0128] The calculation unit 202 calculates the recovered amount RA. The recovered amount RA is the sum of the withdrawal amounts WD that have been withdrawn during the withdrawal period of the funding agreement C, or the sum of the invoice amounts CH that have been paid on invoices during the withdrawal period of the funding agreement C. The calculation unit 202 calculates the recovered amount RA according to the selected payment method. In other words, if payment from cashless sales is selected as the payment method, the calculation unit 202 calculates the recovered amount RA as the sum of the withdrawal amounts WD that have been withdrawn during the withdrawal period of the funding agreement C. If invoices are selected as the payment method, the calculation unit 202 calculates the recovered amount RA as the sum of the invoice amounts CH that have been paid on invoices during the withdrawal period of the funding agreement C.

[0129] In other words, the funding processing unit 208 obtains the amount of funding based on a combined limit, which is the sum of the funding limits for multiple business entities linked to the identification information that identifies the user. In this context, "business entities" refer to restaurants, beauty salons, retail stores, accommodation facilities, medical facilities, etc. However, as mentioned above, even if it is the same business entity (for example, a store), if multiple payment terminals are installed and different accounts are assigned to each payment terminal, it may be determined that they are "different business entities (for example, stores)" if the accounts are different. In the case where transaction accounts are linked to each store, as in the example of this embodiment, the fund provision processing unit 208 obtains the fund provision amount based on the combined fund provision limit which is the sum of the fund provision limits for each of the multiple stores operated by the user. The fund provision processing unit 208 obtains the amount deducted from the business entity's sales that corresponds to the amount of funds provided.

[0130] The calculation unit 202 calculates the outstanding balance corresponding to the amount of funds provided, based on the acquired deposit amount D1 and the withdrawn amount RA. For example, the calculation unit 202 calculates (deposit amount D1 - withdrawn amount RA) as the outstanding balance or outstanding amount.

[0131] Step S243: The fund management device 20 notifies the sales settlement system 2 of the amount RA collected. The sales settlement system 2 deposits the amount RA collected from the store's sales into the operator of the fund provision system 1 (for example, the fund provision company), and deposits the remaining balance into the user's designated account on the user terminal device 10.

[0132] In this embodiment, "deposit" may refer to a transfer of money itself, such as a transfer between accounts, or it may refer to a transfer of a right equivalent to money, such as the transfer of monetary claims in cashless payments.

[0133] Step S141: The display control unit 209 of the fund provision management device 20 causes the withdrawal confirmation screen P6 or the billing confirmation screen P6a to be displayed on the display unit 11 of the user terminal device 10.

[0134] If payment from cashless sales is selected as the payment method, the display control unit 209 of the fund provision management device 20 causes the display unit 11 of the user terminal device 10 to display a withdrawal confirmation screen P6 showing the withdrawal amount WD and the remaining withdrawal amount.

[0135] Figure 15 shows an example of the withdrawal confirmation screen P6 of this embodiment. The withdrawal confirmation screen P6 includes the current withdrawal information section P61 and the future withdrawal information section P62. The current withdrawal information section P61 displays the current withdrawal amount WD.

[0136] The upcoming withdrawal information section on page 62 will display the remaining withdrawal amount, the estimated number of remaining withdrawals based on the store's sales performance, and the timing of the withdrawal completion.

[0137] On the other hand, if an invoice is selected as the payment method, the display control unit 209 of the fund provision management device 20 causes the display unit 11 of the user terminal device 10 to display a billing confirmation screen P6a showing the withdrawal amount WD and the remaining withdrawal amount.

[0138] Figure 16 shows an example of the billing confirmation screen P6a of this embodiment. The billing confirmation screen P6a includes the current billing information field P61a and the future billing information field P62a. The current billing information field P61a displays the current billing amount CH.

[0139] The future billing information section on page 62a will display the remaining balance, the estimated number of remaining bills based on the store's sales performance, and the billing completion date.

[0140] The display control unit 209 may also be configured to display the amount debited or the amount billed for each of the multiple business entities, for each business entity.

[0141] Figure 17 shows an example of the correspondence between the deposit amount D and the withdrawal amount WD or billing amount CH in the funding agreement C of this embodiment. In the example shown in the figure, the user of the funding applied for funding in March of a certain year. Based on this application for funding, funding agreement C was concluded. Funding of deposit amount D1 was provided to the combined maximum funding limit FL1A of the user's store. In this example, of the combined maximum funding framework FL1A, the combined funding framework FL11A is an unused funding framework FL.

[0142] Furthermore, the funding agreement C may be made in units of the amount of funding to be provided, or it may be made without specifying an amount, by specifying the "period" for which future receivables will be transferred, for example, "transferring the user's sales (future receivables) for two years from the application date in a lump sum." In the case of a contract that specifies the period for which future receivables will be transferred, if settlement is completed before the end of the period, the future receivables for the remaining period may be returned to the user at the time of settlement completion. As mentioned above, when the transfer period for future receivables is specified in advance, the funder can refer to the sales forecast for the contract period, making it easier to set an upper limit on the amount of funds to be provided within a range that allows for smooth settlement within the contract period.

[0143] In the example shown in the diagram, the withdrawal amount WD or billing amount CH is calculated by multiplying the sales revenue SA for each month from April onward by the withdrawal rate or billing rate specified by the user. The cumulative value of the withdrawal amount WD or billing amount CH up to a certain month is the recovered amount RA. When the withdrawn amount RA matches the deposit amount D1, the withdrawal for the funding agreement C is completed.

[0144] Although I have omitted the explanation to avoid making it complicated, in reality, a "fee" is incurred for funding under this embodiment. In other words, the amount deducted from the sales amount is the amount of funds provided to the user plus the fee. Therefore, to accurately rephrase the above statement regarding the deducted amount RA, the part that says, "When the deducted amount RA matches the deposit amount D1, the deduction for funding agreement C is completed," should be changed to, "When the deducted amount RA matches the total amount of deposit amount D1 + (the fee that the user must pay) the deduction for funding agreement C is completed."

[0145] In this diagram, withdrawals are shown occurring monthly, but the timing and frequency of withdrawals are not limited to this. For example, withdrawals may occur every 5 days (the so-called "five-tenth day") or every 10 days. Furthermore, the timing of withdrawals may differ from one financial institution to another, or from one type of financial institution to another (for example, city banks, regional banks, second-tier regional banks, credit unions, etc.).

[0146] Step S244: Returning to Figure 14, when the fund management device 20 determines that the withdrawal or payment has been completed, it notifies the user terminal device 10 that the withdrawal or payment has been completed. Step S142: The user terminal device 10 displays either the withdrawal completion screen P7 or the payment completion screen P7a on the display unit 11.

[0147] If payment from cashless sales is selected as the payment method, the user terminal device 10 displays the withdrawal completion screen P7 on the display unit 11.

[0148] Figure 18 shows an example of the withdrawal completion screen P7 in this embodiment. The withdrawal completion screen P7 includes information indicating that the withdrawal of the deposit amount D1 based on the funding agreement C has been completed.

[0149] On the other hand, if invoice is selected as the payment method, the user terminal device 10 displays the payment completion screen P7a on the display unit 11.

[0150] Figure 19 shows an example of the payment completion screen P7a in this embodiment. The payment completion screen P7a includes information indicating that the payment of the deposit amount D1 based on the funding agreement C has been completed.

[0151] In this embodiment, an example has been described in which the first sales are sales made by cashless payment and the second sales are the sum of sales made by cashless payment and sales made by cash payment, but this is not the only example. The first sales may be sales made by cashless payment and the second sales may be sales made by cash payment. Another example is that the first sales may be sales made by cash payment and the second sales may be the sum of sales made by cashless payment and sales made by cash payment.

[0152] Furthermore, in this embodiment, an example has been described in which the first collection method is collection by invoice and the second collection method is collection from sales managed by the settlement server 50, but it is not limited to this. The first collection method may be collection by invoice, and the second collection method may be a combination of invoice and collection from sales managed by the settlement server 50. Another example is that the first collection method may be collection from sales managed by the settlement server 50, and the second collection method may be a combination of invoice and collection from sales managed by the settlement server 50.

[0153] Furthermore, one or more of the sales selection unit 204 or the payment method selection unit 205 may be omitted from the configuration of the calculation unit 200.

[0154] As described above, the fund provision system 1 according to this embodiment includes a reception unit 201 and a sales selection unit 204. Reception room 201 accepts applications for funding from businesses operating as entities. The sales selection unit 204 selects, based on a selection operation by the business operator, whether to provide funding based on a first sales forecast based on the business entity's first sales (in this embodiment, sales from cashless payments) or a second sales forecast based on the business entity's second sales (in this embodiment, both sales from cashless payments and sales from cash payments).

[0155] With this configuration, the funding system 1 according to this embodiment allows users to select the size of the funding limit, enabling effective and flexible use of the funding limit for each store, thereby improving convenience for users.

[0156] As described above, the fund provision system 1 according to this embodiment includes a reception unit 201 and a payment method selection unit 205. Reception room 201 accepts applications for funding from businesses operating as entities. The payment method selection unit 205 selects, based on the business operator's selection operation, whether to recover the funds provided to the business operator using a first recovery method (recovery by invoice in this embodiment) or a second recovery method (recovery from sales managed by the settlement server 50 in this embodiment).

[0157] With this configuration, the funding system 1 according to this embodiment allows the user to select the payment method, thereby improving user convenience in terms of payment methods when providing funds for the store's future sales.

[0158] Although embodiments 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 design modifications and the like are also included within the scope of the gist 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.

[0159] 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 networks such as the Internet or communication lines such as telephone lines, which retain programs for a certain period of time.

[0160] 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" used to transmit the program refers to a medium that has the function of transmitting information, such as a network (communication network) like the Internet or a communication line (communication line) like 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]

[0161] 1...Funding System, 201...Reception Department, 204...Sales Selection Department

Claims

1. A reception department that accepts applications for funding from businesses operating as entities, A sales selection unit that selects, based on a selection operation by the business operator, whether to provide funding based on a first sales forecast based on the business entity's first sales or a second sales forecast based on the business entity's second sales, A funding system equipped with these features.

2. The system further includes a proposal unit that proposes to the business operator the amount of funding to be provided calculated based on the first sales forecast and the amount of funding to be provided calculated based on the second sales forecast. The funding system according to claim 1.

3. The first sales mentioned above are sales made through cashless payments, and the second sales mentioned above are sales made through cashless payments and sales made through cash payments. The funding system according to claim 1.

4. On the computer, We accept applications for funding from businesses operating as entities, The choice of whether to provide funding based on the first sales forecast based on the first sales of the said business entity or the second sales forecast based on the second sales of the said business entity is made based on a selection operation by the said business entity. A program to execute.

Images