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 funding amount acquisition unit for acquiring a funding amount based on a combined limits obtained by summing funding limits for multiple business entities associated with identification information for identifying users; a withdrawn amount acquisition unit for acquiring a withdrawn amount corresponding to the funding amount from sales of a business entity; a computation unit for computing a withdrawn balance corresponding to the funding amount on the basis of the acquired funding amount and withdrawn amount; and a display control unit for displaying the computed withdrawal balance.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 funding amount acquisition unit that acquires a funding amount based on a combined funding limit obtained by adding up the funding limits of multiple business entities linked to identification information that identifies a user; a debited amount acquisition unit that acquires a debited amount corresponding to the funding amount from the sales of the business entities; a calculation unit that calculates a remaining debit amount corresponding to the funding amount based on the acquired funding amount and debited amount; and a display control unit that displays the calculated remaining debit amount.

[0007] One aspect of the present invention is a program that causes a computer to perform the following operations: obtain a funding amount based on a combined funding limit obtained by adding up the funding limits of multiple business entities linked to identification information that identifies a user; obtain a debit amount corresponding to the funding amount from the sales of the business entities; calculate a remaining debit amount corresponding to the funding amount based on the obtained funding amount and the debit amount; and display the calculated remaining debit amount. [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 showing an example of a funding condition input screen according to the present embodiment. [Figure 6] FIG. 10 is a diagram showing an example of an application content display screen according to the present embodiment. [Figure 7] FIG. 10 is a diagram showing an example of a deposit account candidate screen according to the present embodiment. [Figure 8] FIG. 10 is a diagram showing a modified example of the withdrawal schedule display field of the present embodiment. [Figure 9] FIG. 10 is a diagram illustrating an example of an application completion screen according to the present embodiment. [Figure 10] FIG. 10 is a diagram showing an example of an examination status display screen according to the present embodiment. [Figure 11]FIG. 10 is a diagram showing an example of the operational flow (part 3) of the funding system of this embodiment. [Figure 12] FIG. 10 is a diagram showing an example of a deposit information display screen according to the present embodiment. [Figure 13] FIG. 10 is a diagram showing an example of the operational flow (part 4) of the funding system of this embodiment. [Figure 14] FIG. 10 is a diagram illustrating an example of a withdrawal confirmation screen according to the present embodiment. [Figure 15] A figure showing an example of the correspondence between the amount deposited and the amount withdrawn in the funding contract of this embodiment. [Figure 16] FIG. 10 is a diagram showing an example of a withdrawal completion screen according to the present embodiment. [Figure 17] FIG. 10 is a diagram showing an example of funding limit information according to the present embodiment. [Figure 18] A figure showing an example of the correspondence between the deposit amount and the withdrawal amount in an additional funding agreement of this 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 the future sales of a store to a user who operates one or more stores, based on an application from the user. 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.

[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 has, as its functional units, a reception unit 201, a calculation unit 202, a proposal unit 203, a selection unit 204, a confirmation unit 205, a provided amount acquisition unit 206, a debited amount acquisition unit 207, and a display control unit 208.

[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 arranged, for example, for each store. 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 there is no need to distinguish between the k devices from store terminal device 60-1 to store terminal device 60-k, they will also be collectively referred to as store terminal device 60. This sales settlement system 2 records a log of money deposited at each store (that is, a log of sales amounts at each store) when, for example, the price of a product is settled cashlessly.

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

[0025] In this embodiment, the above-mentioned transaction accounts linked to each store, the store terminal device 60 (payment terminal) installed at each store, and the payment accounts linked to the payment terminals are collectively referred to as payment means. These payment methods are linked to identification information that identifies the user (for example, a user ID of the sales payment system 2). That is, in this embodiment, a plurality of payment methods are linked to identification information that identifies a user (customer).

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

[0027] 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 a funding framework (2) Acceptance and review of funding applications (3) Provision of funds (4) Withdrawal from sales

[0028] The funding system 1 of this embodiment can simultaneously conclude multiple funding contracts C for the sales of one business entity (for example, a store). Below, we will explain the case where there is no other funding contract C under contract, and the case where there is another funding contract C under contract. Also, a "facility" or a "store" may be described as an example of a business entity. In other words, a "facility" or a "store" is an example of a business entity.

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

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

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

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

[0033] 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 a per-store upper limit funding limit FL1 in association with each store.

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

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

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

[0037] In one example of this embodiment, a user operates multiple business entities. In this case, identification information for identifying each of the multiple business entities is linked to a user ID (identification information) for identifying the user (user). The deposit accounts are linked to each of these multiple business entities. That is, the account ID is information that identifies the deposit accounts that are linked to each of the multiple business entities. The deposit account and the transaction account may be the same account. In this case, the account ID is information that identifies the deposit account as well as the transaction account.

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

[0039] As described above, the store-specific upper limit funding quota 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 store-specific upper limit funding quota FL1 may differ between stores operated by the same user. For example, the store-specific upper limit funding quota FL1 for the store with store ID: SP201 (i.e., the first store of the second user) is FL1-201 (400,000 yen). The store-specific upper limit funding quota FL1 for the store with store ID: SP202 (i.e., the second store of the second user) is FL1-202 (500,000 yen).

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

[0041] In addition to the above-mentioned example, the timing of updating the store-specific upper limit funding limit FL1 may be configured to be calculated each time a user applies for funding based on sales information for any period going back from that time.

[0042] Here, the funding management device 20 of this embodiment includes a calculation unit 202. This calculation unit 202 calculates a combined limit obtained by adding up the funding limits predetermined for each of a plurality of business entities, i.e., a combined upper limit funding limit FL1A.

[0043] In the example shown in FIG. 4, a first user (user ID: U001) operates three stores: a first store (store ID: SP101), a second store (store ID: SP102), and a third store (store ID: SP103). The upper limit 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 total upper limit funding limit FL1A obtained by adding up the upper limit funding limits FL1 of 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 total limit assuming that the total upper limit funding limit FL1A of the first user (user ID: U001) is 700,000 yen.

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

[0045] (Step S221) The reception unit 201 of the funding management apparatus 20 receives a funding application from a user. As described above, the user ID (identification information) of the user (customer) is linked to multiple business entities (for example, store IDs).

[0046] That is, the accepting unit 201 accepts applications for funding from users who have identification information linked to multiple business entities.

[0047] In other words, the accepting unit 201 accepts applications for funding from users who have identification information linked to business entities.

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

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

[0050] (Step S225) The funding management device 20 notifies the user terminal device 10 of the combined limit calculated in step S212 (that is, combined upper limit funding limit FL1A).

[0051] The proposal unit 203 of the funding management device 20 proposes funding to the user based on the calculated combined limit (i.e., combined upper limit funding limit FL1A). Proposing funding includes, for example, displaying a funding condition input screen P1 on the display unit 11 of the user terminal device 10.

[0052] (Step S122) The user terminal device 10 receives the combined upper limit funding limit FL1A from the funding management device 20. The user terminal device 10 displays on the display unit 11 the funding condition input screen P1 including the received combined upper limit funding limit FL1A.

[0053] 5 is a diagram showing an example of the funding condition input screen P1 of this embodiment. The funding condition input screen P1 includes a store total funding condition display field P11, a usage amount selection field P12, a deduction rate selection field P13, and an application button P14.

[0054] The store total funding conditions display field P11 is a field that displays the funding conditions when funding is provided based on the content currently selected by the user in the usage amount selection field P12 and the deduction rate selection field P13. The funding conditions include the amount of fees for funding, simulation results for the amount and timing of deductions, etc.

[0055] As an example, the combined upper limit funding limit FL1A (for example, 700,000 yen) calculated in step S212 is displayed in the store combined funding condition display field P11.

[0056] When the user changes the selection in the usage amount selection field P12 or the deduction rate selection field P13, the display content of the store total funding condition display field P11 is immediately changed to match the change. In the example of Figure 5, the store total funding condition display field P11 displays the funding conditions when the usage amount is "700,000 yen" and the deduction rate is "25%."

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

[0058] In addition, if there are no other funding contracts C currently being debited, the "maximum amount used = total upper limit funding limit FL1A" will be displayed, and the total upper limit funding limit FL1A will be displayed in the store total funding conditions display field P11.

[0059] The amount of use selection field P12 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.

[0060] The receiving unit 201 of the funding management device 20 receives an amount selected from a plurality of candidate amounts as the funding amount.

[0061] The usage amount selection field P12 always displays the maximum usage amount selectable 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 "total upper limit funding limit FL1A = maximum usage amount," and therefore "total upper limit funding limit FL1A - selected usage amount" becomes the unusable amount. In other words, the relationship "unused amount of total upper limit funding limit FL1A = maximum usage amount (at that time)" holds. Therefore, if there are no other funding agreements C currently being debited, then "total upper limit funding limit FL1A = unusable amount = maximum usage amount" holds.

[0062] Depending on the type and number of stores operated by the user, the total upper limit funding quota FL1A may be excessive. In this case, the proposal unit 203 may propose funding with the lower of the total upper limit funding quota FL1A calculated by the calculation unit 202 or a predetermined upper limit funding quota as the upper limit of funding.

[0063] That is, the proposal unit 203 may be configured to propose funding with an amount based on the combined limit (for example, combined upper limit funding limit FL1A) and a predetermined upper limit of funding. According to the funding management device 20 configured in this manner, when the funding limits for multiple business entities are added together, the risk of the funding amount becoming excessive and withdrawals not being able to be carried out smoothly can be reduced.

[0064] The options for the usage amount are calculated by the funding management device 20 based on the unused amount of the combined upper limit funding frame FL1A. As an example, if the unused amount of the combined upper limit funding frame FL1A 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).

[0065] The minimum spending amount may vary based on the amount of unused funds in the total upper limit funding limit FL1A. For example, if the unused amount is less than a predetermined value (e.g., 200,000 yen), the funding management device 20 may calculate the minimum amount as 10,000 yen. For example, if the unused amount is 200,000 yen, the funding management device 20 may calculate the 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 50,000 yen rounded up or down). Generally, stores tend to want to provide as much funding as possible. Therefore, it is expected that it would be more advantageous for users to present a relatively large amount as a spending amount option, including the maximum amount available at that time. In other words, it is desirable to present relatively high spending amounts as options to stores with a high combined upper limit funding limit FL1A, and conversely, it is desirable to present relatively low spending amount options to stores with a low combined upper limit funding limit FL1A.

[0066] 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 total upper limit funding frame FL1A 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."

[0067] The deduction rate selection field P13 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.

[0068] In the example shown in the figure, the funds provision management device 20 displays two options for the withdrawal rate: "25%" and "70%." The funds provision management device 20 may arbitrarily set the withdrawal rate option, or the funds provision management device 20 may calculate the withdrawal rate option each time based on the store's expected sales amount predicted based on past sales information. For example, the funds provision management device 20 calculates the first option (e.g., 70%) as the withdrawal rate at which the maximum amount of the usage amount presented in the usage amount selection field P12 (e.g., 700,000 yen) will be deducted within a predetermined period (e.g., 3 months). The funds provision management device 20 also calculates the second option (e.g., 25%) as the withdrawal rate at which the maximum amount of the usage amount presented in the usage amount selection field P12 (e.g., 700,000 yen) will be deducted within a predetermined period (e.g., 12 months) longer than the above period.

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

[0070] The application button P14 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 display control unit 208 detects a user operation on the application button P14, it causes the display unit 11 of the user terminal device 10 to display the application content display screen P2.

[0071] That is, the display control unit 208 displays a confirmation screen for confirming the accepted application.

[0072] 6 is a diagram showing an example of the application content display screen P2 of this embodiment. The application content display screen P2 is a screen that presents the details of a user's application for funding. The application content display screen P2 includes a total deduction amount display field P21, a deposit account selection field P22, a deduction schedule display field P23, and an application confirmation operation button P24.

[0073] The total amount to be debited display field P21 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 P21 displays the total amount to be debited and its breakdown (i.e., the amount used and the fee).

[0074] The deposit account selection field P22 is a field for accepting an operation to select a deposit account. Selecting a deposit account means selecting the deposit account linked to which store the funds will be provided from among the deposit accounts linked to stores operated by the user.

[0075] When the deposit account selection field P22 is operated, the display control unit 208 causes the display unit 11 of the user terminal device 10 to display a deposit account candidate screen P221.

[0076] 7 is a diagram showing an example of the deposit account candidate screen P221 of this embodiment. The deposit account candidate screen P221 displays deposit accounts based on the account ID of each store linked to the user ID (i.e., the deposit accounts of each store). In this example of the present 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).

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

[0078] The selection unit 204 selects the deposit account designated by the user as the deposit account of the fund recipient from among the candidate deposit accounts of the fund recipient displayed on the application confirmation screen.

[0079] That is, the selection unit 204 selects a deposit account to which funds will be provided based on the accepted application from among deposit accounts linked to multiple business entities.

[0080] Returning to Figure 6, the Withdrawal Schedule Display Column P23 displays the dates on which the withdrawal will be made. It displays the start date of the withdrawal, the end date of the withdrawal, the withdrawal rate, the initial withdrawal amount, and the scheduled date of the first withdrawal. This figure shows an example of the display when there are no other funding agreements C currently under contract.

[0081] This example shows that the first deduction will occur after a predetermined period has elapsed from the date of application for funding (application date). The predetermined period may be determined by funding agreement C. As an example, funding agreement C determines that the predetermined period is 12 business days starting from the day after the date of application for funding. In this example, it shows that the first deduction will occur 12 business days starting from the day after the date of application for funding.

[0082] As described above, debit refers to a fund provider deducting in advance an amount corresponding to the amount of funding from the sales of a business entity (e.g., a store) operated by a user in the sales settlement system 2. The remaining amount after deducting the amount corresponding to the amount of funding from the sales of the business entity (e.g., a store) is deposited into the user's transaction account. The display control unit 208 displays the withdrawal schedule in the withdrawal schedule display field P23.

[0083] That is, the display control unit 208 displays a schedule of deductions from sales of the business entity.

[0084] As shown in the figure, the display control unit 208 displays the withdrawal schedule in a calendar format showing dates for each day of the week.

[0085] Generally, settlements by the sales settlement system 2 through financial institutions are made several times per month at predetermined intervals, such as on dates that are multiples of 5 (5th, 10th, 15th, 20th, 25th, 30th) or on dates that are multiples of 10 (10th, 20th, 30th). These settlement dates are determined by a contract between the operator of the sales settlement system 2 and the financial institution, and the settlement cycle may differ depending on the type of financial institution. If the settlement date by the sales settlement system 2 (that is, the date on which the deduction for the provided funds occurs) differs depending on the type of financial institution, it becomes difficult for the user to know when the deduction will occur. According to the funding system 1 of this embodiment, the withdrawal schedule is displayed in a calendar format, making it easier for the user to grasp the date on which the withdrawal will occur.

[0086] The display control unit 208 can display the withdrawal schedule in various formats in the withdrawal schedule display field P23.

[0087] FIG. 8 is a diagram showing a modified example of the withdrawal schedule display field P23 of this embodiment. [A] in the same figure shows a modified example of the withdrawal schedule display field P23a. The withdrawal schedule display field P23a is an example of a case where, when multiple funding agreements C have been concluded, the withdrawal due date of the currently applied funding agreement C and the withdrawal due dates of other funding agreements C concluded in the past are displayed in calendar format. In this example, the first withdrawal due date of the currently applied funding agreement C is displayed in a different manner from the other withdrawal due dates. The withdrawal schedule display field P23a configured in this manner displays the timing at which the withdrawal amount increases in a format that is easy for the user to visually recognize, thereby providing the effect of making it easier for the user to refer to their cash flow schedule.

[0088] [B] in the same figure shows a modified example of the withdrawal schedule display field P23b. The withdrawal schedule display field P23b is an example of a case where the withdrawal due date and number of withdrawals for the currently applied funding agreement C are displayed in a calendar format. With the withdrawal schedule display field P23b configured in this way, the number of withdrawals is displayed in a format that is easy for the user to see, which has the effect of making it easier for the user to refer to their cash flow schedule.

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

[0090] 6, the application confirmation operation button P24 is an operation image operated by the user when confirming the application for funding. The application confirmation operation button P24 is operated by the user when the user agrees with the content displayed on the application content display screen P2.

[0091] (Step S123) When the user terminal device 10 detects the user's operation on the application confirmation operation button P24, it presents the application completion screen P3.

[0092] 9 is a diagram showing 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.

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

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

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

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

[0097] 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 P4 showing the status of the application.

[0098] 10 is a diagram showing an example of the review status display screen P4 of this embodiment. The review status display screen P4 includes an application content display field P41 and a status display field P42. The application content display field P41 is a field showing the details of the requested funding conditions. The status display field P42 is a field showing the progress of the review and deposit procedures.

[0099] (3) Provision of Funds FIG. 11 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 deposit account selected in the deposit account selection field P22). (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 P5) indicating that the notification of the deposit result has been received.

[0100] 12 is a diagram showing 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 field P51 displays the name of the store to which funds are being provided, the deposit amount D, and the stage at which the procedure has progressed and the deposit has been completed. The deposit account display field P52 displays the name of the financial institution, branch name, account number, etc. of the deposit account.

[0101] [(4) Withdrawal from sales revenue] FIG. 13 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.

[0102] (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 total sales amount obtained by adding up the sales amounts of multiple stores by the above-mentioned debit rate. For example, if the total sales amount for a specified period (e.g., 5 days) is 1 million yen and the debit rate is 25%, the debit amount WD for the total sales amount for that period is calculated as 250,000 yen.

[0103] More specifically, the provision amount acquisition unit 206 of the funding management device 20 acquires the funding amount (that is, the deposit amount D1) in the funding contract C signed by the user. The calculation unit 202 calculates the sum of the withdrawal amounts WD that have been withdrawn during the withdrawal period of the funding agreement C (that is, the withdrawn amount RA). The debited amount acquisition unit 207 acquires the sum of the debited amounts WD that have been debited during the debit period of the funding contract C (that is, the debited amount RA).

[0104] That is, the provision amount acquisition unit 206 acquires the funding amount based on the total funding limit obtained by adding up the funding limits of each of the multiple business entities linked to the identification information that identifies the user. The term "business entity" as used herein refers to restaurants, beauty salons, retail stores, accommodation facilities, medical facilities, etc. As described above, even if the same business entity (e.g., a store) has multiple payment terminals and different accounts are assigned to each payment terminal, the different accounts may be determined to be "different business entities (e.g., stores)." In the example of this embodiment, when a transaction account is linked to each store, the provision amount acquisition unit 206 acquires a funding amount based on the combined funding limit obtained by adding up the respective funding limits for multiple stores operated by the user. The debited amount acquisition unit 207 acquires the debited amount corresponding to the funded amount from the sales of the business entity.

[0105] The calculation unit 202 calculates the remaining amount of withdrawal corresponding to the amount of funding based on the acquired deposit amount D1 and the withdrawn amount RA. For example, the calculation unit 202 calculates the remaining amount of withdrawal as (deposit amount D1 - withdrawn amount RA).

[0106] The display control unit 208 of the funding management device 20 causes the display unit 11 of the user terminal device 10 to display a withdrawal confirmation screen P6 showing the withdrawal amount WD and the remaining withdrawal amount.

[0107] 14 is a diagram showing an example of the deduction confirmation screen P6 of this embodiment. The deduction confirmation screen P6 includes a current deduction information field P61 and a future deduction information field P62. The current deduction amount WD is displayed in the current deduction information field P61. The current deduction amount WD is an example of deduction information that includes the deduction amount for the due date closest to the present among future deduction dates.

[0108] That is, the display control unit 208 displays the debit information including the debit amount for the due date closest to the present among the future debit due dates.

[0109] The future withdrawal information column P62 displays the remaining amount to be withdrawn, the number of remaining withdrawals estimated based on the store's sales situation, and the timing of withdrawal completion.

[0110] That is, the display control unit 208 displays at least one of the remaining number of withdrawals or the timing of withdrawal completion for the remaining withdrawal amounts of a plurality of business entities.

[0111] The display control unit 208 may be configured to display the amount debited from each of a plurality of business entities for each business entity.

[0112] (Step S243) Returning to FIG. 13, 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.

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

[0114] FIG. 15 is a diagram showing an example of the correspondence between the deposit amount D and the withdrawal amount WD in a funding agreement 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 agreement C1 was concluded. Funding of the deposit amount D1 was provided against the combined upper limit funding limit FL1A of the user's store. In this example, of the combined upper limit funding limit FL1A, the combined funding limit FL2A is an unused funding limit FL.

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

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

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

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

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

[0120] 16 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.

[0121] <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 combined upper limit funding limit FL1A. 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.

[0122] [Conditions for generating unused quota] The following are examples of conditions under which unused quotas will be generated for the combined upper limit funding quota FL1A.

[0123] (1) If the amount used is less than the combined upper limit of funding FL1A set for the user's store: As shown in Figure 15, if the usage amount (deposit amount D1) is less than the combined upper limit funding limit FL1A set for the user's store, the combined funding limit FL2A, which is the difference between the combined upper limit funding limit FL1A and the deposit amount D1, becomes the unused limit. (2) If a withdrawal is made: As shown in Figure 15, 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 sum of the above-mentioned combined funding limit FL2A and the withdrawn amount RA becomes the unused limit. To give a specific example, if a store with a combined upper limit funding limit FL1A of 1 million yen receives funding of 700,000 yen as of March, the unused limit immediately after funding (combined funding limit FL2A) will be 300,000 yen, calculated as combined upper limit funding limit FL1A - deposit amount D1. If 100,000 yen is then deducted from sales in April as a WD deduction, and 50,000 yen in May as a WD deduction, then when the deduction in May is completed, the deducted amount RA will be 150,000 yen, and the unused limit (combined funding limit FL2A) at this time will be 450,000 yen. (3) If the combined upper limit of funding FL1A increases: As described above, the funding management device 20 may be configured to update the combined upper limit funding limit FL1A by reacquiring store sales data at a predetermined timing. When the funding management device 20 is configured in this manner, the combined upper limit funding limit FL1A increases as the store sales data increases. In other words, the unused limit (combined funding limit FL2A) increases by the amount that the combined upper limit funding limit FL1A increases.

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

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

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

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

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

[0129] (Step S224) The calculation unit 202 calculates a new funding limit FL (i.e., additional per-store funding limit FL2) in the additional funding agreement C (i.e., funding agreement C2) based on the combined upper limit funding limit FL1A, the deposited amount D, and the withdrawn amount RA. The calculation unit 202 stores the calculated additional per-store funding limit FL2 in the storage unit 250 as funding limit information 302.

[0130] 17 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, a store-specific upper limit funding limit FL1, a deposit amount D, a withdrawn amount RA, and an additional store-specific funding limit FL2, all of which are associated with each 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 store-specific funding limit FL2 to the above-described funding limit information 301.

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

[0132] (Step S225) The funding management device 20 refers to the funding limit information 302 and acquires the additional per-store funding limit FL2 of the user who has applied for funding. The funding management device 20 calculates a combined funding limit FL2A by adding up the additional per-store funding limits FL2 acquired in step S221 across multiple stores. The funding management device 20 notifies the user terminal device 10 of the calculated combined funding limit FL2A.

[0133] (Step S122) The user terminal device 10 receives the combined funding limit FL2A from the funding management device 20. The user terminal device 10 displays on the display unit 11 a shop selection screen (not shown) including the received combined funding limit FL2A.

[0134] The store selection screen including the combined funding limit FL2A differs from the funding condition input screen P1 shown in Fig. 5 in that the amount shown in the funding limit display field for the first store in the per-store funding limit display field is not the amount of the combined upper limit funding limit FL1A but the amount of the additional combined funding limit FL2A. The store selection screen displayed in step S122 can also be said to be a screen for proposing additional funding.

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

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

[0137] 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 P1 and the application content display screen P2 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 combined funding limit FL2A.

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

[0139] FIG. 18 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 combined funding limit FL2A.

[0140] As described above, the funding limit FL is set for each store associated with the applicant. In this embodiment, the funding contract C can be concluded based on the combined funding limit FL of each of the multiple stores.

[0141] According to the funding system 1 configured in this manner, even if the upper limit funding limit FL1 of an individual store is relatively small, the combined upper limit funding limit FL1 of each store can be utilized, thereby enabling a larger amount of funding to be received. For example, if the funding amount is too low, a minimum funding limit may be set for the funding amount due to the relatively high fixed costs, such as management costs and system operation costs, for concluding the funding contract C, or the cumbersome process. In such a case, if the combined upper limit funding limit FL1 of each store can be utilized, the opportunities for concluding a funding contract C that exceeds the minimum funding amount increase. In other words, according to the funding system 1, the upper limit funding limit FL of each store can be utilized more flexibly.

[0142] Furthermore, as described above, according to the funding system 1, the funding contract C is concluded based on the combined funding limit FL of each of multiple stores. Therefore, even if a change in the business environment occurs, such as the closure of a store, the funding amount can be debited using sales from other stores. Therefore, according to the funding system 1, situations in which debits are delayed are reduced, thereby reducing the user's risk of changes in the business environment. Furthermore, the funding system 1 can reduce the risk of changes in the user's business environment, making it possible to provide larger amounts of funding to users.

[0143] Furthermore, according to the funding system 1, the funding contract C can be operated all at once based on the combined limit of multiple stores, thereby reducing the amount of work required for operations compared to operating the funding contract C individually for the upper limit funding limit FL1 of each store.

[0144] In addition, when the funding system 1 notifies the user of the completion of the withdrawal (for example, by presenting the withdrawal completion screen P7 shown in Figure 16) or when notifying the user of the completion of the withdrawal via a medium such as email, it may also present the latest unused limit for each store that has increased as a result of the completion of the withdrawal.

[0145] 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 a nuisance. Therefore, by setting the notification conditions for unused limits in advance, for example, to "notify when the amount is 500,000 yen or more," the funding device 20 may present the user with an unused limit notification screen, send an email by push notification, or issue an app notification alert only when "total funding limit FL2A≧500,000 yen" is established when referring to the combined funding limit FL2A in FIG. 15.

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

[0147] Furthermore, the funding system 1 allows multiple funding agreements C to be concluded up to the combined limit of the upper funding limit FL1 of each store. This allows users 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, combining multiple funding agreements allows for more complex funding plans to 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.

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

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

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

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

[0152] 1... funding system, 10... user terminal device, 20... funding management device, 201... reception unit, 202... calculation unit, 203... proposal unit, 204... selection unit, 205... confirmation unit, 206... funding amount acquisition unit, 207... debited amount acquisition unit, 208... display control unit

Claims

1. a funding amount acquisition unit that acquires a funding amount based on a total funding limit obtained by adding up the funding limits of a plurality of business entities linked to identification information that identifies a user; a debit amount acquisition unit that acquires a debit amount corresponding to the funded amount from the sales of the business entity; a calculation unit that calculates a remaining amount to be debited corresponding to the funded amount based on the acquired funded amount and the debited amount; a display control unit that displays the calculated remaining withdrawal amount; A funding system that includes:

2. The display control unit Display the amount debited from multiple business entities for each business entity The funding system of claim 1 .

3. The display control unit Display withdrawal information including the withdrawal amount for the nearest future due date The funding system of claim 1 .

4. The display control unit Displaying at least one of the remaining number of withdrawals or the timing of withdrawal completion for the remaining withdrawal amounts of a plurality of business entities The funding system of claim 1 .

5. On the computer, Obtaining a funding amount based on a total funding limit obtained by adding up the funding limits of each of a plurality of business entities linked to identification information that identifies the user; obtaining a debited amount corresponding to the funding amount from the sales of the entity; Calculating a remaining amount to be debited corresponding to the funded amount based on the acquired funded amount and the debited amount; Displaying the calculated withdrawal balance; A program to execute.

Images