Funding system and program

Abstract

To provide a funding system which enables effective and flexible utilization of an upper funding limit of each store when funding against future store sales, improving user convenience thereby.SOLUTION: A funding system is provided, comprising a reception unit for receiving a funding application, a computation unit for computing an amount withdrawn from a provided fund, and a proposal unit for proposing additional funding based on the computed withdrawn amount.SELECTED DRAWING: Figure 1

Description

[Technical Field]

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

[0002] Conventionally, a system has been proposed that provides funds based on predicted sales values ​​of a store or the like (for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2022-116627 Summary of the Invention [Problem to be solved by the invention]

[0004] In such a funding system, it is preferable that the upper limit funding limit for each store can be utilized effectively and flexibly.

[0005] The object of the present invention is to provide a funding system and program that can effectively and flexibly utilize the upper limit funding limit for each store when funding the store's future sales, thereby improving convenience for users. [Means for solving the problem]

[0006] One aspect of the present invention is a funding system comprising a reception unit that receives applications for funding, a calculation unit that calculates the amount already debited for the provided funds, and a proposal unit that makes a proposal for additional funding based on the calculated amount already debited.

[0007] One aspect of the present invention is a program for causing a computer to accept an application for funding, calculate the amount of the provided funds that has already been debited, and make a proposal for additional funding based on the calculated amount that has already been debited. [Effects of the Invention]

[0008] According to the present invention, the upper limit funding limit for each store can be effectively and flexibly utilized in funding for future sales of the store, thereby improving convenience for users. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram illustrating an example of a device configuration of a funding system according to an embodiment of the present invention. [Figure 2] FIG. 2 is a diagram illustrating an example of a functional configuration of the funding management device according to the present embodiment. [Figure 3] FIG. 1 is a diagram showing an example of the operational flow (part 1 and part 2) of the funding system of this embodiment. [Figure 4] FIG. 10 is a diagram showing an example of funding limit information according to the present embodiment. [Figure 5] FIG. 10 is a diagram illustrating an example of a store selection screen according to the present embodiment. [Figure 6] FIG. 10 is a diagram showing an example of a funding condition input screen according to the present embodiment. [Figure 7] FIG. 10 is a diagram showing an example of an application content display screen according to the present embodiment. [Figure 8] FIG. 10 is a diagram illustrating an example of an application completion screen according to the present embodiment. [Figure 9] FIG. 10 is a diagram showing an example of an examination status display screen according to the present embodiment. [Figure 10] FIG. 10 is a diagram showing an example of the operational flow (part 3) of the funding system of this embodiment. [Figure 11] FIG. 10 is a diagram showing an example of a deposit information display screen according to the present embodiment. [Figure 12] FIG. 10 is a diagram showing an example of the operational flow (part 4) of the funding system of this embodiment. [Figure 13] A figure showing an example of the correspondence between the amount deposited and the amount withdrawn in the funding contract of this embodiment. [Figure 14] FIG. 10 is a diagram illustrating an example of a withdrawal completion screen according to the present embodiment. [Figure 15] FIG. 10 is a diagram showing an example of funding limit information according to the present embodiment. [Figure 16] FIG. 10 is a diagram illustrating an example of a store selection screen according to the present embodiment. [Figure 17] A figure showing an example of the correspondence between the amount deposited and the amount withdrawn in the funding contract of this embodiment. [Figure 18] FIG. 10 is a diagram illustrating an example of an unused frame presentation screen according to the present embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0010] The funding system 1 of this embodiment will be described with reference to the drawings. The embodiment described below is merely an example, and the embodiments to which the present invention is applied are not limited to the following embodiment. In all the drawings for explaining the embodiments, the same reference numerals are used for components having the same functions, and repeated explanations will be omitted. Furthermore, in this application, "based on XX" means "based on at least XX," and includes cases where it is based on other elements in addition to XX. Furthermore, "based on XX" is not limited to cases where XX is used directly, but also includes cases where it is based on XX that has been calculated or processed. "XX" is any element (for example, any information).

[0011] [Embodiment] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. 1 is a diagram showing an example of the device configuration of a funding system 1 according to this embodiment. The funding system 1 includes a user terminal device 10, a funding management device 20, and a user information server 30.

[0012] The funding system 1 of this embodiment provides an amount equivalent to a portion of future sales of a store to a user who runs one or more stores, based on an application from the user.

[0013] In this embodiment, a "store" broadly includes organizations that are expected to have future sales. For example, the "store" in this embodiment includes not only general retail stores selling goods, but also accommodation facilities such as inns and hotels, food and beverage establishments such as restaurants and izakayas, information providers such as travel, real estate, job listings, wedding venue introductions, and cram schools, rental facilities for items such as car rentals and equipment rentals, purchase and sale facilities for used items, and experience-providing facilities such as amusement parks. Furthermore, the "store" may be a so-called physical store, or a virtual store configured on a network.

[0014] The user terminal device 10 is a computer device such as a personal computer, a tablet, a smartphone, etc. 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, displaying an image on the display unit 11 is also referred to as presenting an image to the user. The operation unit 12 includes, for example, a touch panel, and detects user operations.

[0015] The user terminal device 10 includes a calculation unit 100 and a storage unit 150 . The calculation unit 100 includes, for example, a central processing unit (CPU), and operates based on programs and data stored in the storage unit 150 to provide various functions. The storage unit 150 is configured by, for example, a hard disk drive or semiconductor memory (flash memory, RAM, ROM), and stores various information such as programs and data read by the calculation unit 100. Note that the storage unit 150 may be realized by a virtual storage device such as a cloud server located outside the user terminal device 10.

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

[0017] The funding management device 20 includes a calculation unit 200 and a storage unit 250. The calculation unit 200 includes, for example, a central processing unit (CPU), and operates based on programs and data stored in the storage unit 250 to provide various functions.

[0018] FIG. 2 is a diagram showing an example of the functional configuration of the funds provision management device 20 of this embodiment. The calculation unit 200 of this embodiment includes a reception unit 201, a calculation unit 202, and a proposal unit 203 as its functional units.

[0019] The storage unit 250 is configured, for example, with a hard disk drive or semiconductor memory (flash memory, RAM, ROM), and stores various information such as programs and data read by the calculation unit 200. The storage unit 250 may also be realized by a virtual storage device such as a cloud server external to the funding management device 20.

[0020] 1, the above-mentioned user terminal device 10 and funding management device 20 can communicate with each other via a network NT1. The network NT1 includes the Internet, a wide area network (WAN), a local area network (LAN), a public line, a provider device, a dedicated line, a wireless base station, etc.

[0021] Note that some of the functions of the funding management device 20 described below may be provided in the user terminal device 10 or the user information server 30.

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

[0023] In one example of this embodiment, a user uses a sales settlement system 2 at a store. As an example, the sales settlement system 2 includes 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. A store terminal device 60 is provided for each store, for example. For example, if a user operates k stores (k is a natural number), 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 from one another, they are also collectively referred to as store terminal device 60. This sales settlement system 2 records a log of money deposited for each store (i.e., a log of sales amounts for each store) when, for example, product prices are paid for cashlessly.

[0024] The funding system 1 can communicate with the sales settlement system 2 via the network NT3. The user information server 30 of the funding 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 be simply referred to as "sales information."

[0025] The funding system 1 of this embodiment provides funding to users, collects funds from users, and collects fees through the following four stages. (1) Setting of funding limits (2) Acceptance and review of funding applications (3) Provision of funds (4) Withdrawal from sales

[0026] The funding system 1 of this embodiment can simultaneously conclude multiple funding contracts C for the sales of one store. Below, we will explain the case where there is no other funding contract C in progress and the case where there is another funding contract C in progress.

[0027] <1: If there is no other funding agreement C under contract> First, the flow of operations of the funding system 1 when there is no other funding contract C in progress will be described.

[0028] [Funding System 1 Operation Flow] FIG. 3 is a diagram showing an example of the operational flow (part 1 and part 2) of the funding system 1 of this embodiment.

[0029] [(1) Setting of funding framework] (Step S311) The user information server 30 provides the sales information to the fund provision management device 20. (Step S211) The funding management device 20 acquires sales information from the user information server 30. (Step S212) The funding management device 20 calculates the funding limit FL based on the sales information. The funding management device 20 uses a predetermined algorithm to predict future sales for each store based on the user's sales information for each store (i.e., past sales performance). The funding management device 20 calculates the funding limit FL for each store based on the results of the sales prediction. The funding management device 20 stores the calculated funding limit FL in the memory unit 250 as funding limit information 301.

[0030] In the following description, the upper limit of the funding limit FL for a particular store is also referred to as the upper limit funding limit FL1. That is, the funding management device 20 calculates the upper limit funding limit FL1 for each store based on sales information.

[0031] 4 is a diagram showing an example of the funding limit information 301 of this embodiment. The funding limit information 301 stores a user ID, a store ID, an account ID, and an upper limit funding limit FL1 in association with each store.

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

[0033] A store ID is information that identifies an individual store. Store ID: SP101 is a store ID that identifies the first store of the first user. Store ID: SPnm (m is a natural number) is a store ID that identifies the mth store of the nth user (i.e., the mth store).

[0034] The account ID is information that identifies the deposit account for the funds to be provided. In the funding system 1 of this embodiment, a deposit account is associated with each store terminal device 60 (that is, each payment terminal).

[0035] As an example of this embodiment, the upper limit funding quota FL1 of the store with store ID: SP101 (i.e., the first store of the first user) is the upper limit funding quota FL1-101 (300,000 yen). Note that the amount of the upper limit funding quota FL1 is merely an example. The upper limit funding limit FL1 of the store with store ID: SP102 (i.e., the second store of the first user) is upper limit funding limit FL1-102 (300,000 yen). Similarly, the upper limit funding limit FL1 of the store with store ID: SPnm (i.e., the mth store of the nth user) is upper limit funding limit FL1-nm.

[0036] As described above, the upper limit funding limit FL1 is set based on sales information for each store. Sales figures for each store may differ between stores operated by the same user. As a result, the upper limit funding limit FL1 may be different between stores operated by the same user. For example, the upper limit funding limit FL1 for the store with store ID: SP201 (i.e., the first store of the second user) is upper limit funding limit FL1-201 (400,000 yen). The upper limit funding limit FL1 for the store with store ID: SP202 (i.e., the second store of the second user) is upper limit funding limit FL1-202 (500,000 yen).

[0037] Note that store sales may fluctuate depending on changes in the season, weather, economic conditions, the surrounding environment of the location, etc. The funds management device 20 may be configured to update the upper limit funds limit FL1 by reacquiring the store sales at a predetermined timing.

[0038] (2) Acceptance and review of funding applications (Step S121) Returning to Fig. 3, the user applies for funding by operating the user terminal device 10. The user terminal device 10 notifies the funding management device 20 that the user has applied for funding.

[0039] (Step S221) The reception unit 201 of the funding management device 20 receives the funding application.

[0040] (Step S222) The funds provision management device 20 determines whether or not there is another funds provision contract C in progress at the user's store. In the following explanation, "other funding agreement C under contract" will also be referred to as "other funding agreement C under debit." If the funding management device 20 determines that there is another funding contract C in the process of being debited at the user's store, the processing proceeds to step S223. If the funding management device 20 determines that there is no other funding contract C in the process of being debited at the user's store, the processing proceeds to step S225.

[0041] In this example, a case is described in which there is no other funding contract C in the middle of withdrawal. The funding management device 20 proceeds to step S225.

[0042] (Step S225) The funding management device 20 acquires the upper limit funding limit FL1 of the user who has applied for funding by referring to the funding limit information 301. The funding management device 20 notifies the user terminal device 10 of the upper limit funding limit FL1 acquired in step S221. (Step S122) The user terminal device 10 receives the upper limit funding limit FL1 from the funding management device 20. The user terminal device 10 displays on the display unit 11 the shop selection screen P1 including the received upper limit funding limit FL1.

[0043] 5 is a diagram showing an example of the store selection screen P1 of this embodiment. The store selection screen P1 includes a store-specific funding limit display field P11 and a details display button P12. The store-specific funding limit display field P11 is a field that displays the maximum current amount of spending (available amount) for each store.

[0044] As described above, if there are no other funding contracts C currently being debited, the "maximum amount used = upper limit funding limit FL1", and therefore the upper limit funding limit FL1 will be displayed in the funding limit display field P11 for each store. In the example shown in the figure, the funding limit display field P11 for each store includes a funding limit display field P111 for the first store and a funding limit display field P112 for the second store. The details display button P12 is an operation image for displaying a details screen of the funding plan. When the user operates the details display button P12, the user terminal device 10 causes the display unit 11 to display a funding condition input screen P2.

[0045] 6 is a diagram showing an example of the funding condition input screen P2 of this embodiment. The funding condition input screen P2 includes a store-specific funding condition display field P21, a usage amount selection field P22, a deduction rate selection field P23, and an application button P24.

[0046] The store-specific funding conditions display field P21 is a field that displays the funding conditions when funding is provided using the content currently selected by the user in the usage amount selection field P22 and the deduction rate selection field P23. The funding conditions include the amount of the fee for funding, and simulation results for the amount and timing of deduction. When the user changes the selection in the usage amount selection field P22 or the deduction rate selection field P23, the display content of the store-specific funding conditions display field P21 is immediately changed to match the change. In the example of Figure 6, the store-specific funding conditions display field P21 displays the funding conditions when the usage amount is "700,000 yen" and the deduction rate is "25%."

[0047] In this embodiment, "withdrawal" refers to the organization operating the funding system 1 deducting a portion of the deposit amount as a cost for funding when the store's sales proceeds are deposited into the user's account through the sales settlement system 2 with which the user has a contract. Here, the cost for funding includes the amount of funds provided that have been collected and a fee for funding. In other words, the amount of the store's sales proceeds after deduction (i.e., the amount after the amount of funds collected and the fee have been deducted) is deposited into the user's deposit account.

[0048] The amount of use selection field P22 is a field that presents options for the amount of funds to be provided (i.e., the amount of use). In the example shown in the figure, four options are shown: 50,000 yen, 200,000 yen, 350,000 yen, and 700,000 yen.

[0049] The usage amount selection field P22 always displays the maximum usage amount that can be selected at that time as an option. Here, if the user does not select the maximum option, the difference between the maximum usage amount and the usage amount selected by the user becomes the "unused amount." If there are no other funding agreements C currently being debited, then "maximum funding limit FL1 = maximum usage amount," and therefore "maximum funding limit FL1 - selected usage amount" becomes the unusable amount. In other words, the relationship "unused amount of maximum funding limit FL1 = maximum usage amount (at that time)" holds. Therefore, if there are no other funding agreements C currently being debited, then "funding limit FL1 = unusable amount = maximum usage amount" holds.

[0050] The options for the usage amount are calculated by the funding management device 20 based on the unused amount of the upper limit funding limit FL1. As an example, if the unused amount of the upper limit funding limit FL1 is 700,000 yen, the options calculated are the unused amount (700,000 yen), half of the unused amount (350,000 yen), the minimum usage amount (50,000 yen), and the median between half the amount and the minimum (200,000 yen).

[0051] The minimum spending amount may vary based on the amount of unused funds within the upper limit funding frame FL1. 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 following options: the unused amount (200,000 yen), half of the unused amount (100,000 yen), the minimum value (10,000 yen), and the median between half the amount and the minimum value (45,000 yen, or rounded to 50,000 yen). Generally, stores tend to want to provide as much funding as possible. Therefore, it is expected that it is more advantageous for users to present spending amount options that include the maximum amount available at that time and are a relatively large amount. In other words, it is desirable to present relatively high spending amount options to stores with a high upper limit funding frame FL1, and conversely, it is desirable to present relatively low spending amount options to stores with a low upper limit funding frame FL1.

[0052] It is also possible to set the minimum unit of the amount to be used. For example, if the minimum unit is 10,000 yen, the amount to be used cannot be set in units of 1,000 yen or less. The funding device 20 calculates the options so as to present as many options as possible, but if the upper limit funding frame FL1 is small, there are cases where the number of options that can be presented to the user is less than four. For example, if the upper limit funding frame is only 30,000 yen, only three options can be presented: "10,000 yen," "20,000 yen," and "30,000 yen."

[0053] The deduction rate selection field P23 is a field that presents options for deduction rates. In this embodiment, the "deduction rate" refers to the percentage to be deducted as funding costs from the store's sales amount. In other words, the "deduction rate" is a value indicated by (funding costs / store sales amount). For example, if the withdrawal rate is 25%, the funding cost is an amount equivalent to 25% of the store's sales amount.

[0054] In the example shown in the figure, the funds provision management device 20 calculates options for the withdrawal rate based on the store's expected sales amount predicted based on past sales information. For example, the funds provision management device 20 calculates the withdrawal rate at which the maximum usage amount (e.g., 700,000 yen) presented in the usage amount selection field P22 will be deducted in a predetermined period (e.g., 3 months) as the first option (e.g., 70%). Furthermore, the funds provision management device 20 calculates the withdrawal rate at which the maximum usage amount (e.g., 700,000 yen) presented in the usage amount selection field P22 will be deducted in a predetermined period (e.g., 12 months) longer than the above-mentioned period as the second option (e.g., 25%).

[0055] If the deduction rate is high, a large portion of the sales amount will be deducted to recover the funds provided, which runs the risk of significantly reducing the amount deposited as store sales. On the other hand, there is the benefit of being able to reduce the fees for providing funds, so stores with a relatively stable business can benefit greatly from selecting a high deduction rate. On the other hand, stores that are not yet stable in business or using the service during periods of low sales, such as the off-season, can benefit greatly from selecting a low deduction rate and securing the sales amount to be deposited (but the total amount of fees will increase as deductions are made over a long period of time).

[0056] The application button P24 is an operation image that accepts an operation of the user to confirm the conditions of funding (amount used and withdrawal rate) selected by the user and submit an application. When the user terminal device 10 detects the user's operation on the application button P24, it causes the display unit 11 to display the application content display screen P3.

[0057] 7 is a diagram showing an example of the application content display screen P3 of this embodiment. The application content display screen P3 is a screen that shows which of the stores operated by the user has a funding limit to use. The application content display screen P3 includes a total withdrawal amount display field P31, a scheduled deposit display field P32, a withdrawal information display field P33, and a deposit account display field P34.

[0058] The total amount to be debited display field P31 is a field that displays the total amount to be debited. The total amount to be debited includes the amount of funds provided (i.e., the amount used) and the fee for providing the funds. The total amount to be debited display field P31 displays the total amount to be debited and its breakdown (i.e., the amount used and the fee).

[0059] The expected payment display field P32 is a field in which the date on which the funds will be provided is displayed. The deduction information display field P33 displays the deduction start date, deduction end date, deduction rate, initial deduction amount, and scheduled date of the first deduction. The deposit account display field P34 is a field that displays information about the account (for example, bank account) into which the provided funds will be deposited.

[0060] (Step S123) When the user terminal device 10 receives an operation by the user to accept the contents displayed on the application content display screen P3, it presents an application completion screen P4.

[0061] 8 is a diagram showing an example of the application completion screen P4 of this embodiment. The application completion screen P4 includes an application completion display field P41, a next application selection button P42, and a close button P43.

[0062] The application completion display field P41 is a field where information indicating that the funding application procedure has been completed is displayed. The next application selection button P42 is an operation image that is operated when making another funding application. The close button P43 is an operation image that is operated when ending the application process without making another funding application.

[0063] Furthermore, when the user terminal device 10 receives an operation by the user to accept the contents displayed on the application content display screen P3, it transmits to the funding management device 20 information indicating that the funding conditions have been finalized.

[0064] (Step S226) The receiving unit 201 of the funding management device 20 receives the funding application. Specifically, when the receiving unit 201 receives information indicating that the funding conditions have been finalized, which is transmitted from the user terminal device 10 in step S123, the receiving unit 201 receives the funding application.

[0065] When the funding application is accepted by the funding management device 20, the user terminal device 10 displays on the display unit 11 an examination status display screen P5 showing the status of the application.

[0066] 9 is a diagram showing an example of the review status display screen P5 of this embodiment. The review status display screen P5 includes an application content display field P51 and a status display field P52. The application content display field P51 is a field showing the details of the requested funding conditions. The status display field P52 is a field showing the progress of the review and deposit procedures.

[0067] (3) Provision of Funds FIG. 10 is a diagram showing an example of the operational flow (part 3) of the funding system 1 of this embodiment. (Step S231) If the funding screening is passed, the funding management device 20 performs a deposit process to the account specified by the user (for example, the bank account shown in the deposit account display field P34). (Step S232) The funding management device 20 notifies the user terminal device 10 of the deposit result. (Step S131) ​​When the user terminal device 10 receives the notification of the deposit result from the funding management device 20, it displays a screen (for example, deposit information display screen P6) indicating that the notification of the deposit result has been received.

[0068] 11 is a diagram showing an example of the deposit information display screen P6 of this embodiment. The deposit information display screen P6 includes a deposit status display field P61 and a deposit account display field P62. The deposit status display field P61 displays the name of the store to which funds are being provided, the deposit amount D, and the fact that the procedure has progressed and the deposit has been completed. The deposit account display field P62 displays the name of the financial institution, branch name, account number, etc. of the deposit account.

[0069] [(4) Withdrawal from sales revenue] FIG. 12 is a diagram showing an example of the operational flow (part 4) of the funding system 1 of this embodiment. (Step S341) The user information server 30 provides the fund provision management apparatus 20 with sales information of the store to which funds are provided. (Step S241) The funding management device 20 acquires sales information from the user information server 30.

[0070] (Step S242) The funds provision management device 20 calculates the amount to be debited in advance from the store's sales amount before depositing the funds to the store (i.e., the debit amount WD). The debit amount WD is calculated by multiplying the store's sales amount by the above-mentioned debit rate. For example, if a store's sales amount for a specified period (e.g., 5 days) is 1 million yen and the debit rate is 70%, the debit amount WD for the sales amount for that period is calculated to be 700,000 yen.

[0071] (Step S243) The funding management device 20 notifies the above-mentioned sales settlement system 2 of the debit amount WD. The sales settlement system 2 deposits the debit amount WD, of the store's sales amount, to the operator of the funding system 1 (for example, the funding company), and deposits the remaining amount into the account specified by the user of the user terminal device 10.

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

[0073] FIG. 13 is a diagram showing an example of the correspondence between the deposit amount D and the withdrawal amount WD in a funding contract C1 of this embodiment. In the example shown in the figure, a funding user applied for funding in March of a certain year. Based on this funding application, a funding contract C1 was concluded. Funding of the deposit amount D1 was provided against the upper limit funding limit FL1 of the user's store. In this example, of the upper limit funding limit FL1, the funding limit FL2 is an unused funding limit FL.

[0074] The funding contract C1 may be made in units of the amount of funding provided, or the amount may not be specified, and the contract may be made by specifying the "period" for which the future claims will be transferred, for example, by "transferring the user's sales (future claims) for two years from the date of application in one lump sum." When making a contract specifying the period for which the future claims will be transferred in this way, if settlement is completed before the end of the period, the future claims for the remaining period may be converted to the user at the time of settlement completion. When the transfer period for future claims is specified in advance as described above, the fund provider can refer to the sales forecast for the contract period and easily set an upper limit on the amount of funding within a range that allows settlement to be completed comfortably within the contract period.

[0075] In the example shown in the figure, the deduction amount WD is calculated by multiplying the sales amount SA for each month from April onwards by the deduction rate specified by the user. The cumulative value of the deduction amount WD for a period up to a certain month is the deduction amount RA. When the deduction amount RA matches the deposit amount D1, the deduction for funding agreement C1 is completed.

[0076] Although the explanation is omitted to avoid complicating matters, in reality, a "fee" is incurred for funding according to this embodiment. In other words, the amount deducted from the sales amount is the amount of funds received by the user plus a fee. Therefore, to accurately rephrase the above description of the deducted amount RA, the part "When the deducted amount RA matches the deposit amount D1, the deducting of the funding agreement C1 is completed" should be "When the deducted amount RA matches the total of the deposit amount D1 + the fee (to be paid by the user), the deducting of the funding agreement C1 is completed."

[0077] Although the figure shows deductions occurring once a month, the timing and frequency of deductions are not limited to this. For example, deductions may occur every five days (so-called 5-10 days), or every 10 days. Furthermore, the timing of deductions may differ depending on the financial institution or type of financial institution (for example, city bank, regional bank, second-tier regional bank, credit union, credit association, etc.).

[0078] (Step S244) Returning to FIG. 12, when the funds provision management device 20 determines that the withdrawal is completed, it notifies the user terminal device 10 of the completion of the withdrawal. (Step S141) The user terminal device 10 displays a withdrawal completion screen P7 on the display unit 11.

[0079] 14 is a diagram showing an example of the withdrawal completion screen P7 of this embodiment. The withdrawal completion screen P7 includes information indicating that the withdrawal of the deposit amount D1 based on the funding agreement C1 has been completed.

[0080] <2: If there is another funding agreement C in progress> Next, we will explain the operation flow of the funding system 1 when there is another funding contract C in progress. The funding system 1 of this embodiment can enter into an additional funding contract C even if there is another funding contract C in progress of withdrawal, as long as there is an unused limit in the upper limit funding limit FL1. In the following description, the other funding agreement C being debited will also be referred to as funding agreement C1. The additional funding agreement C will also be referred to as funding agreement C2.

[0081] [Conditions for generating unused quota] The following shows an example of a condition under which an unused portion of the upper limit funding limit FL1 occurs.

[0082] (1) If the amount used is less than the upper limit of funding FL1 set for the user's store: As shown in Figure 13, if the amount used (deposit amount D1) is less than the upper limit funding limit FL1 set for the user's store, the funding limit FL2, which is the difference between the upper limit funding limit FL1 and the deposit amount D1, becomes the unused limit. (2) If a withdrawal is made: As shown in Figure 13, when a withdrawal is made, the withdrawn amount RA, which is the integrated value of the withdrawn amount WD, increases. The unused limit increases by the amount of the increase in the withdrawn amount RA. In other words, the total value of the above-mentioned funding limit FL2 and the withdrawn amount RA becomes the unused limit. To give a specific example using Figure 13, if a store with an upper limit funding limit FL1 of 1 million yen receives funding of 700,000 yen as of March, the unused limit (funding limit FL2) immediately after the funding is provided will be 300,000 yen, calculated as "upper limit funding limit FL1 - deposit amount D1". If 100,000 yen is then deducted from the sales amount in April as a debit amount WD and 50,000 yen in May as a debit amount, when the debits in May are completed the debit amount RA will be 150,000 yen, and the unused limit (funding limit FL2) at this time will be 450,000 yen. (3) If the upper limit of funding FL1 increases: As described above, the funding management device 20 may be configured to update the upper limit funding limit FL1 by reacquiring the store's sales at a predetermined timing. When the funding management device 20 is configured in this way, the upper limit funding limit FL1 increases as the store's sales increase. In other words, the unused limit (funding limit FL2) increases by the amount that the upper limit funding limit FL1 increases.

[0083] The following explanation will explain a specific example of the case shown in (1) above, i.e., when the amount used is less than the upper limit funding limit FL1 set for the user's store, in which an additional funding contract C2 is made. In the following description, the above-mentioned funding limit FL2 will also be referred to as "additional funding limit FL2."

[0084] (Step S121) Returning to Fig. 3, the user applies for additional funding by operating the user terminal device 10. The user terminal device 10 notifies the funding management device 20 that the user has applied for funding.

[0085] (Step S221) The reception unit 201 of the funding management device 20 receives an additional funding application.

[0086] (Step S222) The funds provision management device 20 determines whether or not there is another funds provision contract C in progress at the user's store. In this example, a case is described in which there is another funding contract C (that is, funding contract C1) in the process of being debited. The funding management device 20 proceeds to step S223.

[0087] (Step S223) The calculation unit 202 of the funds provision management device 20 calculates the withdrawn amount RA of the provided funds.

[0088] (Step S224) The calculation unit 202 calculates a new funding limit FL (i.e., additional funding limit FL2) in the additional funding agreement C (i.e., funding agreement C2) based on the upper limit funding limit FL1, the deposit amount D, and the withdrawn amount RA. The calculation unit 202 stores the calculated additional funding limit FL2 in the memory unit 250 as funding limit information 302.

[0089] 15 is a diagram showing an example of funding limit information 302 according to this embodiment. The funding limit information 302 stores a user ID, a store ID, an account ID, an upper limit funding limit FL1, a deposit amount D, a withdrawn amount RA, and an additional funding limit FL2, each associated with a store. In other words, the funding limit information 302 is information obtained by adding columns for the deposit amount D, the withdrawn amount RA, and the additional funding limit FL2 to the above-described funding limit information 301.

[0090] That is, the calculation unit 202 calculates a funding limit FL2, which is the upper limit UL of additional funding, based on a funding limit FL predetermined for the applicant of the application and the withdrawn amount RA.

[0091] (Step S225) The funding management device 20 acquires the additional funding limit FL2 of the user who has applied for funding by referring to the funding limit information 302. The funding management device 20 notifies the user terminal device 10 of the additional funding limit FL2 acquired in step S221.

[0092] (Step S122) The user terminal device 10 receives the upper limit funding limit FL1 from the funding management device 20. The user terminal device 10 displays on the display unit 11 a shop selection screen P1a including the received additional funding limit FL2.

[0093] 16 is a diagram showing an example of a store selection screen P1a according to this embodiment. The store selection screen P1a differs from the store selection screen P1 shown in FIG. 5 in that the amount displayed in the funding limit display field P111a for the first store in the per-store funding limit display field P11 is not the amount of the upper limit funding limit FL1 but the amount of the additional funding limit FL2. This store selection screen P1a can also be said to be a screen for proposing additional funding.

[0094] That is, the proposal unit 203 proposes additional funding based on the calculated withdrawn amount RA.

[0095] It can also be said that the proposal unit 203 proposes additional funding within the scope of the additional funding limit FL2, which is the calculated upper limit UL.

[0096] For the additional funding contract C, which is funding contract C2, the funding management device 20 and the user terminal device 10 sequentially present the funding condition input screen P2 and the application content display screen P3 to the user in the same manner as described for the funding contract C1 above. The amounts displayed on these screens will change accordingly based on the additional funding limit FL2.

[0097] Furthermore, the operational flow from step S123 onwards in the funding contract C2 is the same as the steps from step S123 to step S141 explained in the funding contract C1, and therefore the explanation thereof will be omitted.

[0098] FIG. 17 is a diagram showing an example of the correspondence between the deposit amount D and the withdrawal amount WD in a funding agreement C2 of this embodiment. In the example shown in the figure, a funding user applied for funding in March of a certain year. Based on this funding application, a funding agreement C2 was concluded. Funding of the deposit amount D2 was provided to the user's store's additional funding limit FL2.

[0099] As explained above, the funding limit FL is set for each store associated with the applicant. In this embodiment, the funding agreement C can be concluded for each store.

[0100] That is, the receiving unit 201 receives a first application that is an application related to a first store among a plurality of stores associated with the applicant of the application. The calculation unit 202 calculates a first withdrawn amount RA, which is the amount withdrawn from the first store, out of the withdrawn amount RA. The proposal unit 203 proposes additional funding to the first store based on the calculated first withdrawn amount RA.

[0101] As described above, there are cases where multiple funding agreements C (e.g., funding agreement C1 and funding agreement C2) are simultaneously concluded for a single store's funding limit FL. In this case, in step S224 described above, the calculation unit 202 calculates the debit amount WD and the debited amount RA corresponding to each funding agreement C. The calculation unit 202 adds up the calculated debit amounts RA (e.g., the debited amount RA for funding agreement C1 and the debited amount RA for funding agreement C2) for each store to calculate the unused limit for each store.

[0102] The funding system 1 of this embodiment allows an application for additional funding to be made for the available funding limit for the store (the first store among the multiple stores).

[0103] That is, the calculation unit 202 calculates the second funding limit (additional funding limit FL2), which is the upper limit UL of additional funding for the first store, based on the first funding limit (upper limit funding limit FL1), which is the funding limit FL set for the first store among the multiple stores associated with the applicant of the application, and the first debited amount RA1, which is the amount debited from the first store among the debited amounts RA. The proposal unit 203 proposes additional funding to the first store within the calculated funding limit FL2.

[0104] The funding system 1 may present the latest unused credit limit for each store that has increased as a result of the completion of the withdrawal when notifying the user of the completion of the withdrawal (for example, by presenting the withdrawal completion screen P7 shown in Figure 14) or when notifying the user of the completion of the withdrawal via a medium such as email.

[0105] 18 is a diagram showing an example of the unused quota presentation screen P8 of this embodiment. The unused quota presentation screen P8 includes an unused quota display field P81 for each store. The unused quota display field P81 for each store displays, for example, an unused quota display field P811 for the first store, an unused quota display field P812 for the second store, an unused quota display field P813 for the third store, and so on. This increases the opportunities for the user to consider applying for new funding.

[0106] Furthermore, the system may be designed so that the user can set any amount in advance for notifications of unused limits. For example, for a store that has a relatively high upper limit funding limit FL (e.g., 1 million yen or more), receiving a notification every time the unused limit increases by several tens of thousands of yen can be irritating. Therefore, by setting the notification conditions for unused limits in advance, for example, to "notify when the amount is 500,000 yen or more," when the funding device 20 refers to the additional funding limit FL2 in FIG. 15, the system may present the user with the unused limit presentation screen P8, send an email by push notification, or issue a notification alert in the app only if "additional funding limit FL2≧500,000 yen" is established.

[0107] According to the funding system 1 configured in this manner, even if a funding contract C1 for a store's future sales has been concluded and is currently being withdrawn, an additional funding contract C2 can be concluded up to the upper funding limit FL1 for each store.

[0108] That is, the funding system 1 allows multiple funding agreements C to be concluded up to the upper funding limit FL1 for each store. This allows stores to apply for new funding as soon as the unused limit reaches the desired funding amount, without waiting for the completion of withdrawals for existing funding agreements C, which is a significant benefit in terms of cash flow. Furthermore, by combining multiple funding agreements, more complex funding plans can be set. For example, it is possible to set different amounts and withdrawal rates for funding agreement C1 and funding agreement C2, or to set different timings for deposits and withdrawals between funding agreements C, thereby enabling flexible use of the funding limit FL.

[0109] That is, according to the funding system 1, the upper limit funding quota FL1 for each store can be utilized effectively and flexibly, thereby improving convenience for users.

[0110] Although an embodiment of the present invention has been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes and the like are also included within the scope that does not deviate from the gist of the present invention. For example, a computer program for implementing the functions of each of the above-described devices may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read and executed by a computer system. Note that the term "computer system" may include hardware such as an OS and peripheral devices.

[0111] In addition, "computer-readable recording medium" refers to writable non-volatile memory such as a flexible disk, optical magnetic disk, ROM, or flash memory, portable media such as a DVD (Digital Versatile Disc), or a storage device such as a hard disk built into a computer system. Furthermore, the term "computer-readable recording medium" also includes those that retain a program for a certain period of time, such as volatile memory (e.g., DRAM (Dynamic Random Access Memory)) within a computer system that serves as a server or client when a program is transmitted via a network such as the Internet or a communication line such as a telephone line.

[0112] The program may be transmitted from a computer system storing the program in a storage device or the like to another computer system via a transmission medium or by transmission waves in the transmission medium. Here, the "transmission medium" that transmits the program refers to a medium that has the function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line. The program may also be a program for implementing some of the functions described above, or may be a so-called differential file (differential program) that can implement the functions described above in combination with a program already stored in the computer system. [Explanation of symbols]

[0113] 1... funding system, 10... user terminal device, 20... funding management device, 201... reception unit, 202... calculation unit, 203... proposal unit

Claims

1. a reception department for accepting funding applications; a calculation unit for calculating the amount of funds already withdrawn from the provided funds; a proposal unit that proposes additional funding based on the calculated withdrawn amount; A funding system that includes:

2. The calculation unit calculates an upper limit of additional funding based on a funding limit predetermined for the applicant of the application and the amount already debited, The proposal unit proposes additional funding within the calculated upper limit. The funding system of claim 1 .

3. the reception unit receives a first application that is an application for a first store among a plurality of stores associated with the applicant of the application; the calculation unit calculates a first debited amount, which is the amount debited from the first store, from the debited amount; The proposal unit proposes additional funding to the first store based on the calculated first debited amount. The funding system of claim 1 .

4. The funding limit is determined for each store associated with the applicant; the calculation unit calculates a second funding limit, which is the upper limit of additional funding for the first store, based on a first funding limit, which is the funding limit set for a first store among a plurality of stores associated with the applicant of the application, and a first debited amount, which is the amount debited from the first store among the debited amounts; The proposal unit proposes additional funding to the first store within the calculated second funding limit. The funding system of claim 2 .

5. On the computer, Accepting applications for funding; calculating the amount of funds provided that has been debited; making an offer of additional funding based on the calculated debited amount; A program to execute.

Images