Funding systems and programs

Abstract

This allows users to check the amount deducted and the balance of payments for receivables purchased for funding purposes, thereby improving user convenience. [Solution] The funding system comprises a reception unit that receives applications for funding from businesses operating business entities, and a display control unit that displays collection information for each claim purchased for the purpose of funding.

Description

Technical Field

[0001] The present invention relates to a fund - providing system and a program.

Background Art

[0002] Conventionally, a system for providing funds based on the predicted sales value of stores and the like has been proposed (for example, Patent Document 1). 10>

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In such a fund - providing system, it is preferable that the user can check the amounts debited as payments for the claims purchased for fund - providing, the balances, and the like.

[0005] An object of the present invention is to provide a fund - providing system and a program that allow a user to check the amounts debited as payments for the claims purchased for fund - providing and the balances, and can improve the convenience for the user.

Means for Solving the Problems

[0006] (1) One aspect of the present invention is a fund - providing system including a reception unit that receives an application for fund - providing from an operator operating a business entity, and a display control unit that displays collection information for each claim purchased for the fund - providing. (2) One aspect of the present invention is the fund - providing system according to (1) above, wherein the display control unit displays the collection information on a dedicated screen of the operator. (3) In one aspect of the present invention, in the fund provision system described in (1) above, the recovery information includes one or more of the following: total amount withdrawn or amount entrusted for recovery, amount to be partially recovered, amount partially recovered, and amount not recovered. (4) One aspect of the present invention is a program for causing a computer to perform the following actions: receiving applications for funding from business operators operating business entities, and displaying collection information for each claim purchased for the purpose of providing said funding. [Effects of the Invention]

[0007] According to the present invention, users can check the amount withdrawn as payment for receivables purchased for funding purposes, as well as the remaining balance, thereby improving convenience for users. [Brief explanation of the drawing]

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

Mode for Carrying Out the Invention

[0009] The fund - providing system 1 of the present 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 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. Also, in the present application, "based on XX" means "based at least on XX", and includes cases where it is based on XX in addition to other elements. 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] Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a diagram showing an example of the device configuration of the fund - providing system 1 of the present embodiment. The fund - providing system 1 includes a user terminal device 10, a fund - providing management device 20, and a user information server 30.

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

[0012] In this embodiment, a store broadly includes an organization with foreseeable future sales. For example, the "store" referred to in this embodiment includes, in addition to general retail stores of goods, 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, item rental facilities such as car rental and equipment rental, buy-and-sell facilities for used items, 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] The user terminal device 10 is a computer device such as a personal computer, a tablet, or a smartphone. The user terminal device 10 includes a display unit 11 and an operation unit 12. The display unit 11 includes, for example, a liquid crystal display and displays various images. In the following description, the display unit 11 displaying an image is also referred to as presenting an image to the user. The operation unit 12 includes, for example, a touch panel and detects the operations of the user.

[0014] 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 the programs and data stored in the storage unit 150 to provide 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.

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

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

[0017] Figure 2 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, an account selection unit 204, a confirmation unit 205, a fund provision processing unit 206, a notification unit 207, and a display control unit 208.

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

[0019] Returning to Figure 1, 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.

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

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

[0022] In one example of this embodiment, the user utilizes a sales settlement system 2 and a service provision system 40 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. This sales settlement system 2 records, for example, a log of cash deposits for each store (i.e., a log of sales amounts for each store) when the price of goods is paid by cashless payment.

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

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

[0025] The service provision system 40 provides services to business entities. The service provision system 40 consists of one or more servers depending on the content of the service. For example, the service provision system 40 consists of a reservation management server 410, an accounting server 420, and an invoice issuance server 430.

[0026] The reservation management server 410 is configured, for example, as a cloud server and provides a website (reservation platform) as a platform for accepting reservations to stores (business entities). The reservation management server 410 generates reservation information. The reservation information shows the history of accepted reservations.

[0027] The accounting server 420 is configured, for example, as a cloud server and manages deposits and withdrawals to and from trading accounts. The accounting server 420 has an application for accounting management. The accounting server 420 may also have an API (Application Programming Interface) provided by a financial institution such as a bank. The accounting server 420 generates deposit and withdrawal information. This information shows the history of deposits into and withdrawals from accounts.

[0028] The invoice issuance server 430 is configured, for example, as a cloud server, and acts on behalf of funders to collect funds and issue invoices to businesses. The invoice issuance server 430 may issue payment requests instead of invoices. The invoice or payment request may be issued as electronic data, or as paper documents or postcards. The invoice issuance server 430 generates invoice information. The invoice information indicates the amount to be billed and the payment due date in the issued invoice.

[0029] The fund provision system 1, sales settlement system 2, reservation management server 410, accounting server 420, and invoice issuance server 430 are all able to communicate with each other via network NT3. The user information server 30 of the fund provision system 1 acquires logs recorded by the 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 simply be referred to as "sales information."

[0030] For example, the fund management device 20 obtains reservation information from the reservation management server 410. The fund management device 20 obtains deposit and withdrawal information for users' trading accounts from the accounting server 420. The fund management device 20 obtains invoice information from the invoice issuance server 430.

[0031] Historical information is provided to the fund management device 20 from one or more servers that make up the service provision system 40. Reservation information, deposit and withdrawal information, and invoice information are examples of historical information. The historical information includes information used for both sales forecasting and calculation of withdrawal amounts, and information used only for calculation of withdrawal amounts. Deposit and withdrawal information and invoice information are used for both sales forecasting and calculation of withdrawal amounts. Reservation information is used only for calculation of withdrawal amounts.

[0032] Furthermore, the fund management device 20 is pre-configured to access user information from each server included in the service provision system 40. This configuration may include, for example, ID linking or data linking. Alternatively, the fund management device 20 may obtain user information from each server included in the service provision system 40 by scraping. Furthermore, if one or more user IDs or passwords are changed on each server included in the service provision system 40, it is preferable that the details of such changes are notified to the fund provision management device 20.

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

[0034] The funding system 1 of this embodiment can simultaneously enter into multiple funding contracts C for the sales of a single business entity (for example, a store). The following explanation will be divided into two cases: one where there are no other funding contracts C in operation, and another where there are other funding contracts C in operation. Furthermore, the business entity may be described as either a "facility" or a "store." In other words, "facility" and "store" are examples of business entities.

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

[0036] [(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.

[0037] Step S411: The service provision system 40 provides historical information to the fund management device 20. For example, the accounting server 420 provides deposit and withdrawal information to the fund management device 20. The invoice issuance server 430 provides invoice information to the fund management device 20.

[0038] Step S212: The fund management device 20 obtains historical information from the service provision system 40. The fund management device 20 obtains deposit and withdrawal information from the accounting server 420. The fund management device 20 obtains invoice information from the invoice issuance server 430.

[0039] Step S213: The fund management device 20 calculates the fund allocation limit FL based on sales information and historical information. The fund allocation limit FL is calculated for each type of receivable. These include receivables collected through sales (accounts receivable), receivables collected through deposits into accounts managed by the accounting server 420, and receivables collected through invoices or payment requests.

[0040] The fund management device 20 uses a predetermined algorithm to forecast future sales for each store based on the user's store-specific sales information (i.e., past sales performance) and historical information (one or more of the following: reservation information, deposit / withdrawal information, and invoice information). Based on the sales forecast results, the fund management device 20 calculates the fund provision limit FL for each store for each type of receivable. The fund management device 20 stores the calculated fund provision limit FL as fund provision limit information 301 in the storage unit 250.

[0041] Furthermore, to calculate the funding limit FL, one or more of the following information is used, depending on the type of receivable: sales information and historical information. In addition, for a single type of receivable, multiple pieces of sales information and historical information (one or more of reservation information, deposit / withdrawal information, and invoice information) may be combined to calculate the funding limit FL. The funding management device 20 does not need to acquire sales information and historical information that are not used to calculate the funding limit FL.

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

[0043] Figure 4 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, which are associated with each store. The funding limit information 301 shown in the figure shows a funding limit for accounts receivable as an example, but funding limits for other types of receivables are similar.

[0044] 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).

[0045] 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).

[0046] 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).

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

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

[0049] As mentioned above, the per-store maximum funding limit FL1 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 may have different values. For example, the per-store maximum funding limit FL1 for store ID: SP201 (i.e., the second user's first store) is per-store maximum funding limit FL1 - 201 (400,000 yen). The per-store maximum funding limit FL1 for store ID: SP202 (i.e., the second user's second store) is per-store maximum funding limit FL1 - 202 (500,000 yen).

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

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

[0052] In this embodiment, the fund provision management device 20 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 predetermined fund provision limits for each of the multiple business entities.

[0053] In the example shown in Figure 4, 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 FL1 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 FL1A, which is the sum of the maximum funding limits FL1 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 FL1A for the first user (user ID: U001) is 700,000 yen.

[0054] [(b) Acceptance and review of applications for funding] Step S121: Returning to Figure 3, 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.

[0055] 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).

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

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

[0058] Step S222: The fund provision management device 20 notifies the user terminal device 10 of the total limit calculated in step S212 (i.e., the total upper limit fund provision limit FL1A).

[0059] The proposal unit 203 of the fund provision management device 20 makes a fund provision proposal to the user based on the calculated total limit (i.e., the total upper limit fund provision limit FL1A). 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.

[0060] Step S122: The user terminal device 10 receives the combined maximum fund provision limit FL1A 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 FL1A, on the display unit 11.

[0061] Figure 5 shows an example of the funding conditions input screen P1 of this embodiment. The funding conditions input screen P1 includes a combined store funding conditions display field P11, a usage amount selection field P12, a withdrawal rate selection field P13, and an application button P14. The funding conditions input screen P1 shown is an example of an input screen for accounts receivable, but the input screens for other types of receivables are similar.

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

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

[0064] 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 5, 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%".

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

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

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

[0068] 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."

[0069] 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).

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

[0071] 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%).

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

[0073] The application button P14 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 208 detects the user's operation on the application button P14, it displays the application details screen P2 on the display unit 11 of the user terminal device 10.

[0074] Figure 6 shows an example of the application details display screen P2 of this embodiment. The application details display screen P2 is a screen that presents the user's application details 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. The illustrated application details display screen P2 shows an input screen for accounts receivable as an example, but input screens for other types of receivables are similar.

[0075] The withdrawal amount display field P21 is where the total withdrawal amount is shown. 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).

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

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

[0078] Figure 7 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).

[0079] 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).

[0080] The account selection unit 204 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.

[0081] Returning to Figure 6, 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.

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

[0083] 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 208 displays the withdrawal schedule in the withdrawal schedule display field P23.

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

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

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

[0087] Figure 8 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.

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

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

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

[0091] The confirmation unit 205 confirms the application based on the application operation on the confirmation screen.

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

[0093] Figure 9 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.

[0094] [(h) Provision of funds] Figure 10 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).

[0095] Therefore, the Funding Processing Unit 206 receives funds by purchasing future sales information of the business entity.

[0096] 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).

[0097] Figure 11 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.

[0098] [(ii) Deduction from sales proceeds] Figure 12 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.

[0099] Step S441: The service provision system 40 provides the fund management device 20 with historical information from the fund recipient store. For example, the reservation management server 410 provides reservation information to the fund management device 20. The accounting server 420 provides deposit and withdrawal information to the fund management device 20. The invoice issuance server 430 provides invoice information to the fund management device 20.

[0100] Step S242: The fund management device 20 obtains history information from the service provision system 40. The fund management device 20 obtains reservation information from the reservation management server 410. The fund management device 20 obtains deposit and withdrawal information from the accounting server 420. The fund management device 20 obtains invoice information from the invoice issuance server 430.

[0101] Step S243: The fund management device 20 calculates the amount to be withdrawn in advance from the store's sales amount before depositing the funds into the store (i.e., the withdrawal amount WD). The withdrawal amount WD is calculated by multiplying the total sales amount, which is the sum of the sales amounts from multiple stores, by the withdrawal rate described above. For example, if the total sales amount for a predetermined period (e.g., 5 days) is 1 million yen and the withdrawal rate is 25%, the withdrawal amount WD for the total sales amount for that period is calculated to be 250,000 yen.

[0102] More specifically, the fund provision processing unit 206 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. The calculation unit 202 calculates the total amount of withdrawals WD that have been withdrawn during the withdrawal period of the funding agreement C (i.e., the withdrawn amount RA). The Funding Processing Unit 206 obtains the total amount of withdrawals WD that have been withdrawn during the withdrawal period of Funding Agreement C (i.e., the withdrawn amount RA).

[0103] In other words, the funding processing unit 206 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 206 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 Funding Processing Unit 206 obtains the amount deducted from the business entity's sales that corresponds to the amount of funds provided.

[0104] 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 the outstanding balance as (deposit amount D1 - withdrawn amount RA).

[0105] The calculation unit 202 calculates the amount collected by the business operator based on sales information, reservation information, deposit and withdrawal information, and invoice information, as the sales amount used in calculating the withdrawal amount WD. In other words, the calculation unit 202 calculates the amount collected by the business operator through the business entity (collected amount) based on sales information and history information, as the sales amount used in calculating the withdrawal amount WD. For example, the calculation unit 202 sets a predetermined percentage of the calculated collected amount as the withdrawal amount WD.

[0106] Therefore, the calculation unit 202 calculates the withdrawal amount WD, which is the payment for the funding, based on the historical information about the service managed by the service provision system 40. Furthermore, the method for calculating the withdrawal amount (WD) from the estimated collection amount based on sales information and historical information is not limited to the method using the predetermined percentage described above.

[0107] Step S244: The fund management device 20 notifies the sales settlement system 2 of the withdrawal amount WD. The sales settlement system 2 deposits the withdrawal amount WD from the store's sales amount to 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.

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

[0109] Step S141: The display control unit 208 of the fund provision management device 20 causes the withdrawal confirmation screen P6, which shows the withdrawal amount WD and the remaining withdrawal amount, to be displayed on the display unit 11 of the user terminal device 10.

[0110] Figure 13 shows an example of the withdrawal confirmation screen P6 of this embodiment. The withdrawal confirmation screen P6 includes the current withdrawal information field P61, the future withdrawal information field P62, and a display button P63. The current withdrawal information field P61 displays the current withdrawal amount WD.

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

[0112] The display button P63 is an operation image that accepts an operation to display collection information. When the display control unit 208 detects a user operation on the display button P63, it displays the collection status details screen P64 on the display unit 11 of the user terminal device 10.

[0113] Figure 14 shows an example of the recovery status details screen P64 of this embodiment. The recovery status details screen P64 is a screen that displays recovery information. The recovery status details screen P64 includes a recovery information display field P641 and a close button P642.

[0114] The collection information display section P641 is a section for displaying collection information. Collection information shows the status of fund collection for each debt. The collection information is stored in association with each type of debt, including the total amount withdrawn or the amount entrusted for collection, the amount to be partially recovered, the amount partially recovered, the outstanding amount, the estimated number of remaining withdrawals, and the estimated end date of withdrawals. The amount entrusted for collection is the total amount entrusted to the business (or collection agency) for debt collection. The amount to be partially recovered is, for example, the amount expected to be recovered this month. The amount partially recovered is, for example, the amount actually recovered this month. The outstanding amount is the remaining balance of the amount entrusted for collection that has not yet been recovered.

[0115] On page 641 of the collection information display section, the following are displayed for each type of debt: "Total amount withdrawn / Collection entrusted amount," "Amount withdrawn this month," "Amount received this month," "Withdrawal balance," "Estimated number of remaining withdrawals," and "Estimated withdrawal end month." "Collection entrusted amount" indicates the total amount to be collected. "Amount withdrawn this month" indicates the amount to be partially collected. "Amount received this month" indicates the amount partially collected. "Withdrawal balance" indicates the amount not yet collected. "Estimated number of remaining withdrawals" indicates the estimated number of remaining withdrawals. "Estimated withdrawal end month" indicates the estimated end date for withdrawals.

[0116] Therefore, the display control unit 208 displays collection information for each claim that has been purchased for funding.

[0117] Note that the predicted number of remaining withdrawals and the predicted end date of withdrawals may be omitted from the collection information. As mentioned above, the collection information includes one or more of the following: total withdrawal amount, amount to be collected, amount to be partially collected, amount to be partially collected, and outstanding amount.

[0118] The detailed collection status screen P64 is described as an example of how it might be displayed when the display button P63 is operated on the withdrawal confirmation screen P6, but it is not limited to this. The detailed collection status screen P64 may also be displayed on the user's dedicated screen (so-called My Page). Therefore, the display control unit 208 displays the collection information on the business operator's dedicated screen (My Page). The user can check the collection information on My Page at their desired time.

[0119] The display control unit 208 may also be configured to display the debited amounts for each of the multiple business entities.

[0120] Furthermore, the withdrawal amount may be notified via the service provision system 40. In that case, the notification unit 207 of the fund provision management device 20 notifies the user of the withdrawal amount, for example, via the reservation management server 410.

[0121] Figure 15 shows an example of the withdrawal amount notification screen P8 of this embodiment. The withdrawal amount notification screen P8 is a screen that displays reservation information managed by the reservation management server 410. The withdrawal amount notification screen P8 includes a management screen display area P81 and a withdrawal amount notification area P82.

[0122] The P81 area of ​​the management screen display is the section that shows the reservation history. The withdrawal amount notification area P82 is a field that displays the withdrawal amount WD calculated by the calculation unit 202 of the fund provision management device 20. The withdrawal amount notification area P82 is displayed on the withdrawal amount notification screen P8 when the notification unit 207 notifies the withdrawal amount.

[0123] The withdrawal amount notification area P82 includes the notification mark P821. The notification mark P821 is displayed, for example, when the withdrawal amount notification screen P8 is displayed for the first time after the withdrawal amount notification has been issued. The notification mark P821 is intended to make the withdrawal amount notification area P82 more prominent. From the time the withdrawal amount notification is issued until the next (next month's) withdrawal amount is calculated, the notification mark P821 will not be displayed on subsequent displays of the withdrawal amount notification screen P8. The notification mark P821 makes it easier for the user to notice that this month's withdrawal amount has been finalized.

[0124] In addition to the notification mark P821, the withdrawal amount notification area P82 may be displayed in any manner in which it is conspicuous. However, the withdrawal amount notification area P82 does not need to be displayed in a conspicuous manner.

[0125] The notification unit 207 may also notify the user of the withdrawal amount on a screen that displays deposit and withdrawal information managed by the accounting server 420. Alternatively, the notification unit 207 may also notify the user of the withdrawal amount on a screen that displays invoice information managed by the invoice issuance server 430.

[0126] Therefore, the notification unit 207 notifies the service provider of the withdrawal amount via the service provision system 40.

[0127] Figure 16 shows an example of the correspondence between the deposit amount D and the withdrawal amount WD in the funding agreement C of this embodiment. In this example, the withdrawal amount WD is the withdrawal amount WD for accounts receivable. The same applies to the withdrawal amount WD for other receivables. In this example, 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 amount D1 was provided to the combined maximum funding limit FL1A of this user's store. In this example, of the combined maximum funding framework FL1A, the combined funding framework FL2A is an unused funding framework FL.

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

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

[0130] For example, a graph showing the relationship between the deposit amount D and the withdrawal amount WD for each receivable may be displayed on the My Page.

[0131] 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."

[0132] 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.).

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

[0134] Figure 17 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.

[0135] Here, we will explain the details of the recovery process by the fund management device 20. Figure 18 shows an example of the operation flow (recovery process) of the fund provision system. The illustrated operation flow includes steps S243, S244, and S245 described above, and more specifically illustrates the recovery process of the fund provision management device 20. The recovery process is repeatedly performed by the fund management device 20 while the fund provision system 1 is in operation.

[0136] Step S10: The fund provision processing unit 206 determines whether the current date is the date of notification of the amount to be recovered. The fund provision processing unit 206 is equipped with a timekeeping function and obtains the current date. The fund provision processing unit 206 makes this determination by comparing the current date with the date of notification of the amount to be recovered. If the fund provision processing unit 206 determines that the current date is the date of notification of the amount to be recovered (Step S10; YES), it executes the process in Step S20. On the other hand, if the fund provision processing unit 206 determines that the current date is not the date of notification of the amount to be recovered (Step S10; NO), it executes the process in Step S60.

[0137] Step S20: The fund provision processing unit 206 identifies the collection contractor. The collection contractor is, for example, a business operator (user) that has received funds from the fund provision management device 20. The fund provision processing unit 206 reads the collection balance management database from the storage unit 250. The collection balance management database stores, for example, the amount received (the amount for which the claim was purchased), the collection due date, and the collection balance for each business operator that has received funds, for each type of claim. Based on the collection balance management database that it has read, the fund provision processing unit 206 identifies (determines) the business operator that has received the funds to be collected. Furthermore, if the system is configured to use a collection agency for fund recovery, the fund provision processing unit 206 identifies the designated collection agency assigned to the identified business (user) as the collection contractor.

[0138] Step S30: The calculation unit 202 calculates the expected collection amount (withdrawal amount WD). The calculation unit 202 obtains one or more of the following, according to the type of receivable: sales information obtained from the settlement server 50 and managed by the user information server 30, reservation information managed by the reservation management server 410, deposit and withdrawal information managed by the accounting server 420, and invoice information managed by the invoice issuance server 430.

[0139] The calculation unit 202 predicts the amount collected by the business operator based on sales information, reservation information, deposit and withdrawal information, and invoice information, as the sales amount used in calculating the withdrawal amount WD. The algorithm used by the calculation unit 202 to calculate the expected collection amount is as described in the calculation of the withdrawal amount WD (step S243).

[0140] Step S40: The notification unit 207 notifies the collection contractor of the planned collection amount. The fund provision processing unit 206 notifies by displaying the planned collection amount calculated by the calculation unit 202 on, for example, the user's (collection contractor's) My Page provided by the fund provision management device 20, or on various management screens provided by the service provision system 40. The notification unit 207 notifies, for example, the planned collection amount on a screen provided by the reservation management server 410 for users to check reservation information. The withdrawal amount notification screen P8 described above is an example of such a screen. As another example, the notification unit 207 may notify the planned collection amount on a screen provided by the accounting server 420 for users to check deposit and withdrawal information.

[0141] Step S50: The Funding Processing Unit 206 issues an invoice or payment request. The Funding Processing Unit 206 instructs the invoice issuance server to issue an invoice or payment request, for example, based on the expected collection amount calculated by the Calculation Unit 202. The invoice or payment request includes the payment due date and the expected collection amount.

[0142] The invoices or payment requests issued by the invoice issuance server may be issued as electronic data, or as paper documents or postcards. Invoice issuance server 430 may be designated as the invoice issuance server.

[0143] Step S60: The fund provision processing unit 206 determines whether the current date is the collection date. The fund provision processing unit 206 makes this determination by comparing the current date with the collection date. If the fund provision processing unit 206 determines that the current date is the collection date (Step S60; YES), it executes the process in Step S70. On the other hand, if the fund provision processing unit 206 determines that the current date is not the collection date (Step S60; NO), it terminates the collection process.

[0144] Step S70: The Funding Processing Unit 206 performs a deposit confirmation. The Funding Processing Unit 206 confirms the deposit by referring to the recipient's account, the deposit and withdrawal information of the accounting server 420, or the notification of the deposit confirmation result from the collection agency. The Funding Processing Unit 206 compares the amount received with the amount scheduled to be collected and determines whether there is any surplus or deficit.

[0145] If the fund provision processing unit 206 determines that the amount received is less than the amount to be recovered, it executes the process in step S80. If the fund provision processing unit 206 determines that the amount received is equal to the amount to be recovered, it executes the process in step S90. If the fund provision processing unit 206 determines that the amount received exceeds the amount to be recovered, it executes the process in step S100.

[0146] Step S80: The notification unit 207 notifies the collection agent (user) of the current insufficient payment amount. This notification includes information such as the insufficient amount, the re-transfer date, and the amount of damages. Therefore, if the amount deposited by the business operator is less than the withdrawal amount, the notification unit 207 will notify the business operator of the insufficient deposit.

[0147] Step S90: The notification unit 207 issues a notification that the collection has been completed.

[0148] Step S100: The notification unit 207 notifies the completion of the collection and also notifies the amount of the payment that has exceeded the limit. Therefore, if the amount deposited by the business exceeds the amount withdrawn, the notification unit 207 will notify the business of the excess deposit amount.

[0149] Furthermore, if the deposit amount exceeds the limit, a refund or carryover to the next collection will be made. Whether a refund or carryover is made may be specified by the fund management device 20 or by the business operator (user). If specified by the user, the Funding Processing Unit 206 accepts the user's selection based on the user's selection. Therefore, if the amount deposited by the business exceeds the withdrawal amount, the Funding Processing Unit 206 will choose, based on the user's selection, whether to issue a refund or carry over the excess to the next withdrawal amount.

[0150] Furthermore, notifications made in step S80, step S90, or step S100 are displayed by the notification unit 207 on various management screens provided by, for example, My Page or the service provision system 40.

[0151] Step S110: The Funding Processing Unit 206 updates the collection balance of the collection contractor (business operator). Based on the amount received as a result of the payment confirmation, the Funding Processing Unit 206 updates the collection balance of the collection contractor (business operator) in the collection balance management database.

[0152] Step S120: The fund provision processing unit 206 checks the outstanding balance of the collection contractor (business operator). The fund provision processing unit 206 reads the collection balance management database from the storage unit 250. The fund provision processing unit 206 checks the collection balance based on the retrieved collection balance management database.

[0153] If the fund provision processing unit 206 determines that the cumulative amount received is less than the amount to be recovered, it executes the process in step S130. If the fund provision processing unit 206 determines that the cumulative amount received is equal to the amount to be recovered, it executes the process in step S140. If the fund provision processing unit 206 determines that the cumulative amount received exceeds the amount to be recovered, it executes the process in step S150.

[0154] Step S130: The notification unit 207 notifies the collection contractor (user) of the outstanding balance.

[0155] Step S140: The notification unit 207 notifies the termination of the collection entrustment. Termination of the collection entrustment means that payment for the provided funds has been completed.

[0156] Step S150: The notification unit 207 notifies the customer of the termination of the collection service and also notifies them of the planned refund.

[0157] Furthermore, notifications made in step S130, step S140, or step S150 are displayed by the notification unit 207 on various management screens provided by, for example, My Page or the service provision system 40. With this, the fund management device 20 terminates the recovery process.

[0158] As described above, the funding system 1 of this embodiment comprises a reception unit 201 and a display control unit 208. Reception room 201 accepts applications for funding from businesses operating as entities. The display control unit 208 displays collection information for each receivable purchased for funding.

[0159] With the funding system 1 configured in this way, users can check the amount withdrawn as payment for receivables purchased for funding purposes, as well as the remaining balance, thereby improving convenience for users.

[0160] Furthermore, the fund provision system 1 of this embodiment includes a reception unit 201, a calculation unit 202, and a notification unit 207. Reception room 201 accepts applications for funding from businesses operating as entities. The calculation unit 202 calculates the withdrawal amount, which is a payment for the provision of funds, based on historical information (in this embodiment, reservation information, deposit and withdrawal information, and invoice information) about the services managed by the service provision system 40 (in this embodiment, a reservation management server 410, an accounting server 420, and an invoice issuance server 430) that provides services to the business entity. The notification unit 207 notifies the service provider of the withdrawal amount via the service provision system 40 (in this embodiment, the reservation management server 410, the accounting server 420, and the invoice issuance server 430).

[0161] With the funding system 1 configured in this way, the amount to be deducted as payment for receivables purchased for funding can be notified to the user through the service provision system that provides the service used by the user, thus facilitating payments for receivables.

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

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

[0164] 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 only a portion 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]

[0165] 1...Funding system, 201...Reception unit, 208...Display control unit

Claims

1. A reception department that accepts applications for funding from businesses operating as entities, A display control unit that displays collection information for each debt purchased for the purpose of providing the aforementioned funds, A funding system equipped with these features.

2. The display control unit displays the collection information on the operator's dedicated screen. The funding system according to claim 1.

3. The aforementioned collection information includes one or more of the following: total withdrawal amount or collection entrusted amount, planned partial collection amount, partially collected amount, and uncollected amount. The funding system according to claim 1.

4. On the computer, We accept applications for funding from businesses operating as entities, To display collection information for each debt purchased for the aforementioned funding, A program to execute.

Images