Funding systems and programs

Abstract

We provide a funding system and program that can improve convenience for users by offering various business schemes tailored to the user's business model. [Solution] The funding system includes: a past transaction information acquisition unit that acquires past transaction information showing the past transaction status between a seller and a buyer based on invoices presented by the seller (user) to the buyer; an identification unit that identifies a specific invoice which is an invoice corresponding to future accounts receivable that is the subject of funding, based on the acquired past transaction information; and a funding unit that provides funding to the user as consideration for purchasing the future accounts receivable of the identified specific invoice.

Description

Technical Field

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

Background Art

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

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In such a fund - providing system, it is preferable to be able to provide various business schemes according to the business form of the user.

[0005] An object of the present invention is to provide a fund - providing system and a program that can improve the convenience for the user by providing various business schemes according to the business form of the user.

Means for Solving the Problems

[0006] One aspect of the present invention includes a past transaction information acquisition unit that acquires bill past transaction information indicating the past transaction situation between a seller and a buyer based on a bill presented by a user who is the seller to the buyer; a specifying unit that specifies a specific bill that is a bill corresponding to a future sales receivable that is the target of fund - providing based on the acquired bill past transaction information; and a fund - providing unit that provides funds to the user as consideration for purchasing the future sales receivable of the specified specific bill.

[0007] One aspect of the present invention is a program that causes a computer to perform the following actions: acquire invoice history transaction information showing past transaction status between a seller and a buyer based on invoices presented by a seller (user) to a buyer; identify a specific invoice that corresponds to a future accounts receivable that is the subject of funding, based on the acquired invoice history transaction information; and provide funding to the user as consideration for purchasing the future accounts receivable of the identified specific invoice. [Effects of the Invention]

[0008] According to the present invention, by providing various business schemes tailored to the user's business model, convenience for the user can be improved. [Brief explanation of the drawing]

[0009] [Figure 1] This figure shows an example of the device configuration of the fund provision system and the functional configuration of the fund provision management device according to the first embodiment. [Figure 2] This figure shows an example of a business scheme for the funding stage of the funding system of this embodiment. [Figure 3] This figure shows an example of the operation flow in the pre-funding stage of the funding system of this embodiment. [Figure 4] This figure shows an example of the operation flow during the funding stage of the funding system of this embodiment. [Figure 5] This figure shows an example of a business scheme for the recovery phase of the funding system of this embodiment. [Figure 6] This figure shows an example of the operation flow during the recovery phase of the funding system of this embodiment. [Figure 7] This figure shows an example of the device configuration of the fund provision system and the functional configuration of the fund provision management device according to the second embodiment. [Figure 8] This figure shows an example of a business scheme for the funding stage of the funding system of this embodiment. [Figure 9]This figure shows an example of the operation flow in the pre-funding stage of the funding system of this embodiment. [Figure 10] This figure shows an example of a business scheme for the recovery phase of the funding system of this embodiment. [Figure 11] This figure shows an example of the operation flow during the recovery phase of the funding system of this embodiment. [Figure 12] This figure shows an example of the device configuration of the funding system and the functional configuration of the funding management device according to the third embodiment. [Figure 13] This figure shows an example of a business scheme for the funding stage of the funding system of this embodiment. [Figure 14] This figure shows an example of the operation flow in the pre-funding stage of the funding system of this embodiment. [Figure 15] This figure shows an example of a business scheme for the recovery phase of the funding system of this embodiment. [Figure 16] This figure shows an example of the operation flow during the recovery phase of the funding system of this embodiment. [Figure 17] This figure shows an example of a business scheme at the funding stage in a modified version of the funding system of this embodiment. [Figure 18] This figure shows an example of a business scheme for the recovery phase in a modified version of the funding system of this embodiment. [Modes for carrying out the invention]

[0010] The funding system 1 of this embodiment will be described with reference to the drawings. The embodiments described below are merely examples, and the embodiments to which the present invention is applied are not limited to the embodiments described below. In all the figures used to illustrate the embodiments, components with the same function are given the same reference numerals, and repeated explanations are omitted. In addition, "based on XX" as referred to in this application means "at least based on XX", and includes cases where it is based on another element in addition to XX. Also, "based on XX" is not limited to the case of directly using XX, and includes cases where it is based on something obtained by performing operations or processing on XX. "XX" is any element (for example, any information).

[0011] [First Embodiment] Hereinafter, referring to the drawings, the first embodiment of the present invention will be described. FIG. 1 is a diagram showing an example of the device configuration of the fund - providing system 1 and the functional configuration of the fund - providing management device 20 in the first embodiment. The fund - providing system 1 includes a user terminal device 10, a fund - providing management device 20, an invoice - issuing system 30, and an account - management system 40.

[0012] The fund - providing system 1 in the present embodiment provides an amount corresponding to a part of the future sales of a store to the user based on the application of the user who is an operator such as a store.

[0013] In the present embodiment, the store broadly includes organizations for which future sales can be expected. For example, the "store" as referred to in the present embodiment includes, in addition to general retail stores of goods, accommodation facilities such as hotels and inns, food - providing facilities such as restaurants and izakayas, information - providing facilities such as travel, real estate, job - hunting, wedding - venue introduction, and learning schools, article - rental facilities such as car rentals and equipment rentals, buy - and - sell facilities for used goods, experience - providing facilities such as amusement parks, etc. Also, the "store" may be a virtual store configured on the network in addition to a so - called physical store. Note that the user only needs to be operating a business for which continuous sales can be expected, and does not necessarily need to be operating a store.

[0014] In the following description, the goods or services provided by the user at a store (or non - store) are also described as the services provided by the user (or simply services). In other words, a user can be considered a seller of a service. Those who receive services from a user (i.e., the user's customer) are also called buyers of services. The seller and buyer of a service are simply referred to as seller and buyer, respectively. The seller provides a service to the buyer. The buyer pays the seller a fee for the service. The seller (e.g., the user) receives this fee as revenue.

[0015] The actors in this embodiment can be summarized as follows: • Seller: The provider of the service. Also known as a user of the funding system 1. Operates the user terminal device 10. • Buyer: A party that receives services from a user and pays a fee for those services. Also known as the user's customer. • Funding provider: A person who acquires the seller's future accounts receivable and provides funds to the seller. A portion of the consideration paid by the buyer to the seller is used to recover the funds provided. The funding management device 20 is operated.

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

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

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

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

[0020] The calculation unit 200 of this embodiment includes, as its functional units, a past transaction information acquisition unit 201, a specific unit 202, a fund provision unit 203, a deposit information acquisition unit 204, a withdrawal amount calculation unit 205, a withdrawal amount notification unit 206, a collection unit 207, and a transfer unit 208.

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

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

[0023] Furthermore, the user terminal device 10 may also have some of the functions of the fund management device 20 described below.

[0024] The invoice issuance system 30 is configured, for example, as a cloud server and manages invoices related to services provided by the user. For example, the invoice issuance system 30 manages the issuance of invoices and the receipt of payment for services provided by the user to buyers. Information on the amount of sales received by the user using invoices is also called invoice sales information.

[0025] The account management system 40 manages the user's account. For example, the account management system 40 deposits the funds withdrawn by the fund provision management device 20 into the user's account.

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

[0027] [Business scheme for funding system 1] Figure 2 shows an example of the business scheme at the funding stage of the funding system 1 of this embodiment.

[0028] In the business scheme of this embodiment, funding is provided to users in the following procedure. 0: The fund management device 20 collects deposit and withdrawal data from the user's financial institution account (for example, via the account management system 40). 1. The fund management device 20 collects past transaction data related to the user's invoices from the invoice issuance system 30. 2: The fund management device 20 predicts the amount of money received from buyers to sellers (i.e., the user's future sales) for a predetermined period (for example, the next two years) based on the collected data. 3. Set up accounts receivable (future accounts receivable R1) for the projected future sales with the seller. 4. The fund management device 20 purchases future accounts receivable R1 from the seller. 5. The fund provision management device 20 provides funds to the seller as consideration for the future accounts receivable R1 that it has purchased.

[0029] [Operation Flow of Funding System 1] Figure 3 shows an example of the operation flow of the funding system 1 of this embodiment in the pre-funding stage.

[0030] [(1) Setting of funding framework] The fund provision management device 20 works in conjunction with the invoice issuance system 30 to understand the transaction status of users.

[0031] (Step S311) The invoice issuance system 30 provides the fund provision management device 20 with past invoice transaction information D1. Past invoice transaction information D1 refers to information on past transactions among the invoice issuance status managed by the invoice issuance system 30. (Step S211) The past transaction information acquisition unit 201 of the fund provision management device 20 acquires past invoice transaction information D1 from the invoice issuance system 30.

[0032] In other words, the past transaction information acquisition unit 201 acquires past invoice transaction information D1 from the invoice issuance system 30 used by the user.

[0033] As mentioned above, Invoice Past Transaction Information D1 is information that shows the past transaction status between the seller and the buyer based on the invoice presented by the seller (user) to the buyer.

[0034] In other words, the past transaction information acquisition unit 201 acquires invoice past transaction information D1, which shows the past transaction status between the seller and the buyer, based on the invoice presented by the seller (user) to the buyer.

[0035] (Step S212) The fund provision management device 20 calculates the fund provision limit based on the invoice past transaction information D1. Specific invoices are used to calculate the fund provision limit. Specific invoices are invoices from past transactions included in the invoice past transaction information D1 that meet specific conditions corresponding to the future accounts receivable R1 that are the target of the fund provision. Specific invoices will be explained below.

[0036] The identification unit 202 of the fund provision management device 20 identifies a specific invoice from among the invoices of past transactions included in the invoice past transaction information D1 using a predetermined algorithm.

[0037] For example, by referring to the seller, buyer, and the extent of the transaction (e.g., frequency of invoice issuance, issuance period, number of invoices issued, etc.) for multiple invoices, it is possible to determine whether a continuous transaction is occurring between the seller and buyer at a frequency such as daily, weekly, monthly, or yearly. If a continuous transaction has occurred in the past, it can be presumed that a similar continuous transaction will occur in the future.

[0038] The identification unit 202 determines whether an ongoing transaction will occur based on information such as the seller, buyer, and extent of issuance of the invoice, and identifies an invoice (or group of invoices) that it has determined will result in an ongoing transaction as a specified invoice.

[0039] In other words, the identification unit 202 identifies a specific invoice that corresponds to the future accounts receivable R1 that is the subject of funding, based on the acquired invoice past transaction information D1.

[0040] For example, a user may operate a food supply store and continuously supply food to a restaurant (for example, once a week). In this case, all invoices included in this group of invoices for this particular food item are in a manner where the seller is the user, the buyer is the restaurant, and the transaction frequency is weekly. The Identification Unit 202 determines that this group of invoices for this particular food item is a group of invoices representing a continuous transaction. In other words, the Identification Unit 202 identifies this group of invoices for this particular food item as a specific invoice.

[0041] In other words, the identification unit 202 identifies a specific invoice based on the combination of seller, buyer, and frequency of the invoice indicated in the invoice past transaction information D1.

[0042] The fund management device 20 predicts the user's future sales by estimating the transaction size for identified specific invoices based on a predetermined algorithm.

[0043] [(2) Acceptance and review of applications for funding] (Step S121) The user operates the user terminal device 10 to apply for funding. The user terminal device 10 notifies the funding management device 20 that the user has applied for funding. Furthermore, the fund provision management device 20 may also include an invitation notification unit that notifies businesses registered in the invoice issuance system 30 of their invitation to become factoring candidates. By targeting businesses registered in the invoice issuance system 30 as the target population for marketing and sales activities, an efficient sales approach becomes possible. In conventional funding methods, applications must be received, and then various documents must be submitted for review and assessment, resulting in a lengthy process and a long lead time for receiving funding. On the other hand, with the funding system 1 of this embodiment, reviews and assessments can be conducted in advance for businesses registered in the invoice issuance system 30, thus shortening the lead time for funding and providing benefits to both the recipient and the provider of funding.

[0044] (Step S221) The fund provision management device 20 receives a fund provision application from the user terminal device 10. (Step S222) The fund provision management device 20 receives a fund provision application.

[0045] [(3) Provision of funds] Figure 4 shows an example of the operation flow during the funding stage of the funding system 1 of this embodiment. (Step S231) If the review after the funding application (funding review) is passed, the funding management device 20 processes the deposit into the financial institution account specified by the user. In one example of this embodiment, the user is using the account management system 40. In this case, the funding management device 20 withdraws the funds to the user's account managed by the account management system 40 (for example, sales deposit account A1).

[0046] In other words, the Funding Department 203 provides funds to the user as consideration for purchasing the future accounts receivable R1 of the specified invoices identified by the Identification Department 202.

[0047] (Step S431) The account management system 40 deposits the funds withdrawn by the fund provision management device 20 into the user's account.

[0048] (Step S232) The fund management device 20 notifies the user terminal device 10 of the deposit result. (Step S131) ​​When the user terminal device 10 receives a notification of the deposit result from the fund management device 20, it displays to the user that a notification of the deposit result has been received. The fund management device 20 may also send a transfer result notification (transfer notification) instead of a deposit result notification. In this case, when the user terminal device 10 receives a deposit notification from the fund management device 20, it will show the user that a deposit result notification has been received.

[0049] [(4) Deduction from sales proceeds] This section explains the deduction from sales proceeds. In this embodiment, "deduction" refers to the organization operating the funding system 1 deducting the costs of funding from the user's sales proceeds. Here, the costs of funding include the amount recovered from the funds provided and the fees for funding. In other words, the amount deposited into the user's deposit account is the amount after the deduction (i.e., the amount after the amount recovered from the funds and the fees have been deducted) from the sales proceeds. The act of the funding system 1 deducting the costs of funding from the user's sales proceeds is also referred to as recovering funds (or simply recovering them).

[0050] Figure 5 shows an example of the business scheme during the recovery phase of the funding system 1 of this embodiment.

[0051] In the business scheme of this embodiment, the funds provided to the user are recovered in the following procedure. 1: The fund management device 20 entrusts the seller with the collection of future accounts receivable R1 and fees. 2. When the seller provides a service to the buyer, accounts receivable are generated for the seller. An invoice for these accounts receivable is issued by the seller to the buyer. Payment for this invoice is made and deposited as sales proceeds into the seller's sales deposit account A1. 3. The fund management device 20 obtains payment information for invoices from the seller (for example, the transaction status of sales deposit account A1). 4. The fund management device 20 calculates the withdrawal amount W from the amount deposited into the sales deposit account A1 (i.e., the seller's sales). 5. The fund management device 20 notifies the account management system 40 of the withdrawal amount W. 6. The account management system 40 transfers the collected funds M1 of the withdrawal amount W from the sales deposit account A1 to the account of the fund provision management device 20.

[0052] Figure 6 shows an example of the operation flow during the recovery phase of the funding system 1 of this embodiment. (Step S441) The account management system 40 provides the fund management device 20 with invoice payment information D2 of the fund recipient (e.g., user). (Step S241) The deposit information acquisition unit 204 of the fund provision management device 20 acquires invoice deposit information D2 from the account management system 40. Invoice payment information D2 is information that shows the payment status from the buyer to the invoice presented by the seller (user) to the buyer.

[0053] In other words, the payment information acquisition unit 204 acquires invoice payment information D2, which shows the payment status from the buyer for the invoice presented by the seller (user) to the buyer.

[0054] In addition, payments from buyers may be made to the user's sales deposit account A1. In this case, the payment information acquisition unit 204 may acquire the payment status of sales deposit account A1 as invoice payment information D2.

[0055] In other words, the payment information acquisition unit 204 acquires the payment status of the user's sales payment account A1, which receives payments from buyers based on invoices, as invoice payment information D2.

[0056] (Step S242) The withdrawal amount calculation unit 205 of the fund provision management device 20 calculates the amount of the recovery amount M1 (i.e., the withdrawal amount W) to be deducted in advance before payment is made to the seller (user) from the sales amount of the store indicated by the invoice payment information D2.

[0057] In other words, the withdrawal amount calculation unit 205 calculates the withdrawal amount W, which is the amount of funds recovered from the user, based on the acquired invoice payment information D2.

[0058] The withdrawal amount W is calculated by multiplying the store's sales amount by a predetermined withdrawal rate. For example, if a store's sales amount for a predetermined period (e.g., 5 days) is 1 million yen and the withdrawal rate is 70%, the withdrawal amount W for the sales amount for that period will be calculated as 700,000 yen.

[0059] Here, the withdrawal amount calculation unit 205 may calculate the amount by multiplying the amount of accounts receivable based on the invoice payment information D2 described above by a predetermined withdrawal rate.

[0060] In other words, the withdrawal amount calculation unit 205 calculates the withdrawal amount W based on the amount of accounts receivable based on the acquired invoice payment information D2 and a predetermined withdrawal rate.

[0061] (Step S243) The withdrawal amount notification unit 206 of the fund provision management device 20 notifies the account management system 40 of the withdrawal amount W. (Step S442) The account management system 40 receives the withdrawal amount W.

[0062] In other words, the withdrawal amount notification unit 206 notifies the account management system 40, which processes the transfer from the sales deposit account A1, of the calculated withdrawal amount W.

[0063] (Step S443) The account management system 40 processes the transfer of the recovered funds M1. That is, the account management system 40 pays the recovered funds M1 of the withdrawal amount W to the operator of the funding system 1 (for example, the funding company).

[0064] In other words, the recovery unit 207 of the fund management device 20 recovers the calculated withdrawal amount W, M1, via the account management system 40.

[0065] The account management system 40 of this embodiment debits the collected amount W from the user's sales deposit account A1. The sales deposit account A1 is the user's account from which payments from buyers based on invoices are received.

[0066] In other words, the collection unit 207 collects the calculated withdrawal amount W by withdrawing it from the user's sales deposit account A1, which receives payments from buyers based on invoices.

[0067] More specifically, the collection unit 207 collects the amount that the account management system 40 has transferred from the sales deposit account A1, based on the withdrawal amount W notified to the account management system 40, as the withdrawal amount W.

[0068] (Step S244) The fund management device 20 confirms that the amount of the recovered funds M1, as determined by the account management system 40, matches the withdrawal amount W notified in step S243. In this case, the amount of the recovered funds M1 may not match the amount withdrawn W, for example, if the withdrawal fails due to insufficient funds in the account. In this case, the fund provision management device 20 may have a function to increase the insufficient amount in the next withdrawal or to issue a separate invoice for the insufficient amount. That is, the fund provision management device 20 includes a recovery control unit that increases the insufficient amount to be recovered in the next withdrawal or issues an invoice for the insufficient amount to be recovered. With the fund provision system 1 configured in this way, the recovery of recovered funds M1 can be facilitated. (Step S245) The fund management device 20 notifies the user terminal device 10 that the withdrawal has been completed. (Step S141) The user terminal device 10 displays on the display unit 11 that the withdrawal has been completed.

[0069] [Second Embodiment] Figure 7 shows an example of the device configuration of the fund provision system 1a and the functional configuration of the fund provision management device 20 according to the second embodiment. The fund provision system 1a comprises a user terminal device 10, a fund provision management device 20, a billing agency system 31, and an account management system 40.

[0070] The funding system 1a of this embodiment differs in that it includes a billing agency system 31 instead of the invoice issuance system 30 of the first embodiment described above. Components and operations similar to those of the funding system 1 of the first embodiment are denoted by the same reference numerals and their descriptions are omitted.

[0071] The billing agency system 31 is configured, for example, as a cloud server, and bills the buyer for the services provided by the user on behalf of the user. Similar to the invoice issuance system 30 described above, the billing agency system 31 can provide the fund provision management device 20 with past invoice transaction information D1.

[0072] [Business scheme for funding system 1a] Figure 8 shows an example of the business scheme at the funding stage of the funding system 1a of this embodiment.

[0073] In the business scheme of this embodiment, funding is provided to users in the following procedure. 1. The fund management device 20 collects past transaction data related to the user's invoices and customer reservation data from the billing agency system 31. 2: The fund management device 20 predicts the amount of money received from buyers to sellers (i.e., the user's future sales) for a predetermined period (for example, the next two years) based on the collected data. 3. Set up accounts receivable (future accounts receivable R1) for the projected future sales with the seller. 4. The fund management device 20 purchases future accounts receivable R1 from the seller. 5. The fund provision management device 20 provides funds to the seller as consideration for the future accounts receivable R1 that it has purchased.

[0074] [Operation Flow of Funding System 1a] Figure 9 shows an example of the operation flow of the pre-funding stage of the funding system 1a in this embodiment.

[0075] [(1) Setting of funding framework] (Step S351) The billing agency system 31 provides the past invoice transaction information D1 to the fund provision management device 20. Past invoice transaction information D1 refers to information on past transactions among the invoice sales information managed by the billing agency system 31. (Step S211) The past transaction information acquisition unit 201 of the fund provision management device 20 acquires past invoice transaction information D1 from the billing agency system 31. Step S212 is the same as in the first embodiment described above, so its explanation will be omitted.

[0076] [(2) Acceptance and review of applications for funding, (3) Provision of funding] The flow of these processes (steps S121, S221-S222, and S231-S131) ​​is the same as that of the first embodiment described above, so we will omit the explanation.

[0077] [(4) Deduction from sales proceeds] Let me explain how sales proceeds are deducted. Figure 10 shows an example of the business scheme during the recovery phase of the funding system 1a of this embodiment. In the business scheme of this embodiment, the funds provided to the user are recovered in the following procedure. 1. When a seller provides a service to a buyer, accounts receivable are generated for the seller. An invoice for these accounts receivable is issued by the seller to the buyer. Payment for this invoice is made and deposited as sales proceeds into an account managed by the billing agency system 31 (for example, the seller's sales deposit account A1). 2: The fund management device 20 obtains invoice payment information (for example, the transaction status of sales deposit account A1) from the billing agency system 31. 3. The fund management device 20 calculates the withdrawal amount W from the amount deposited into the sales deposit account A1 (i.e., the seller's sales). 4. The fund management device 20 notifies the billing agency system 31 of the withdrawal amount W. 5. The billing agency system 31 withdraws the recovered funds M1 of the withdrawal amount W to the account of the fund management device 20. The billing agency system 31 then withdraws the remaining balance M2, which is the sales minus the withdrawal amount W, to the seller's account (for example, sales deposit account A1).

[0078] Figure 11 shows an example of the operation flow during the recovery phase of the funding system 1a of this embodiment. (Step S341) The billing agency system 31 provides the fund management device 20 with invoice payment information D2 from the fund recipient (e.g., user). (Step S241) The deposit information acquisition unit 204 of the fund provision management device 20 acquires invoice payment information D2 from the billing agency system 31. Invoice payment information D2 is information that shows the payment status from the buyer to the invoice presented by the seller (user) to the buyer.

[0079] In other words, the payment information acquisition unit 204 acquires invoice payment information D2, which shows the payment status from the buyer for the invoice presented by the seller (user) to the buyer.

[0080] Furthermore, the billing agency system 31 can be described as a system that, on behalf of the seller, issues invoices to buyers.

[0081] In other words, the payment information acquisition unit 204 acquires invoice payment information D2, which shows the payment status from the buyer to the invoice presented by the seller (user) to the buyer, from the billing agency system 31, which handles the billing of the buyer on behalf of the seller.

[0082] (Step S242) The withdrawal amount calculation unit 205 of the fund provision management device 20 calculates the amount of the recovered funds M1 (i.e., the withdrawal amount W) to be deducted in advance from the seller's sales amount indicated by the invoice payment information D2 before the funds are withdrawn to the seller's account (for example, sales payment account A1).

[0083] In other words, the withdrawal amount calculation unit 205 calculates the withdrawal amount W, which is the amount of funds recovered from the user, based on the acquired invoice payment information D2.

[0084] Here, the withdrawal amount calculation unit 205 may calculate the amount by multiplying the amount of accounts receivable based on the invoice payment information D2 described above by a predetermined withdrawal rate.

[0085] In other words, the withdrawal amount calculation unit 205 calculates the withdrawal amount W based on the amount of accounts receivable based on the acquired invoice payment information D2 and a predetermined withdrawal rate.

[0086] (Step S243) The withdrawal amount notification unit 206 of the fund provision management device 20 notifies the billing agency system 31 of the withdrawal amount W.

[0087] In other words, the withdrawal amount notification unit 206 notifies the billing agency system 31 of the calculated withdrawal amount W.

[0088] (Step S342) The billing agency system 31 receives the withdrawal amount W from the fund provision management device 20. (Step S343) The billing agency system 31 withdraws the remaining balance M2, obtained by subtracting the withdrawal amount W from the store's sales amount, to the account management system 40.

[0089] (Step S441) The account management system 40 deposits funds into the user's financial institution account (for example, sales deposit account A1).

[0090] (Step S344) The billing agency system 31 performs a transfer of the collected funds M1. That is, the billing agency system 31 withdraws the collected funds M1 of the withdrawal amount W to the management account of the fund provision management device 20.

[0091] In other words, the collection unit 207 collects the withdrawal amount W, which the billing agency system 31 deducts from the amount received from the buyer, as the amount of funds to be recovered. In other words, the recovery unit 207 of the fund management device 20 recovers the calculated withdrawal amount W via the billing agency system 31.

[0092] (Step S244) The fund management device 20 confirms that the amount of the collected funds M1 deposited from the billing agency system 31 matches the withdrawal amount W notified in step S243. (Step S245) The fund management device 20 notifies the user terminal device 10 that the withdrawal has been completed. (Step S141) The user terminal device 10 displays on the display unit 11 that the withdrawal has been completed.

[0093] In addition, in step S343 described above, the transfer unit 208 of the fund management device 20 may be configured to transfer the remaining balance M2 to the sales deposit account A1 on behalf of the billing agency system 31. In other words, the transfer unit 208 transfers the remaining amount (remaining balance M2) to the user, which is the amount received from the buyer by the billing agency system 31 minus the withdrawal amount W.

[0094] [Third Embodiment] Figure 12 shows an example of the device configuration of the fund provision system 1b and the functional configuration of the fund provision management device 20 according to the third embodiment. The fund provision system 1b comprises a user terminal device 10, a fund provision management device 20, an order system 32, and an account management system 40.

[0095] The funding system 1b of this embodiment differs in that it includes an order system 32 instead of the billing agency system 31 of the second embodiment described above. Components and operations similar to those of the funding system 1 of the first embodiment and the funding system 1a of the second embodiment are denoted by the same reference numerals and their descriptions are omitted.

[0096] The order system 32 is configured, for example, as a cloud server, and accepts orders from buyers for services provided by the seller (user). Here, an order includes various commercial transactions such as the purchase of goods or services provided by the user, reservations for purchases, subscriptions, and payment of fees.

[0097] For example, if the user operates a business such as accommodation or food service, the ordering system 32 accepts reservations for rooms or seats from buyers (e.g., hotel guests or restaurant customers).

[0098] The invoice issuance system 30 of the first embodiment and the billing agency system 31 of the second embodiment described above provided the fund management device 20 with past invoice transaction information D1. The order system 32 provides the fund management device 20 with order information D3. Order information D3 is information that shows the status of a buyer's order for goods or services provided by the seller.

[0099] The order system 32 may be operated by the organization that operates the funding system 1b, or it may be operated by a third party other than said organization. In this example, the order system 32 will be described as being operated by a third party other than said organization. In this case, the order system 32 can also be said to be a reservation platform (PF) operated by another company, that is, a third-party reservation PF.

[0100] [Business scheme for funding system 1b] Figure 13 shows an example of the business scheme at the funding stage of the funding system 1b of this embodiment.

[0101] In the business scheme of this embodiment, funding is provided to users in the following procedure. 1. The fund management device 20 collects past transaction data related to the user's invoice and customer reservation data from the order system 32. 2: The fund management device 20 predicts the amount of money received from buyers to sellers (i.e., the user's future sales) for a predetermined period (for example, the next two years) based on the collected data. 3. Set up accounts receivable (future accounts receivable R1) for the projected future sales with the seller. 4. The fund management device 20 purchases future accounts receivable R1 from the seller. 5. The fund provision management device 20 provides funds to the seller as consideration for the future accounts receivable R1 that it has purchased.

[0102] [Operational flow of Funding System 1b] Figure 14 shows an example of the operation flow of the pre-funding stage of the funding system 1b of this embodiment.

[0103] [(1) Setting of funding framework] (Step S361) The order system 32 provides order information D3 to the fund management device 20. As described above, order information D3 is information indicating the status of a buyer's order for goods or services provided by the seller user. This order information D3 includes past order history. (Step S261) The order information acquisition unit 210 of the fund provision management device 20 acquires order information D3 (past order history) from the order system 32.

[0104] (Step S262) The fund management device 20 estimates the user's sales volume based on the past order history indicated by the order information D3. The fund management device 20 calculates a fund allocation limit corresponding to the estimated user's sales volume.

[0105] [(2) Acceptance and review of applications for funding, (3) Provision of funding] The flow of these processes (steps S121, S221-S222, and S231-S131) ​​is the same as that of the first embodiment described above, so we will omit the explanation.

[0106] [Identifying the recipient's bank account] The funding system 1b of this embodiment is configured to allow the user to select the financial institution account to which the funds will be provided in step S431 (see Figure 4) described above.

[0107] For example, a user can select their deposit account A2, which is registered in the order system 32, or a newly opened account (new account A3) at a financial institution to receive the funds provided.

[0108] In this case, the operation reception unit 211 receives an operation from the user to select either the user's deposit account registered in the order system 32, which receives orders from buyers for goods or services provided by the seller, or another account, as the financial institution account to which the funds provided to the user will be paid as consideration for purchasing future accounts receivable R1 that will be paid to the seller by the buyer. The account information acquisition unit 212 acquires account information D4 from the order system 32 to identify deposit account A2 when deposit account A2 is selected.

[0109] In this case, the Funding Unit 203 pays the funds to the user to the account selected by the user's selection operation.

[0110] In this case, the account information acquisition unit 212 of the fund management device 20 may be configured to acquire account information for the user's deposit account A2 registered in the order system 32 by scraping or by using an API (Application Programming Interface).

[0111] In other words, the account information acquisition unit 212 acquires account information by reading images or other information presented by the order system 32.

[0112] Furthermore, the account information acquisition unit 212 acquires account information via the API (Application Programming Interface) provided by the order system 32.

[0113] [(4) Deduction from sales proceeds] Let me explain how sales proceeds are deducted. Figure 15 shows an example of the business scheme during the recovery phase of the funding system 1b of this embodiment. In the business scheme of this embodiment, the funds provided to the user are recovered in the following procedure.

[0114] 1. When a seller provides a service to a buyer, accounts receivable are generated for the seller. 2: The fund management device 20 obtains deposit information (for example, the transaction status of deposit account A2) from the order system 32. 3. The fund management device 20 calculates the withdrawal amount W from the amount deposited into deposit account A2 (i.e., the seller's sales). 4. The fund management device 20 notifies the order system 32 of the withdrawal amount W. 5. The order system 32 withdraws the recovered funds M1 (the withdrawal amount W) to the account of the fund management device 20. The order system 32 then withdraws the remaining balance M2 (sales minus the withdrawal amount W) to the seller's account (for example, sales deposit account A1).

[0115] Figure 16 shows an example of the operation flow during the recovery phase of the funding system 1b of this embodiment. (Step S371) The order system 32 provides the order information D3 of the fund recipient (e.g., user) to the fund management device 20. (Step S271) The deposit information acquisition unit 204 of the fund provision management device 20 acquires order information D3 from the order system 32. This order information D3 includes information indicating the status of a buyer's order for goods or services provided by the seller user. Information indicating the status of an order is, for example, payment information for services provided by the user to the buyer.

[0116] In other words, the order information acquisition unit 210 acquires order information D3, which indicates the status of a buyer's order for goods or services provided by the seller (user), from the order system 32 that receives orders from buyers.

[0117] (Step S242) The withdrawal amount calculation unit 205 of the fund provision management device 20 calculates the amount of the recovery amount M1 (i.e., the withdrawal amount W) to be deducted in advance before depositing the sales proceeds to the user, based on the settlement information indicated by the order information D3.

[0118] In other words, the withdrawal amount calculation unit 205 calculates the withdrawal amount W, which is the amount of funds recovered from the user, based on the acquired order information D3.

[0119] Here, the withdrawal amount calculation unit 205 may calculate the amount by multiplying the amount of accounts receivable based on the order information D3 described above by a predetermined withdrawal rate.

[0120] In other words, the withdrawal amount calculation unit 205 calculates the withdrawal amount W based on the amount of accounts receivable based on the acquired order information D3 and a predetermined withdrawal rate.

[0121] (Step S243) The withdrawal amount notification unit 206 of the fund provision management device 20 notifies the order system 32 of the withdrawal amount W.

[0122] In other words, the withdrawal amount notification unit 206 notifies the order system 32 of the calculated withdrawal amount W.

[0123] (Step S342) The order system 32 receives the withdrawal amount W from the fund provision management device 20. (Step S343) The order system 32 withdraws the remaining balance M2, obtained by subtracting the withdrawal amount W from the store's sales amount, to the account management system 40.

[0124] (Step S441) The account management system 40 deposits funds into the user's financial institution account (for example, sales deposit account A1). The fund management device 20 may also include a transfer unit 208 that transfers the remaining balance M2, obtained by subtracting the withdrawal amount W from the store's sales amount, to the user.

[0125] (Step S344) The order system 32 performs the transfer process for the recovered funds M1. That is, the order system 32 withdraws the withdrawal amount W to the operator of the fund provision system 1 (for example, the fund provision company).

[0126] In other words, the recovery unit 207 recovers the withdrawal amount W, which the order system 32 deducts from the amount received from the buyer, as the amount of funds recovered.

[0127] (Step S244) The fund management device 20 confirms that the amount of the recovered funds M1 deposited from the order system 32 matches the withdrawal amount W notified in step S243. (Step S245) The fund management device 20 notifies the user terminal device 10 that the withdrawal has been completed. (Step S141) The user terminal device 10 displays on the display unit 11 that the withdrawal has been completed.

[0128] [Differentiation] Figure 17 shows an example of a business scheme at the funding stage in a modified version of the funding system 1b of this embodiment.

[0129] In this modified business scheme, funding is provided to users in the following procedure. That is, funding is provided to users in the same procedure as the funding stage of the third embodiment of the business scheme.

[0130] 1. The fund management device 20 collects past transaction data related to the user's invoice and customer reservation data from the order system 32. 2: The fund management device 20 predicts the amount of money received from buyers to sellers (i.e., the user's future sales) for a predetermined period (for example, the next two years) based on the collected data. 3. Set up accounts receivable (future accounts receivable R1) for the projected future sales with the seller. 4. The fund management device 20 purchases future accounts receivable R1 from the seller. 5. The fund provision management device 20 provides funds to the seller as consideration for the future accounts receivable R1 that it has purchased.

[0131] Figure 18 shows an example of a business scheme in the recovery phase in a modified version of the funding system 1b of this embodiment. In this modified business scheme, the funds provided to users are recovered through the following procedure.

[0132] 1: The fund management device 20 entrusts the seller with the collection of future accounts receivable R1. 2. When the seller provides a service to the buyer, accounts receivable are generated for the seller. Payment for this service is made and deposited as sales proceeds into the seller's sales deposit account A1. 3. The fund management device 20 obtains deposit information into the sales deposit account A1 via the order system 32. 4. The fund management device 20 calculates the withdrawal amount W from the amount deposited into the sales deposit account A1 (i.e., the seller's sales). 5. The fund management device 20 notifies the seller of the withdrawal amount W. 6. The seller withdraws the collected funds M1, which is the withdrawal amount W, to the account of the fund management device 20. In other words, the fund management device 20 collects the collected funds M1 based on future accounts receivable R1.

[0133] This modified version differs from the third embodiment described above in that it receives the collected funds M1 from the user's sales proceeds without going through the source of the order information D3 (order system 32).

[0134] In this modified example, in step S343 described above, the fund management device 20 transfers the remaining balance M2 to the sales deposit account A1 on behalf of the order system 32.

[0135] In other words, the recovery unit 207 recovers the calculated withdrawal amount W by withdrawing it from the user's deposit account A2, from which the buyer makes the payment for the order. In this case, the transfer unit 208 transfers the remaining amount (remaining balance M2) to the user, which is the amount received from the buyer by the order system 32 minus the withdrawal amount W.

[0136] As described above, the funding system 1 of this embodiment (funding system 1a, funding system 1b, and modified versions; hereinafter collectively referred to as the funding system) provides various business schemes according to the user's business type. With a funding system configured in this way, convenience for the user can be improved.

[0137] Although embodiments of the present invention have been described in detail above with reference to the drawings, the specific configuration is not limited to these embodiments, and design modifications and the like are also included within the scope of the gist of the present invention. For example, a computer program to implement the functions of each of the above-mentioned devices may be recorded on a computer-readable recording medium, and the program recorded on this recording medium may be loaded into a computer system and executed. The term "computer system" here may include hardware such as an operating system and peripheral devices.

[0138] Furthermore, "computer-readable recording media" refers to writable non-volatile memory such as flexible disks, magneto-optical disks, ROMs, and flash memory, portable media such as DVDs (Digital Versatile Discs), and storage devices such as hard disks built into computer systems. Furthermore, "computer-readable recording media" also includes volatile memory (such as DRAM (Dynamic Random Access Memory)) within computer systems that act as servers or clients when programs are transmitted via networks such as the Internet or communication lines such as telephone lines, which retain programs for a certain period of time.

[0139] Furthermore, the above program may be transmitted from a computer system that stores the program in a memory device or the like to another computer system via a transmission medium or by transmission waves within the transmission medium. Here, the "transmission medium" used to transmit the program refers to a medium that has the function of transmitting information, such as a network (communication network) like the Internet or a communication line (communication line) like a telephone line. Furthermore, the above program may be intended to implement some of the functions described above. It may also be a so-called differential file (differential program) that can implement the aforementioned functions in combination with programs already recorded in the computer system. [Explanation of Symbols]

[0140] 1... Funding system, 10... User terminal device, 20... Funding management device, 30... Invoice issuance system, 31... Billing agency system, 32... Ordering system, 40... Account management system

Claims

1. A past transaction information acquisition unit acquires invoice past transaction information that shows the past transaction status between the seller and the buyer based on the invoice presented by the seller (user) to the buyer, Based on the acquired past transaction information of the invoice, the identification unit identifies a specific invoice that corresponds to a future accounts receivable that is the subject of funding, A funding department provides funds to the user as consideration for purchasing the future accounts receivable of the specified invoice, A funding system equipped with these features.

2. The specified part is, Identify the specific invoice based on the combination of seller, buyer, and frequency of the invoice as indicated by the aforementioned past transaction information. The funding system according to claim 1.

3. The aforementioned past transaction information acquisition unit is: The invoice past transaction information is obtained from the invoice issuance system used by the aforementioned user. The funding system according to claim 1.

4. The Invitation Notification Unit sends an invitation notification to businesses registered in the invoice issuance system that manages the aforementioned past transaction information for invoices, inviting them as potential factoring candidates. The funding system according to claim 1, further comprising:

5. On the computer, Obtaining invoice transaction information that shows the past transaction status between the seller and the buyer based on the invoice presented by the seller (user) to the buyer, Based on the acquired past transaction information of the invoices, identify specific invoices that correspond to future accounts receivable that are the subject of funding, In exchange for purchasing the future accounts receivable of the specified invoice, the user will be provided with funds. A program to execute.

Images