JP7349703B2 - Unsecured funding system - Google Patents

Description

The present invention relates to an unsecured funding system that converts a portion of store sales expected to occur in the future into bonds and purchases undetermined future trade receivables. The present invention relates to an unsecured funding system that includes a funding system server that designs undetermined future sales bonds for stores based on commercial transaction data and proposes a purchase plan for the designed bonds.

As a measure to improve the store's cash flow, the inventor converted undefined future credit receivables based on the sales performance of credit card payments over a predetermined period into bonds, thereby influencing short-term sales fluctuations of member stores without collateral. The company proposes a funding system for credit card affiliated stores that is not affected by fluctuations in sales, allowing stores to secure an abundance of liquid funds on hand without being affected by fluctuations in sales (Patent Document (see 1).

In addition, although the above proposal is useful for stores with a high credit card usage rate, it has the disadvantage that funding cannot be used effectively at stores that mainly accept payment methods other than credit cards, such as cash payments and various electronic money payments. Because the inventor had the functions of the finalized sales aggregation department, which aggregates the finalized sales after the store's commercial transactions have been settled and deposited, and calculates the finalized sales by period, and the function of the finalized sales amount calculation department that calculates the finalized sales by period, and the separation of payments to the funding business, the inventor Using a cash register or ticket vending machine that has the function of a separate payment setting unit that calculates the payment amount and settlement and/or reserve amount to be deposited with the separate payment agency, the future is undetermined based on sales results for a predetermined period. We are proposing an unsecured funding system that converts trade receivables into bonds and supports stores so that they are not affected by short-term fluctuations in sales of member stores. At the main store, it is possible to secure an abundance of liquid funds on hand without being affected by fluctuations in sales (see Patent Document 2).

In recent years, in addition to traditional cash and credit card payments, payment methods for purchasing and selling products at stores have expanded to include various electronic money payments, cash on delivery at online shops, convenience store payments, bank transfer payments, and including the product price in the mobile phone payment. There are a wide variety of payment methods available, including carrier payments. Furthermore, in recent years, virtual currencies such as Bitcoin, which digitize monetary value, have been used directly to settle product sales.
Although POS systems, which are the core of retail distribution in stores, have been designed to accommodate the diversification of payment methods, existing systems such as virtual currency cannot handle this, and the aforementioned unsecured funding system has been developed. It is becoming difficult to calculate the fixed sales amount for a specified period of time for a store to be used, making it difficult to utilize the funding system.

In addition, in an unsecured funding system that converts undetermined future receivables into bonds based on confirmed sales performance over a predetermined period, sales are not recognized as sales results until sales are settled, so if sales suddenly occur, The problem was that growing stores were unable to raise funds based on their upcoming sales.

International Patent Publication No. 2014/024520 Japanese Patent Application Publication No. 2016-164717

The present invention has been made in view of the above-mentioned conventional problems, and an object of the present invention is to create a bond purchase plan that converts undetermined future sales receivables of stores into bonds based on daily sales information from stores. We provide an unsecured funding system that is equipped with a funding system center server that can create and propose to stores, and an unsecured funding system that can support funding for stores that adopt a variety of payment methods, including virtual currency payments. It's about doing.

An unsecured funding system according to one aspect of the present invention made to achieve the above object includes a store management server used by a store operator of a funding system member store, and a funding operator that operates the funding system. A funding system center server to be used is connected via a communication network, and is an unsecured funding system for purchasing undetermined future receivables of the funding system member stores, wherein the store management server is connected to the The funding system center server includes a store management server communication unit that transmits commercial transaction information of a funding system member store to the funding system center server, and the funding system center server uses the transmitted commercial transaction information of the funding system member store. provisional sales calculation means for calculating the expected deposit amount and totaling the results to create a provisional sales list of the funding system member stores for each predetermined period; and a provisional sales list created by the provisional sales calculation means. and a bond conversion specification design means for creating a bond purchase plan in which undetermined future trade receivables of the funding system member stores are converted into bonds using The provisional sales calculation means updates the provisional sales list using the commercial transaction information of the funding system member stores received after the creation of the provisional sales list, and the bonding specification design means updates the provisional sales An unsecured funding system characterized in that when a high list is updated, a purchase plan for bonds that convert undetermined future trade receivables of the funding system member stores into bonds is updated and transmitted to the store management server.

The transaction information of the funding system member store sent from the store management server includes physical store transaction information including the payment method and name of the payment processing company for transaction payments conducted at the physical store, and transaction information conducted at the online shop. It is preferable to include either or both of the online shop transaction information including the payment method of payment, the name of the payment processing company, and the amount of virtual currency received in the payment of the product transaction, and the store management server is installed at the physical store. It is preferable that the terminal is connected to a physical store terminal that transmits the physical store transaction information and/or an online shop server that transmits the online shop transaction information of the online shop.

The physical store terminal may be a vending machine having a communication function to the store management server, or a parking payment machine having a communication function to the store management server.

The provisional sales amount calculation means of the funding system center server includes a physical store scheduled deposit amount calculation unit that calculates the scheduled deposit amount for physical store payments, and an online shop that calculates the scheduled deposit amount for online shop payments excluding virtual currency payments. Estimated deposit amount calculation unit, which calculates the planned deposit amount by converting the virtual currency amount received through virtual currency settlement to the virtual currency market price at the time of the transaction and subtracting the expected conversion fee from the converted amount. It is preferable to have a portion.

According to the unsecured funding system of the present invention, a bond purchase plan that converts future receivables into bonds is quickly created based on daily sales information, so funding system member stores can quickly raise funds. In addition, funding system member stores will be able to secure an abundance of liquid funds on hand without being affected by fluctuations in sales due to payment methods or seasonal fluctuations, and will be able to use those funds to invest in new businesses. It can be used for purchasing, capital investment, etc., giving you more leeway in your cash flow.

FIG. 1 is a diagram for explaining a scheme of an unsecured funding system according to an embodiment of the present invention. FIG. 1 is a block diagram for explaining the configuration of an unsecured funding system using a system center server according to an embodiment of the present invention. FIG. 3 is a block diagram for explaining the configuration of the system center server shown in FIG. 2. FIG.

Hereinafter, a specific example of a form for implementing the unsecured funding system of the present invention will be described in detail with reference to the drawings.
FIG. 1 is a diagram for explaining the scheme of the unsecured funding system of this embodiment.

This scheme is premised on the conclusion of a debt purchase price transfer contract between the store operator 20 of the funding system member store 10 and the funding operator 30.
The flow of this scheme will be explained with reference to FIG. The store operator 20 of the funding system member store 10 transmits to the funding operator 30 commercial transaction information regarding the member store's daily product transactions.
Transmission of commercial transaction information is performed at predetermined intervals, preferably on a daily basis. The commercial transaction information includes transaction date and time, product name, product selling price, payment method, and name of payment handling business such as credit card company. The funding business operator 30 calculates provisional sales from the transmitted commercial transaction information, and provides a financial product that converts undetermined future receivables of the funding system member store 10 into bonds based on the cumulative total of provisional sales over a certain period. is designed and a bond purchase plan in which future trade receivables corresponding to the funding system member store 10 are turned into bonds is transmitted to the funding system member store 10.

The provisional sales here means the estimated deposit amount after deducting the prescribed fees of the payment agent, handling financial company, card company, etc. from the product's sales price, or the sales price in virtual currency at the time of the transaction. This refers to the amount obtained by subtracting a predetermined conversion fee from the amount converted into the amount of commonly used currency based on the market price.
The store operator 20 of the funding system member store 10, if there is a plan that the funding operator 30 would like to purchase from among the transmitted bond purchase plans that convert undetermined future trade receivables into bonds, the store operator 20 of the funding system member store 10 The store's undetermined future trade receivable bonds are sold to the funding business operator 30 at the price and redemption conditions set in the bond purchase plan, and the funding business operator 30 sells them to the store business operator 20 of the funding system member store 10. Pay the bond purchase price for future trade receivables. Thereby, the store operator 20 of the funding system member store 10 secures necessary liquid funds on hand without collateral.

The store operator 20 of the funding system member store 10 transmits commercial transaction data information during the period to the funding operator 30 when the sold future receivables are converted into bonds. The funding business operator 30 calculates the scheduled finalized sales from the commercial transaction information during the period in which the future trade receivables are converted into bonds, and calculates the redemption amount of the future trade receivables of the funding system member store 10 based on this. The store operator 20 of the funding system member store 10 is notified.
The store operator 20 of the funding system member store 10 pays the notified redemption money to the funding operator 30.
Redemption of bonds paid to the funding business operator 30 continues until the face value of the bonds purchased by the funding business operator 30 matches the cumulative amount of redemption received by the funding business operator 30.

FIG. 2 is a block diagram for explaining the configuration of an unsecured funding system using a system center server according to this embodiment.
As shown in FIG. 2, the unsecured funding system according to the present embodiment includes a store management server 200 used by the store operator 20 of the funding system member store 10 and a funding system center server 300 used by the funding operator 30. Become.

In this embodiment, the store management server 200 includes a physical store terminal 100 that is installed in a physical store and transmits physical store transaction information to the store management server 200, and an online shop transaction information of an online shop managed by a store operator 20. It has a store management server communication section 210 that is connected to the online shop server 150 that transmits data to the management server 200 and transmits physical store transaction information and online shop transaction information to the funding system center server 300 as funding system member store transaction information.
The physical stores mentioned here include vending machines and parking payment machines in unmanned parking lots.

The physical store terminal 100 is a cash register installed in a physical store, a terminal that operates in conjunction with the cash register, a vending machine, or a parking payment machine in an unmanned parking lot, and is used to handle product transactions and payments performed at the physical store. The information is sent to the store management server 200 one by one as actual store transaction information. The physical store transaction information includes transaction date and time, product name, product sales price, payment method, and name of payment handling business such as credit card company.
The physical store terminal 100 is equipped with a card reader compatible with various types of electronic money such as credit cards and debit cards, and a reading or display device for QR codes (registered trademarks) and barcodes compatible with various cashless payment methods. It is connected to the host computer of a company or electronic money service company, or to the host computer of a payment agent, so that payments can be made by credit card or various electronic money.

The online shop server 150 is a computer used to manage orders and payments for commercial transactions at the online shop run by the store operator 20, and has a virtual currency wallet unit 155 that stores virtual currency received in virtual currency payments.
The online shop server 150 sends information on product transactions and payments made in the online shop one by one to the store management server 200 as online shop transaction information. Online shop transaction information includes transaction date and time, product name, product sales price, amount of virtual currency received in payment of product transaction, payment method, and name of payment handling business such as credit card company.
In this embodiment, the online shop server 150 is equipped with a virtual currency wallet section 155 that can receive and store virtual currency in addition to payments such as cash-on-delivery payments by carriers and convenience store payments that are commonly used in online shops. Payment can be made.

The store management server 200 is a computer that manages the overall business of the funding system member store 10, and stores physical store transaction information and/or online shop transaction information transmitted from the physical store terminal 100 and the online shop server 150 for a predetermined period of time. It has a store management server communication section 310 that totals each transaction and transmits it to the funding system center server 300 as funding system member store transaction information. Funding system member store transaction information includes the transaction date and time, product name, product sales price, amount of virtual currency received for product transaction settlement, payment method, credit card company, etc. that handles payment for each product that was traded. Contains information on the person's name.

The store management server communication section 310 connects with the host computer of the funding system member store 10's main bank, payment and/or separate payment agent, payment service provider, etc., and connects with the funding system center server 300. It manages the overall communications of the funding system member stores 10, including connections, mail server operations, FTP processing, telephone, FAX, and dedicated line communication processing including LAN.

A funding system center server 300 used by a funding business operator 30 is connected to a store management server 200 via a communication network such as a public line network or a private line, and includes a center server communication section 305, a database 310, and provisional sales calculation means. 320, bond specification design means 330, and redemption management means 340.
The provisional sales amount calculation means 320 calculates the expected deposit amount using the funding system member store transaction information transmitted from the store management server 200, aggregates this, and creates a provisional sales amount list for each predetermined period, The bond conversion specification design means 330 uses the provisional sales list created by the provisional sales calculation means 320 to create a bond purchase plan that converts undetermined future trade receivables of the funding system member stores 10 into bonds, and sends them to the center. The redemption management means 340 transmits the information to the store management server 200 via the server communication unit 305, and uses the provisional sales list created by the provisional sales calculation means 320 to calculate future sales receivables of the funding system member store 10. The redemption amount is calculated and transmitted to the store management server 200 via the center server communication section 305.

The store management server 200 and the system center server 300 can be configured using a commercially available PC (personal computer), etc., and include a CPU (central control unit), memory, and a storage device such as a hard disk that constitutes a database. , a display device for displaying images, text, etc. for management purposes, input devices such as a keyboard and mouse, and other input devices related to communication, and their configuration drawings will be omitted. Furthermore, detailed explanations of each component that functions by executing a software program using these components will be omitted.

FIG. 3 is a block diagram for explaining the configuration of the funding system center server 300 shown in FIG. 2. As shown in FIG.
With reference to FIG. 3, the configuration, function, and operation of each part of the provisional sales amount calculation means 320, bond formation specification design means 330, and redemption management means 340 of the system center server 300 according to this embodiment will be explained.

(Calculation of provisional sales)
The provisional sales amount calculation unit 320 includes a physical store payment scheduled payment amount calculation unit 321 that calculates the scheduled payment amount for physical store payment, and an online shop payment scheduled payment amount calculation unit that calculates the scheduled payment amount for online shop payment excluding virtual currency payment. section 322, a virtual currency settlement scheduled deposit amount calculation section 323 that converts the virtual currency amount received through virtual currency settlement to the virtual currency market price at the time of the transaction, and calculates the scheduled deposit amount by subtracting the scheduled conversion fee from the converted amount; A scheduled deposit amount list creation unit 324 that arranges and lists scheduled deposit amounts for each commercial transaction in order of transaction date and time; a redemption target transaction data selection unit 325 that selects redemption target transaction data from the scheduled deposit amount list; It has a redemption target scheduled deposit amount list creation unit 326 that lists scheduled deposit amounts, and a period-specific provisional sales amount calculation unit 327 that totals the amounts in the scheduled deposit amount list for each predetermined period and creates a period-specific provisional sales amount list.

The planned deposit amount calculation unit 321 receives the funding system member store transaction information from the store management server 200, and calculates the scheduled deposit amount for the actual store payment of the funding system member store based on a predetermined amount for each payment method. A planned deposit amount is calculated from the sales price of each commercial transaction using a calculation method, and a list of scheduled deposit amounts for actual store settlement is created by arranging the scheduled deposit amounts of the commercial transactions in order of transaction occurrence date and time.
At physical stores, in addition to cash payments, payments are made using various cashless payment methods. Examples of cashless payment methods include prepaid electronic money that is charged with the amount to be used in advance, real-time pay debit cards and QR codes (registered trademarks), mobile wallets such as NFC, and post-pay credit cards. It will be done.

The actual store payment scheduled deposit amount calculation unit 322 includes a list of handling fees for cashless payment methods with which the funding system member store 10 has contracted. The physical store cashless payment method handling fee list is created based on an application from the funding system member store 10 when joining the funding system.
The estimated deposit amount for actual store payments is calculated by subtracting the cashless payment method handling fee from the sales price of the commercial transaction.
The list of planned deposit amount for physical store payment includes the following items: transaction date and time, product name, product sales price, virtual currency amount received, payment method, name of cashless payment processing company, cashless payment processing fee, and scheduled deposit amount. included.
When the physical store payment scheduled deposit amount calculation unit 321 completes the creation of the physical store payment scheduled deposit amount list, it transmits the physical store payment scheduled deposit amount list to the scheduled deposit amount list creation unit 324, and the received funding system affiliate The store transaction information is transmitted to the online shop payment scheduled payment amount calculation unit 322.

The online shop payment scheduled receipt amount calculation unit 322 receives the funding system member store transaction information from the physical store payment scheduled payment amount calculation unit 321, and receives the funding system member store transaction information from the online shop payment amount calculation unit 322. A scheduled deposit amount is calculated, and a list of scheduled deposit amounts for online shop settlement is created by arranging the scheduled deposit amounts for commercial transactions in the order of transaction occurrence date and time.
At online shops, payments can be made using various payment methods in addition to credit card payments. Payment methods used at online shops include credit card payment, debit card payment, cash on delivery method where the carrier receives the payment in exchange for the arrival of the product, and convenience store payment based on the number issued by the convenience store collection agency. , payment slip-style deferred payment where the payment agency collects the payment, carrier payment where the product price is included in the monthly mobile phone bill when shopping on a mobile device such as a smartphone, and a bank where the product price is transferred from the bank to a designated account. Examples include transfers.

The online shop payment scheduled deposit amount calculation unit 324 includes a list of handling fees for the online shop payment means with which the funding system member store 10 has contracted. The online shop payment method handling fee list is created based on an application from the funding system member store 10 when joining the funding system.
The estimated online shop deposit amount is calculated by subtracting the online shop payment method handling fee from the sales price of the transaction.
The online shop payment scheduled deposit amount list includes the following items: transaction date and time, product name, product sales price, amount of virtual currency received, payment method, name of online shop payment method handling business, online shop payment method handling fee, and scheduled deposit amount. included.

When the online shop payment scheduled deposit amount calculation unit 322 finishes creating the online shop payment scheduled deposit amount list, it transmits the online shop payment scheduled deposit amount list to the scheduled deposit amount list creation unit 324, and the transmitted funding system The member store transaction information is transmitted to the virtual currency payment scheduled deposit amount calculation unit 323.

The virtual currency payment scheduled deposit amount calculation unit 326 calculates the scheduled deposit amount based on the amount when the received virtual currency amount in the virtual currency payment is converted into the normally used currency, and calculates the scheduled deposit amount for the virtual currency receipt case based on the virtual currency receipt date and time. Arrange them in order to create a list of scheduled virtual currency payment payments.
The virtual currency settlement scheduled deposit amount calculation unit 326 includes a virtual currency market price list in which the market prices of virtual currencies used for settlement by the funding system member store 10 are listed. The virtual currency market price list is obtained by the funding system member store 10 obtaining market prices that fluctuate from moment to moment from the website of the virtual currency exchange used for settlement, and recording the market prices at predetermined time intervals.
To calculate the expected virtual currency deposit amount, based on the virtual currency market value list, convert the virtual currency amount received in the settlement of the product transaction to the virtual currency market price at the time of receiving the virtual currency, and then subtract the expected conversion fee from the converted amount. is required.

The list of scheduled virtual currency payment deposits includes the date and time of receipt, product name, product selling price, amount of virtual currency received, name of virtual currency exchange, virtual currency market price at the time of virtual currency receipt, estimated virtual currency conversion fee amount, and converted amount. Contains an item for the expected deposit amount.
When the online shop payment scheduled deposit amount calculation unit 322 completes the creation of the virtual currency payment scheduled deposit amount list, it transmits the virtual currency payment scheduled deposit amount list and the funding system member store transaction information to the scheduled deposit amount list creation unit 324. do.

The planned deposit amount list creation unit 324 generates the schedule for each list if the physical store payment scheduled deposit amount list, the online shop payment scheduled deposit amount list, the virtual currency payment scheduled deposit amount list, and the funding system member store transaction information are transmitted. A deposit schedule list in which deposit amounts are arranged in date and time order is created, and the deposit schedule list and funding system member store transaction information are stored in the database 310.
The scheduled deposit list includes the following items: transaction date and time, product name, product selling price, amount of virtual currency received, payment method, name of payment service provider, and scheduled deposit amount.
The deposit schedule list receives funding system member store transaction information transmitted from the store management server 200 from time to time, and is updated every time the scheduled deposit amount corresponding to the transaction is calculated. When the expected deposit amount calculation unit 322 creates a scheduled deposit list, it transmits a notification of creation of a scheduled deposit list to the period-by-period provisional sales amount calculation unit 327, and when it updates the scheduled deposit amount in the scheduled deposit list, it transmits a planned deposit amount update notification. . Creation of the deposit schedule list continues until the funding system member store 10 withdraws from the funding system.

The redemption target transaction data selection unit 325 determines whether the transaction date and time of the funding system member store transaction information stored in the database 310 is the start date of the bond conversion period for future trade receivables sold by the funding system member store 10. If so, the scheduled deposit amounts for commercial transactions after the start date of the bond period are extracted from the deposit schedule list stored in the database 310 to create a redemption target deposit schedule list.

The redemption target transaction data sorting unit 325 sorts the scheduled payment transaction data in the created redemption target payment schedule list into redemption scheduled payment transaction data, redemption target final payment scheduled transaction data, and non-redemption scheduled payment transaction data, and performs redemption. The commercial transaction data that is not eligible for redemption is removed from the list of scheduled deposits, and the list of scheduled deposits that are eligible for redemption is stored in the database 310.
The redemption target deposit schedule list is updated every time funding system member store transaction information is transmitted from the store management server 200 and the scheduled deposit amount corresponding to the transaction is calculated until the bond redemption is completed.

The method of selecting transaction data to be redeemed is to accumulate the transaction amount scheduled to be deposited in chronological order, regardless of settlement or deposit timing, for the transaction data scheduled to be deposited after the start of the bonding target period of the funding system member stores 10, and to calculate the cumulative amount. The scheduled deposit transaction data at the time when the amount multiplied by the bond redemption ratio is equal to or greater than the bond face value is the final scheduled payment transaction data for redemption, and the scheduled deposit is when the cumulative amount multiplied by the bond redemption ratio is less than the bond face value. The commercial transaction data is set as the scheduled payment transaction data eligible for redemption, and the scheduled transaction transaction data subsequent to the final scheduled payment transaction data is set as the scheduled payment transaction data not eligible for redemption.
When the redemption target transaction data selection unit 325 starts creating a redemption target deposit schedule list, it transmits a redemption target deposit schedule creation start notification to the redemption management unit 340, and a redemption completion notification is transmitted from the redemption management unit 340. If so, the update of the scheduled deposit list for redemption will be canceled.

When the scheduled deposit amount list creation notification is transmitted and the scheduled deposit amount data for a predetermined period is accumulated, the period-by-period provisional sales calculation unit 326 calculates the scheduled deposit amount listed in the scheduled deposit list stored in the database 310. A provisional sales amount for each period is calculated by totaling for each predetermined period, and a list of provisional sales amounts for each period is created and stored in the database 310.
For example, the provisional sales list by period includes a daily provisional sales list that lists provisional sales for each day, a weekly provisional sales list that lists provisional sales for each week, and a provisional sales list for each month. Examples include a monthly provisional sales list that lists the highest sales figures.
The period-by-period provisional sales list of the funding system member stores 10 is updated and saved in the database 310 each time data on expected deposits for a predetermined period is further accumulated and provisional sales are calculated.

When the period-specific provisional sales amount calculation unit 326 creates the period-based provisional sales amount list, it transmits a period-based provisional sales amount list creation notification to the bonding specification design means 330, and when the period-based provisional sales amount list is updated, the period-based provisional sales amount calculation section 326 Send sales list update notification.

When the redemption target period provisional sales calculation unit 327 receives the redemption target deposit schedule creation start notification from the redemption target transaction data selection unit 325, the redemption target period provisional sales calculation unit 327 calculates the deposit schedule listed in the redemption target deposit schedule list stored in the database 310. The amounts are aggregated on a daily basis to calculate the daily provisional sales to be redeemed, create a list of daily provisional sales to be redeemed, store this in the database 310, and store the daily provisional sales to be redeemed in the redemption management means 340. Transmits a high list creation start notification.
Updating of the daily provisional sales list subject to redemption continues until a notification of completion of redemption is transmitted from the redemption management unit 340.

(Design of specifications for converting future trade receivables into bonds)
The bonding specification design means 330 includes a bonding target period setting unit 332 that sets the bonding target period and redemption start date of the future trade receivables, the bond face value of the future trade receivables and the funding system member store 10. a bond face value setting unit 334 that sets the bond purchase price; a redemption condition setting unit 336 that sets the payment terms of the redemption money to be paid by the funding system member store 10; a bond conversion period, bond face value, bond purchase price, redemption money. It has a bond purchase plan setting unit 338 that creates a bond financial product plan in which payment conditions are set and proposes it to the funding system member store 10.

If the fixed sales amount calculation unit 320 can create a provisional sales list by period for the funding system member stores 10 for a period longer than the preset period length, the bonding specification design means 330 will be able to use the created funding system member stores. Based on the period-by-period provisional sales list of the store 10, the specifications for converting future trade receivables in the future period of the funding system member store 10 into bonds are designed. The period of accumulation of provisional sales data for designing the specifications for converting future trade receivables into bonds is, for example, data for about 3 months during which the store has been operating stably, excluding periods such as when the store first opened or during short-term sale periods. It is preferable to have them all together.

The bond conversion target period setting unit 332 converts undetermined future sales receivables of the funding system member store 10 into bonds when the accumulation of provisional sales performance data of the funding system member store 10 reaches a predetermined accumulation period. Set the period covered by the bond.
It is preferable to determine the length of the period covered by the bond based on the length of the accumulation period of provisional sales performance data.For example, if the period of provisional sales performance data is accumulated for three months, The maximum length of the bond conversion period is three months. Furthermore, the unit period for bonding is preferably in units of months for ease of bonding and redemption management, and the maximum bonding target period length is preferably an integral multiple of the unit period for bonding.
It is preferable to set the target period for bonding to be within one year of the provisional sales performance data accumulation period.

The bonding target period setting unit 332 calls the provisional sales list by period of the funding system member stores 10 from the database 310, sets the maximum length of the bonding target period from the data accumulation period length of the list, and starts data accumulation. Set the period range for bond conversion based on the timing.
The bonding target period setting unit 332 sets the bond face value using the bonding target period setting notification in which the maximum length of the bonding target period and the range of the bonding target period are described and the provisional sales list by period of the funding system member store 10. 334.

When the bondization target period setting notification is transmitted, the bond face value setting unit 334 sets the bond face value and the bond purchase price based on the provisional sales list by period.
The face value of the bond is determined by multiplying the cumulative total of monthly provisional sales by a preset bond ratio. There is no particular limit to the bonding ratio, but it is usually 10% to 30% of provisional sales, and the bonding ratio also corresponds to the bond redemption ratio of the store's sales during the bonding period. In order to prevent a shortage of liquid funds on hand, it is preferable to set an upper limit on the bonding ratio, and the upper limit on the bonding ratio is equivalent to 50% of the lowest monthly provisional sales in the provisional sales accumulated data. It is preferable to set it as a value.
The bond purchase price is determined by subtracting fees and interest from the bond's face value.

The bond face value setting unit 334 generates a bond formation setting notice that includes the maximum bond formation target period length, bond formation target period range, bond face value, and bond purchase price, and a provisional sales list by period of the funding system member store 10. is transmitted to the redemption condition setting unit 336.

When the redemption condition setting unit 336 receives the bond formation setting notification, it sets the payment conditions for the redemption money to be paid by the funding system member store 10.
The redemption money that the funding system member store 10 pays to the funding business operator 30 for the purchase of bonds for future trade receivables will start to be paid when the period covered by the bonding period arrives, and the funding system member store 10 will be converted into a bond. The amount calculated by multiplying the provisional sales during the target period by the bond redemption rate will be paid every predetermined period, and payments will continue until the paid redemption amount equals the bond face value.

The redemption condition setting unit 336 sets the start date and installment payment date of redemption money installment payments and the bond redemption ratio. There is no particular restriction on the start date of the installment payment of redemption proceeds, as long as it is after the day after the start date of the period covered by the bond, but it may start from the month following the start month of the period covered by the bond, in line with the payment period of the settlement agent, etc. It is preferable to do so, and it is preferable that the redemption money installment payment date is also a monthly payment.
The bond redemption ratio is usually set to the same value as the bond conversion ratio, and the redemption condition setting unit 336 multiplies the bond redemption ratio by the actual provisional sales, which is the basis for setting the bond face value, to create a redemption money installment payment model. Create.

The redemption condition setting unit 336 generates a bond formation setting notice, a redemption condition setting notice in which a redemption money installment payment date, a bond redemption ratio, a redemption money installment payment model are described, and a provisional sales list by period of the funding system member store 10. is transmitted to the bond purchase plan creation unit 338.

When the bond purchase plan setting unit 338 receives the redemption condition setting notification, it creates a bond purchase plan for future trade receivables based on the actual provisional sales of the funding system member store 10 and sends the plan via the center server communication unit 305. and transmits it to the store management server 200.
The bond purchase plan includes the provisional sales results of the 10 funding system member stores, the maximum length of the bond conversion period, the bond conversion period range, the bond face value, the bond purchase price, the redemption installment payment date, and the bond redemption ratio. , a redemption payment model is described.
The provisional sales performance of the funding system member store 10 indicates the provisional cumulative sales amount by period and the provisional cumulative sales amount by payment method based on the provisional sales list by period of the funding system member store 10. be.

(Future trade receivable bond redemption management)
A receivables purchase price transfer contract is concluded between the store operator 20 of the funding system member store 10 and the funding operator 30, and the receivables are set as a predetermined percentage of the future provisional sales of the funding system member store 10. is sold to the funding business 30 as a purchase bond for future trade receivables, the redemption management unit 340 of the funding system center server 300 calculates the redemption amount based on the provisional sales list for the redemption period, and sends it to the center server. It is transmitted to the store management server 200 via the communication unit 305.
The redemption management unit 340 includes a redemption amount setting unit 342 that calculates the daily redemption amount, a redemption status determination unit 344 that determines the end of redemption and extension of the redemption period, and a redemption notification that notifies the redemption amount, end of redemption, and extension of the redemption period. 336.

When the redemption amount setting unit 342 receives the notification to start creating a list of scheduled payments for redemption from the scheduled payment amount calculation unit 322, it calls up the scheduled list of scheduled payments for redemption stored in the database 310, and sets the redemption rate to the daily provisional sales. The daily redemption amount is set by multiplying by , and is stored in the database 310.
Regarding the final transaction data to be redeemed, the transaction amount corresponding to the amount where the redemption amount is the same as the face value of the bond is set as the expected deposit amount to be redeemed, so that the redemption amount and the face value of the bond are the same amount.

The redemption status determination unit 344 that determines the completion of redemption concludes the redemption of the bond when the daily redemption amount set by the redemption amount setting unit 332 includes the final transaction data to be redeemed, and determines whether the bond conversion period has passed or not. Also, if the daily redemption amount does not include the last transaction data subject to redemption, the redemption period will be extended.
The extension of the redemption period will continue until the daily redemption amount includes the last transaction data eligible for redemption.

The redemption notification unit 346 notifies the store management server 200 of the daily redemption amount set by the redemption amount setting unit 332 and the completion of the redemption of the bond and the extension of the redemption period determined by the redemption status determination unit 344 to the store management server 200. The notification is sent via the communication unit 305 as follows.
The daily redemption amount notification sent from the redemption notification unit 346 to the store management server 200 via the communication unit 305 includes the daily redemption amount, whether or not bond redemption has ended, and whether or not the redemption period has been extended, as well as future sales. Includes face value of debt purchase bonds, bond conversion ratio, bond conversion period, redemption start date, cumulative redemption amount including same-day redemption amount, and remaining redemption amount.

10 Funding system member store 20 Store operator 30 Funding operator 100 Physical store terminal 150 Online shop server 155 Virtual currency wallet department 200 Store management server 220 Store management server communication department 300 Funding system center server 305 Center server communication department 310 Database 320 Provisional sales calculation means 321 Planned receipt amount calculation unit for physical store settlement 322 Planned receipt amount calculation unit for online shop settlement 323 Planned receipt amount calculation unit for virtual currency settlement 324 Scheduled receipt amount list creation unit 325 Redemption target transaction data selection unit 326 Period Separate provisional sales calculation unit 327 Temporary sales calculation unit for redemption period 330 Bond conversion specification design means 332 Bond conversion target period setting unit 334 Bond face value setting unit 336 Redemption condition setting unit 338 Bond purchase plan setting unit 340 Redemption management unit 342 Redemption amount setting section 344 Redemption status judgment section 346 Redemption notification section

Claims (5)

A store management server used by a store operator of a funding system member store and a funding system center server used by a funding company operating a funding system are connected via a communication network, and the funding system member store An unsecured funding system that purchases undetermined future trade receivables,
The store management server includes a store management server communication unit that transmits commercial transaction information of the funding system member store to the funding system center server,
The funding system center server calculates the expected deposit amount using the transmitted transaction information of the funding system member stores, aggregates this, and creates a provisional sales list of the funding system member stores for each predetermined period. Create a bond purchase plan that converts undetermined future trade receivables of the funding system member stores into bonds using a provisional sales calculation means that creates a provisional sales amount calculation means and a provisional sales list created by the provisional sales amount calculation means. and has a bonding specification design means for transmitting to the store management server via a center server communication unit,
The provisional sales amount calculation means updates the provisional sales amount list using the commercial transaction information of the funding system member store received after the creation of the provisional sales amount list,
When the provisional sales list is updated, the bond conversion specification design means updates a bond purchase plan in which undetermined future sales receivables of the funding system member store are converted into bonds, and transmits the plan to the store management server. ,
The transaction information of the funding system member store transmitted from the store management server includes physical store transaction information including information on product transactions and payments made at physical stores, and information on product transactions and payments made at online shops. online shop transaction information, including information, or both;
The physical store transaction information includes the transaction date and time, product name, product sales price, payment method, and the name of the payment processing company.
The online shop transaction information includes the transaction date and time, product name, product sales price, payment method, name of the payment processing company, and the amount of virtual currency received if the transaction is settled with virtual currency,
The provisional sales calculation means is
Calculate the expected deposit amount for physical store payment by subtracting a predetermined handling fee for each payment method from the product sales price included in the physical store transaction information,
Calculate the expected deposit amount for the online shop payment by subtracting a predetermined handling fee for each payment method from the product sales price included in the online shop transaction information excluding the virtual currency payment,
Converting the amount of virtual currency received in the virtual currency payment to the virtual currency market price at the time of receipt of the virtual currency and deducting the conversion fee from the converted amount to calculate the expected deposit amount for the virtual currency payment,
The planned deposit amount calculated using the commercial transaction information of the funding system member store includes the planned deposit amount for the physical store payment, the scheduled deposit amount for the online shop payment, and the scheduled deposit amount for the virtual currency payment. An unsecured funding system characterized by: The store management server is connected to a physical store terminal that is installed in the physical store and transmits the physical store transaction information, and/or an online shop server that transmits the online shop transaction information of the online shop. The unsecured funding system according to claim 1 . 3. The unsecured funding system according to claim 2 , wherein the physical store terminal is a vending machine equipped with a communication function to the store management server. 3. The unsecured funding system according to claim 2 , wherein the physical store terminal is a parking payment machine equipped with a communication function to the store management server. The provisional sales amount calculation means of the funding system center server includes a physical store scheduled deposit amount calculation unit that calculates the scheduled deposit amount for the physical store payment, and a scheduled deposit amount calculation unit for the online shop payment excluding the virtual currency payment . The online shop's planned deposit amount calculation unit converts the virtual currency amount received in the virtual currency payment to the virtual currency market price at the time of receiving the virtual currency, and calculates the planned amount of the virtual currency payment by subtracting the expected conversion fee from the converted amount. 5. The unsecured funding system according to claim 1 , further comprising a virtual currency payment scheduled deposit amount calculation unit that calculates the amount.

Images