Funding support server, information processing device, funding support method, and program

Abstract

To solve the problem in which: in the world of commercial transactions, factoring, which is a method of cashing accounts receivable generated by transactions at an early stage and procuring funds, is often used; however, there are a variety of companies, for example, some financing service companies (financing sources) such as factoring charge different fees, and some do not accept applications from individual stores in the first place; therefore, it is difficult for users to find financing sources that meet their assumed conditions.SOLUTION: A proposal server 3 informs a user terminal 1 of a specific financing source that will raise funds that meet predetermined conditions requested by a service user company A, and thereby the service user company A can easily find the financing source that meets the conditions assumed by itself.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present disclosure relates to a proposal server, a communication system, a providing method, and a program.

Background Art

[0002] In the world of business transactions, factoring, which is a method of raising funds by quickly cashing accounts receivable generated by transactions, is widely used. For example, Patent Document 1 discloses a method of quickly purchasing accounts receivable while reducing the manual clerical burden by implementing a procedure for purchasing accounts receivable by factoring in a computer system.

Summary of the Invention

Problems to be Solved by the Invention

[0003] However, there are various financing service companies (financing destinations) such as factoring companies, with different fees and some not accepting applications from individual stores at all. Therefore, users face the problem of having difficulty finding a financing destination that meets their assumed conditions.

Means for Solving the Problems

[0004] The invention according to claim 1 is a proposal server that provides information to a user terminal of a user who provides or plans to provide goods or services to a business partner via a communication network, the proposal server comprising: a receiving means for receiving, from the user terminal, condition information indicating predetermined conditions related to financing using a form of goods or services provided by the user; and a transmitting means for transmitting, to the user terminal, information indicating a specific financing destination determined based on the predetermined conditions among a plurality of financing destinations to which the user can perform the financing.

Effects of the Invention

[0005] As described above, according to the present invention, the proposal server notifies the user terminal of a specific financing destination that conducts financing satisfying the predetermined conditions required by the user, so that the user can find a financing destination that meets the conditions assumed by the user. It is possible to solve the problem that it is difficult to do so, and there is an effect.

Brief Explanation of Drawings

[0006]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Figure 25

Figure 26

Figure 27

Mode for Carrying Out the Invention

[0007] 〔Relationships between Enterprises〕 Using FIG. 1, the relationships between each enterprise will be described. FIG. 1 is a relationship diagram of each enterprise according to the present embodiment.

[0008] As shown in FIG. 1, the service-using enterprise A is an enterprise that uses a service to receive a recommendation of a recommended financing source from the proposing enterprise C. The trading partner enterprise B is a trading partner of the service-using enterprise A. Here, a relationship where the service-using enterprise A is a creditor and the trading partner enterprise B is a debtor may occur. The proposing enterprise C is an enterprise that provides the above service to the service-using enterprise A.

[0009] In addition, factoring service company D, accounts receivable secured financing service company E, PO financing company F, and quotation financing service company G are companies that provide the services named respectively, and all of them are fund-providing service companies. From the perspective of service-using company A, the fund-providing service companies are sources of fund-raising.

[0010] Factoring service company D is a general term for a plurality of factoring service companies D1, D2, ··· Dn. Accounts receivable secured financing service company E is a general term for a plurality of accounts receivable secured financing service companies E1, E2, ··· En. PO financing company F is a general term for a plurality of PO financing companies F1, F2, ··· Fn. Quotation financing service company G is a general term for quotation financing service companies G1, G2, ··· Gn.

[0011] Credit information service company H is a company that has trust information indicating the reliability of the management, etc. of companies such as trading partner companies and provides credit information to proposing company C. Note that credit information service company H is a general term for credit information service companies H1, H2, ··· Hn.

[0012] Here, the outline of the processing in this embodiment will be described.

[0013] First, service-using company A provides goods or services to trading partner company B or has a plan to do so, thereby generating accounts receivable and the like (S1). Then, in order to get a proposed company C to propose a source of fund-raising that meets its own conditions from a plurality of sources of fund-raising, service-using company A conveys its desired predetermined conditions (commission rate priority, risk aversion priority) to proposing company C (S2). Then, proposing company C obtains the credit information of trading partner company B from credit information service company H, and comprehensively judges this credit information, the content of the documents, the predetermined conditions from service-using company A, etc., and proposes a specific recommended source of fund-raising to service-using company A (S3).

[0014] As a result, the service-using company A sends a form to the proposed specific financing source (the fund-providing service company) to apply for financing (S4). In response, the specific fund-providing service company conducts financing for the service-using company A after review (S5). Furthermore, the specific fund-providing service company issues a claim for accounts receivable corresponding to accounts receivable and the like to the trading company B (S6). As a result, the trading company B makes a payment of accounts receivable to the specific fund-providing service company on time (S7).

[0015] 〔Overview of the communication system〕 FIG. 2 is a schematic diagram of the communication system of the present embodiment. FIG. 2 is a diagram showing the terminals or servers of each company in FIG. 1.

[0016] A user terminal 1 such as a PC (personal computer) is installed in the user company A and is operated by the user A1. A proposal server 3 is provided in the proposing company C. In addition, fund-providing service servers 5d, 5e, 5f, 5g are provided in the factoring service company D, the accounts receivable secured financing service company E, the PO financing company F, and the quotation financing service company G, respectively. A credit information server 7 is provided in the credit information service company H. Each server is configured by a computer. The user terminal 1, the fund-providing service servers 5d, 5e, 5f, 5g, and the credit information server 7 can communicate via a communication network 100 such as the Internet. Hereinafter, the general term for the fund-providing service servers 5d, 5e, 5f, 5g is denoted as "fund-providing service server 5".

[0017] 〔Hardware configuration of each part of the communication system〕 Subsequently, with reference to FIG. 3, the hardware configuration of each terminal and server that constructs the communication system shown in FIG. 1 will be described. Since all have the same configuration, the hardware configuration of the user terminal 1 will be described, and the description of the hardware configuration of each server will be omitted.

[0018] As shown in FIG. 3, user A1 is composed of a computer, which includes a CPU 101, a ROM 102, a RAM 103, an HD 104, an HDD (Hard Disk Drive) controller 105, a display 106, an external device connection I / F (Interface) 108, a network I / F 109, a bus line 110, a keyboard 111, a pointing device 112, a DVD-RW (Digital Versatile Disk Rewritable) drive 114, and a media I / F 116.

[0019] Among these, the CPU 101 controls the operation of the entire computer. The ROM 102 stores programs used for driving the CPU 101 such as the IPL. The RAM 103 is used as a work area for the CPU 101. The HD 104 stores various data such as programs. The HDD controller 105 controls the reading or writing of various data to and from the HD 104 according to the control of the CPU 101. The display 106 displays various information such as a cursor, a menu, a window, characters, or images. The external device connection I / F 108 is an interface for connecting various external devices. External devices in this case are, for example, a USB (Universal Serial Bus) memory, a printer, and the like. The network I / F 109 is an interface for performing data communication using the communication network 100. The bus line 110 is an address bus, a data bus, etc. for electrically connecting each component such as the CPU 101 shown in FIG. 3.

[0020] In addition, the keyboard 111 is a type of input means having a plurality of keys for inputting characters, numerical values, various instructions, and the like. The pointing device 112 is a type of input means for selecting and executing various instructions, selecting a processing target, moving a cursor, and the like. The DVD-RW drive 114 controls reading or writing of various data with respect to the DVD-RW 113 as an example of a removable recording medium. Note that it is not limited to the DVD-RW, and it may be a DVD-R, a Blu-ray Disc, or the like. The media I / F 116 controls reading or writing (storage) of data with respect to the recording medium 115 such as a flash memory.

[0021] In addition, to the external device connection I / F, a microphone as an example of a sound collection device, a speaker as an example of a sound output device, a camera as an example of an imaging device, and the like can be connected.

[0022] Next, with reference to FIGS. 3 to 16, each functional configuration of the communication system of the present embodiment will be described. FIG. 4 is a functional block diagram of the communication system according to the present embodiment. Note that the funding service server 5 and the credit information server 7 are not described because they do not have new functions in the communication process of the present embodiment.

[0023] First, with reference to FIGS. 3 and 4, the functional configuration of the user terminal 1 will be described. As shown in FIG. 4, the user terminal 1 includes a transmission / reception unit 11, a reception unit 12, a display control unit 14, a determination unit 15, and a storage / read processing unit 19. Each of these units is a function or a means realized by any of the components shown in FIG. 3 operating according to an instruction from the CPU 101 according to a program expanded from the HD 104 onto the RAM 103. In addition, the user terminal 1 has a storage unit 1000 constructed by the RAM 103 and the HD 104 shown in FIG. 3.

[0024] ( ​​Next, each component of the user terminal 1 will be described. The transmission / reception unit 11 is realized by instructions from the CPU 101 shown in FIG. 3, as well as the external device connection I / F 108 and the network I / F 109, and transmits and receives various data (or information) to and from other terminals, devices, or systems via the communication network 100.

[0025] The reception unit 12 is mainly realized by instructions from the CPU 101 shown in FIG. 3, as well as the keyboard 111, the pointing device 112, the operation buttons, and the power switch, and receives various inputs from the user.

[0026] The display control unit 14 is mainly realized by instructions from the CPU 101 shown in FIG. 3, and displays an image by outputting image data to the display 106 or an external display connected to the external device connection I / F. The display control unit 14 has a web browser function.

[0027] The determination unit 15 is mainly realized by instructions from the CPU 101 shown in FIG. 3, and makes various determinations.

[0028] The storage / reading processing unit 19 is mainly executed by instructions from the CPU 101 shown in FIG. 3 and the HDD controller 105, and performs processing for storing various data in the storage unit 1000 or reading out various data stored in the storage unit 1000.

[0029] <Functional Configuration of the Proposal Server> Subsequently, the functional configuration of the proposal server 3 will be described with reference to FIGS. 3 to 16. As shown in FIG. 4, the proposal server 3 includes a transmission / reception unit 31, a calculation unit 33, a determination unit 35, a creation unit 36, and a storage / reading processing unit 39. Each of these units is a function or means realized by the operation of any of the components shown in FIG. 3 according to instructions from the CPU 101 in accordance with the program expanded from the HD 104 onto the RAM 103. The proposal server 3 also has a storage unit 3000 constructed by the RAM 103 and the HD 104 shown in FIG. 3.

[0030] (Tenant Regular Expense History Management Table) FIG. 5 is a conceptual diagram showing a tenant regular expense history management table. In the storage unit 3000, a tenant regular expense management DB 3001 configured by a tenant regular expense history management table as shown in FIG. 5 is constructed. In this table, for each tenant ID for identifying a service-using company (tenant) that receives services from the proposing company C, the past expense types, expense months, and amounts for which regular payments have occurred are managed in association. Based on this table, future regular payments are predicted.

[0031] (Tenant Individual Payment Management Table) FIG. 6 is a conceptual diagram showing a tenant individual payment management table. In the storage unit 3000, a tenant regular expense management DB 3001 configured by a tenant regular expense history management table as shown in FIG. 6 is constructed. In this table, as tenant payment information, for each tenant ID, information such as ID, claimant, payment due date, amount, and payment status is managed in association.

[0032] (Fundraising Information Management Table) FIG. 7 is a conceptual diagram showing a fundraising information management table. In the storage unit 3000, a fundraising information management DB 3003 configured by a fundraising information management table as shown in FIG. 7 is constructed. This table shows the content of the form used for fundraising. Therefore, in this table, for each tenant ID, information such as ID, trading partner, fundraising target type, payment due date, amount, and payment status, as well as the storage destination of the form image digitized into PDF, etc., is managed in association. Note that the fundraising target types include invoices, orders, and estimates.

[0033] (Tenant Bank Account Table) FIG. 8 is a conceptual diagram showing a tenant bank account management table. In the storage unit 3000, a tenant bank account management DB 3004 constituted by a tenant bank account management table as shown in FIG. 8 is constructed. This table shows the contents regarding the user's own bank account registered in the proposal server 3 in advance. Therefore, in this table, for each tenant ID, the bank name, branch name, account number, user name, and password are managed in association.

[0034] (Tenant Credit Card Information Management Table) FIG. 9 is a conceptual diagram showing a tenant credit card information management table. In the storage unit 3000, a tenant credit card management DB 3005 constituted by a tenant credit card information management table as shown in FIG. 9 is constructed. This table shows the contents regarding the user's own credit card registered in the proposal server 3 in advance. Therefore, in this table, for each tenant ID, the card name (card number), user name, and password are managed in association. The amount that can be borrowed with this information is used for the cash balance later.

[0035] (Tenant Management Table) FIG. 10 is a conceptual diagram showing a tenant management table. In the storage unit 3000, a tenant management DB 3006 constituted by a tenant management table as shown in FIG. 10 is constructed. This table shows the contents regarding the corporate information of the tenant. Therefore, in this table, the tenant ID, tenant name, tenant address (location), tenant industry type, and tenant business type are managed in association. This information is used, for example, when a funding service company that does not provide funds specifically for the construction industry is excluded from the selection target when the tenant is in the construction industry.

[0036] (Funding Service Type Management Table) FIG. 11 is a conceptual diagram showing a fund - providing service type management table. In the storage unit 3000, a fund - providing service type management DB3007 composed of a fund - providing service type management table as shown in FIG. 11 is constructed. In this table, the types of financing targets and the types of fund - providing services (financing types) are managed in association with each other.

[0037] (Fund - providing service management table) FIG. 12 is a conceptual diagram showing a fund - providing service management table. In the storage unit 3000, a fund - providing service management DB3008 composed of a fund - providing service management table as shown in FIG. 12 is constructed. In this table, the type of fund - providing service, the name of the fund - providing service (company name), the industries not eligible for fund - providing, the regions eligible for fund - providing, the response to individual businesses for fund - providing, the amount condition for fund - providing, and the connection URL (destination information) of the fund - providing service server 5 of the fund - providing service company are managed in association with each other. Note that when the response to individual businesses for fund - providing is "false", the fund - providing service company is a company that provides funds to enterprises but not to individuals.

[0038] (Destination information management table) FIG. 13 is a conceptual diagram showing a destination information management table. In the storage unit 3000, a destination information management DB3009 composed of a destination information management table as shown in FIG. 13 is constructed. In this table, for each type of information, the destination name (company name) for obtaining the information and the connection URL (destination information) are managed in association with each other.

[0039] (Credit information adjustment management table) FIG. 14 is a conceptual diagram showing a credit information adjustment management table. In the storage unit 3000, a credit information adjustment management DB 3010 is constructed by a credit information adjustment management table as shown in FIG. 14. In this table, for each credit rating, the credit ratings provided by each credit information service company are managed in association. Since the levels of credit ratings set by each credit information service company are different, this is used to adjust and unify them.

[0040] (Credit Information Management Table) FIG. 15 is a conceptual diagram showing a credit information management table. In the storage unit 3000, a credit information management DB 3011 is constructed by a credit information management table as shown in FIG. 15. In this table, the credit ratings adjusted in the credit information management table of FIG. 15 are managed in association for each trading partner.

[0041] (Recommended Candidate Information Management Table) FIG. 16 is a conceptual diagram showing a recommended candidate information management table. In the storage unit 3000, a recommended candidate information management DB 3012 is constructed by a recommended candidate information management table as shown in FIG. 16. This table shows recommended candidate information including the content of the forms used for financing. Therefore, in this table, the trading partner, the credit rating of the trading partner, the transaction amount shown in the form, the type of financing target, the type of financing service (financing type), the name of the financing service (company name), the commission rate at the time of financing, and the deposit date for depositing money into the service-using company when financing are managed in association. Note that the recommended information finally proposed to the service-using company is extracted from among these recommended candidate information.

[0042] (Each Functional Configuration of the Proposal Server) Next, each functional configuration of the proposal server 3 will be described in detail. Hereinafter, when explaining each functional configuration of the proposal server 3, the relationship with the main components for realizing each functional configuration of the proposal server 3 among each component shown in FIG. 3 will also be explained.

[0043] The transmission / reception unit 31 of the proposed server 3 shown in FIG. 4 is realized by the instructions from the CPU 101 shown in FIG. 3 and the network I / F 109, and transmits and receives various data (or information) with other terminals, devices, or systems via the communication network 100.

[0044] The calculation unit 33 is realized by the instructions from the CPU 101 shown in FIG. 3 and performs a predetermined calculation. The calculation details will be described later.

[0045] The determination unit 35 is realized by the instructions from the CPU 101 shown in FIG. 3 and performs a predetermined determination. The determination details will be described later.

[0046] The creation unit 36 is realized by the instructions from the CPU 101 shown in FIG. 3 and creates a fund flow screen, etc.

[0047] The storage / read processing unit 39 is realized by the instructions from the CPU 101 shown in FIG. 3 and the HDD controller 105, and performs processing to store various data in the storage unit 3000 or read out various data stored in the storage unit 3000.

[0048] 〔Processing or operation of the embodiment〕 Subsequently, with reference to FIGS. 17 to 27, the processing or operation of this embodiment will be described.

[0049] <Display processing of the fund flow screen> First, with reference to FIG. 17, the processing for displaying the fund flow screen will be described. FIG. 17 is a sequence diagram showing the processing for displaying the fund flow screen.

[0050] User A1 makes a login request from user terminal 1 to proposal server 3 (S21). This login request includes a tenant ID and a password for identifying service-using company A, which is an example of a tenant. As a result, the transmission / reception unit 31 of proposal server 3 receives the login request. Then, the determination unit 35 of proposal server 3 performs authentication by determining whether service-using company A is a legitimate tenant for receiving the service (S22).

[0051] Next, the transmission / reception unit 31 transmits a response to user terminal 1 (S23). As a result, the transmission / reception unit 11 of user terminal 1 receives the response. Here, the case where service-using company A is a legitimate tenant will be continued to be explained.

[0052] User A1 operates user terminal 1, and the reception unit 12 receives a display request for the cash flow screen (S24). Then, the transmission / reception unit 11 transmits a request for cash flow screen data to proposal server 3 (S25). As a result, the transmission / reception unit 31 of proposal server 3 receives the request for cash flow screen data.

[0053] Next, proposal server 3 performs a creation process for the cash flow screen (S26). Here, with reference to FIG. 18, the creation process for the cash flow screen will be described in detail. FIG. 18 is a flowchart showing the creation process for the cash flow screen.

[0054] (Creation Process for Cash Flow Screen) As shown in FIG. 18, the storage / reading processing unit 39 reads out the corresponding tenant regular expense history information by searching the tenant regular expense management DB3001 (see FIG. 5) using the tenant ID used at the time of authentication as a search key (S101). Also, the storage / reading processing unit 39 reads out the corresponding tenant individual payment information by searching the tenant individual payment management DB3002 (see FIG. 6) using the tenant ID as a search key (S102). Then, the calculation unit 33 calculates the expenditure information for each corresponding period (here, one month) based on the tenant regular expense history information and the tenant individual payment information (S103).

[0055] Next, the memory / read processing unit 39 reads out the corresponding financing information by searching the financing information management DB 3003 (see FIG. 7) using the tenant ID as a search key (S104). Then, the calculation unit 33 calculates the income information for each target period (S105).

[0056] Next, the memory / read processing unit 39 reads out the corresponding tenant bank account information by searching the tenant bank account management DB 3004 (see FIG. 8) using the tenant ID as a search key (S106). Also, the memory / read processing unit 39 reads out the corresponding tenant credit card information by searching the tenant credit card management DB 3005 (see FIG. 9) using the tenant ID as a search key (S107). Then, the calculation unit 33 calculates the cash balance for each target period (S108).

[0057] Next, the creation unit 36 creates a fund flow screen as shown in FIG. 19 using the calculation results calculated in the above steps S103, S105, and S108 (S109). FIG. 19 is a diagram showing a display example of the fund flow screen. Thus, the creation process of the fund flow screen ends.

[0058] <� Subsequently, returning to FIG. 17, the display control unit 14 of the user terminal 1 displays the first fund flow screen as shown in FIG. 19 on the display 106 of the user terminal 1 by means of the Web browser function (S27).

[0059] (First fund flow screen) Here, the first fund flow screen 210 will be described with reference to FIG. 19. FIG. 19 is a diagram showing a display example of the fund flow screen.

[0060] As shown in FIG. 19, the fund flow screen 210 includes a display column 211 for the tenant ID, a display column 212 for the operation date, a display column 213 for the past income and expenditure performance, and a display column 214 for the future income and expenditure prediction.

[0061] Among these, in the operation date display column 212, the date (displayed date) on which this cash flow screen is operated is shown. In the past revenue and expenditure performance display column 213, the monthly revenue and expenditure performance (expenditure, revenue, cash balance) prior to the operation date is shown. This revenue and expenditure performance is the value at the end of the month. For example, in August 2020, the revenue is 1 million yen, the cash balance is 1.2 million yen, and the expenditure is 0.7 million yen. Among these, the cash balance is the value of "revenue + cash balance - expenditure" for the previous month, which is July in this case.

[0062] Also, in the future revenue and expenditure prediction display column 214, the monthly performance (expenditure, revenue, cash balance) in the future relative to the operation date is shown. Since the revenue and expenditure prediction is the value at the end of the month, when the operation date is September 15th, the revenue and expenditure at the end of September will be shown in the revenue and expenditure prediction display column 214. Here, information 2141 indicating a shortfall of 2 million yen at the end of October is shown. The expenditure in October is 2.6 million yen. Only the cash balance of 0.6 million yen that surely exists by the payment date is used to fill the gap for this 2.6 million yen. As a result, the shortfall information 2141 indicating a shortfall of 2 million yen in October is shown. Note that since the predicted revenue of 0.5 million yen in October may not arrive in time by the payment date of 2.6 million yen, it is not used to fill the gap for the 2.6 million yen expenditure. Thus, the user can easily and visually understand that there will be a shortfall of 2 million yen at the end of October 2020.

[0063] Also, at the bottom of the cash flow screen 210, three reception columns 215 to 217 for receiving selections or inputs from the user are included. Note that from the user's perspective, the fund-providing service company is the source of funds.

[0064] Among these, in the "recommended priority condition" reception column 215, a "fee rate priority (condition)" radio button 2151 and a "risk avoidance priority (condition)" radio button 2152 are shown.

[0065] "Fee rate priority" is an example of a predetermined condition for determining a specific funding source by prioritizing the low fee rates of each funding from among multiple funding sources (fund - providing service companies) according to the content of multiple documents with each of the multiple funding sources. When the user presses the "Fee rate priority" radio button 2151, the proposal server 3 proposes the recommended information described below, giving priority to the fee rate.

[0066] Also, "risk avoidance priority" is an example of a predetermined condition for determining a specific funding source by prioritizing the low reliability of the trading partner from among multiple funding sources (fund - providing service companies). When the user presses the "Risk avoidance priority" radio button 2152, the proposal server 3 prioritizes the low reliability of the trading partner and determines a specific funding source as an example of a predetermined condition. When the user presses the "Risk avoidance priority" radio button 2152, the proposal server 3 proposes the recommended information described below, giving priority to risk avoidance. For example, when there is a high possibility that accounts receivable cannot be collected from a debtor as a trading partner company, funding is prioritized for accounts receivable from such a company.

[0067] In addition, in the "Payment due date of funding target" reception field 216, a period input field 2161 for input in units of a predetermined period (here, one month) is displayed. In FIG. 19, the predetermined period from the month including the operation date (here, September 2020) to six months later (February 2021) is input. As a result, the recommended information described below is limited to information including documents in which payments are deducted from revenues until February 2021.

[0068] Furthermore, in the "Type of Financing Target" reception field 217, check boxes 2171, 2172, and 2173 for "Invoice", "Purchase Order", and "Quotation" are displayed as specific examples of the financing target. Among the check boxes 2171 to 2173, the types of documents (including electronic data) checked by the user will be the targets of financing. As shown in FIG. 19, in this embodiment, the types of financing targets include "Quotation" before the conclusion of a transaction (sale or purchase). That is, by selecting (designating) the desired type of financing target, the user can narrow down the candidates for the financing source (fund - providing service company) to be used.

[0069] Next, the "Recommendation Request" button 219 is a button for the user to press when, after making the desired selections and inputs in each input field 215, 216, 217, the user wishes to receive a recommendation of the most suitable financing source (fund - providing service company) from the proposal server 3 of the proposed company C.

[0070] <Display Processing of Recommendation Screen> Subsequently, with reference to FIGS. 19 to 27, the display processing of the recommendation screen will be described. FIG. 20 is a sequence diagram showing the display processing of the recommendation screen.

[0071] First, in FIG. 19, when user A1 makes the desired selections and inputs in each reception field 215 to 217, the reception unit 12 receives the selections and inputs (S41). Furthermore, when user A1 presses the "Recommendation Request" button 219, the reception unit 12 receives the request for the recommendation screen (S42). Then, the transmission - reception unit 11 sends a request for recommendation screen data to the proposal server 3 (S43).

[0072] Next, the proposal server 3 performs the narrowing - down process of the recommendation information (S44). Here, with reference to FIGS. 21 to 27, the narrowing - down process of the recommendation information will be described in detail.

[0073] (Creation Processing of Recommendation Screen) FIG. 21 is a flowchart of the narrowing-down process of recommended information. As shown in FIG. 21, when creating a recommendation screen, the proposal server 3 performs a preliminary preparation process as a process of identifying a funding service company that actually makes an inquiry about the commission rate from among a plurality of funding service companies (fundraising destinations) (S121).

[0074] ((Preliminary Preparation)) Here, the preliminary preparation process will be described in detail with reference to FIG. 22. FIG. 22 is a flowchart showing the preliminary preparation process.

[0075] First, the storage / reading processing unit 39 searches the tenant management DB 3006 (see FIG. 10) using the tenant ID used for authentication in step S22 as a search key, and reads out each piece of information such as the tenant's address, industry type, and business type (S141).

[0076] Next, the storage / reading processing unit 39 reads out the fundraising information (each record) whose payment deadline is included within the "payment deadline of the fundraising target" input in FIG. 19 from the fundraising information management DB 3003 (see FIG. 7) (S142).

[0077] Next, the storage / reading processing unit 39 refers to the funding service type management DB 3007 (see FIG. 11) and identifies the type of funding service (fundraising type) corresponding to the "type of fundraising target" selected in FIG. 19 (S143).

[0078] Next, the storage / reading processing unit 39 searches the funding service management DB 3008 (see FIG. 12) using the information on the type of funding service identified in step S143 as a search key, and identifies the information of the record including the corresponding funding service name (funding service information) (S144).

[0079] Subsequently, the proposal server 3 repeatedly executes the processes of steps S146 to S150 between steps S145 and S151 for each piece of funding service information.

[0080] First, the memory / reading processing unit 39 reads out the "non-corresponding industries", "corresponding regions", and "individual business correspondence" of the fund-providing service from the predetermined fund-providing service information identified in step S145 (S146).

[0081] Next, the determination unit 35 determines whether the tenant industry of user A1 does not correspond based on the "non-corresponding industries" information (S147). If it does not correspond (S147; NO), the determination unit 35 determines whether the tenant address of user A1 is outside the corresponding region (S148). If it is not outside the corresponding region (S148; NO), the determination unit 35 determines whether the business type of the tenant of user A1 corresponds to individual business correspondence (S149). If it corresponds (S149; YES), the determination unit 35 identifies the fund-providing service (enterprise) that actually makes an inquiry about the commission rate (S150). Then, it returns to step S145, and the proposal server 3 proceeds with the same processing for the next predetermined fund-providing service information. On the other hand, if it is YES in step S147, YES in step S148, or NO in step S149, the proposal server 3 does not execute the processing of step S150, returns to step S145, and proceeds with the same processing for the next predetermined fund-providing service information, thus ending the processing of FIG. 22.

[0082] In the above manner, the proposal server 3 can narrow down the specific fund-providing services that are the subjects of commission rate inquiries among all the fund-providing services identified in step S144 (first narrowing).

[0083] Subsequently, returning to FIG. 21, the proposal server 3 creates recommendation candidate information that is a candidate for the recommendation information to be provided to user A1 (S122).

[0084] ((Creation of Recommendation Candidate Information)) Here, the creation process of the recommendation candidate information will be described with reference to FIG. 23. FIG. 23 is a flowchart showing the creation process of the recommendation candidate information.

[0085] As shown in FIG. 23, the memory / read processing unit 39 reads out financing information (each record) whose payment deadline is included within the "payment deadline for financing target" input in FIG. 19 from the financing information management DB 3003 (see FIG. 7) (S161). Subsequently, the proposal server 3 repeatedly executes the processes of steps S163 to S171 between steps S162 and S172 for each piece of financing information read out in step S161.

[0086] First, the memory / read processing unit 39 refers to the funding service type management DB 3007 (see FIG. 11) to identify the type of funding service corresponding to the "type of financing target" selected in FIG. 19 (S163).

[0087] Next, the transmission / reception unit 31 creates inquiry information for each identified type of funding service among the specific funding services (enterprises) for which the commission rate is to be inquired, and obtains the commission rate from the funding service server 5 that manages the specific funding service. The transmission / reception unit 31 makes an inquiry about the commission rate with reference to the destination information of each funding service server 5 managed in the destination information management DB 3009 (see FIG. 12). Here, as the process of step S164, in FIG. 20, the transmission / reception unit 31 of the proposal server 3 transmits inquiry information about the commission rate to each funding service server 5 (S164-​​1), and receives the latest commission rate information transmitted by the funding service server 5 (S164-​​2).

[0088] Next, the memory / read processing unit 39 holds the commission rate information received from each funding service server 5 in the memory unit 3000 (S165).

[0089] Next, the creation unit 36 identifies, as a comparison target for the comparison described later, information in which the fund - providing service with the lowest commission rate is associated with the financing information (secondary narrowing - down) (S166). For example, in FIG. 16, in the case of an invoice with the counterparty being Corporation X1 and the transaction amount being 900,000 yen, services A1, A2, B1, B2, etc. are listed as financing source candidates. Among these, the fund - providing service B2 with the lowest commission rate (5%) and the information in which the financing information (invoice of Corporation X1, credit rating 5, transaction amount 900,000 yen, etc.) are associated are identified as the comparison target.

[0090] Next, the storage / reading processing unit 39 further acquires the credit information of the counterparty (enterprise) from the financing information read in step S161 (S167).

[0091] Next, the transmission / reception unit 31 acquires the credit information of the counterparty enterprise B from each credit information server 7 (S168). In this case, the transmission / reception unit 31 makes an inquiry with reference to the destination information of each credit information server 7 managed in the destination information management DB3009. Also, as the processing of step S168, in FIG. 20, the transmission / reception unit 31 of the proposal server 3 transmits a request for credit information to each credit information server 7 (S168 - 1) and receives the credit information transmitted by the credit information server 7 (S168 - 2).

[0092] However, the content of the credit information varies depending on each credit information service enterprise. For example, some enterprises manage credit information in three levels of "H, N, L", while some manage it in seven levels of "7 - 1". Therefore, adjustment is necessary. Thus, in order to align the response information received from each credit information server 7 with a unified credit rating, the storage / reading processing unit 39 refers to the credit information adjustment management DB3010 and replaces the response information received from each credit information server 7 with a unified credit rating (S169). Then, the storage / reading processing unit 39 manages the credit ratings of each counterparty (enterprise) in the credit information management DB3011 (S170).

[0093] Then, the memory / read processing unit 39 manages each recommended candidate information obtained and managed in Steps S161 to S171 for each business partner in the recommended candidate information management DB 3012 (see FIG. 16) (S171).

[0094] As described above, the proposal server 3 can manage the recommended candidate information.

[0095] ((Sorting of recommended information)) Subsequently, returning to FIG. 21, a process of sorting (reordering) the recommended candidate information as recommended information according to the priority information selected in FIG. 19 will be described.

[0096] When the commission rate priority is selected as the recommended priority condition in FIG. 19 (S123; commission rate priority), the memory and read processing unit 39 compares each piece of recommended candidate information managed in the recommended candidate information management DB 3012, and in order to finally extract the recommended information corresponding to the request from the user, the comparison targets that are each piece of recommended candidate information are sorted with the order of the lower commission rate as the first condition and the order of the higher credit rating as the second condition, and each piece of recommended information optimal for the commission rate priority is read out (S124). For example, in FIG. 16, the recommended candidate information indicating service B2 with a commission rate of 5% which is the lowest for an invoice with a transaction amount of 900,000 yen for Company X1, the recommended candidate information indicating service B1 with a commission rate of 6% which is the lowest for an invoice with a transaction amount of 500,000 yen for Company X2, the recommended candidate information indicating service B2 with a commission rate of 7% which is the lowest for an invoice with a transaction amount of 800,000 yen for Company X3, etc. are the comparison targets. Also, as a result of sorting the comparison targets in the order of the lower commission rate (the first condition), the combination of the invoice with a transaction amount of 900,000 yen for Company X1 and service B2 (commission rate 5%), the combination of the invoice with a transaction amount of 500,000 yen for Company X2 and service B1 (commission rate 6%), the combination of the invoice with a transaction amount of 800,000 yen for Company X3 and service B2 (commission rate 7%) are in this order. If there are multiple comparison targets with the same commission rate, the comparison targets with the same commission rate are further sorted in the order of the higher credit rating (the second condition). That is, the comparison targets are sorted by the first condition, and for the comparison targets with the same first condition, they are sorted by the second condition. The same applies when the risk avoidance priority is selected as the priority condition described later.

[0097] On the other hand, when the risk avoidance priority is selected as the priority condition in FIG. 19 (S123; risk avoidance priority), the memory and read processing unit 39 compares each piece of recommended candidate information managed in the recommended candidate information management DB 3012, and in order to finally extract the recommended information corresponding to the request from the user, the comparison targets that are each piece of recommended candidate information are sorted with the order of the lower credit rating as the first condition and the order of the lower commission rate as the second condition, and each piece of recommended information optimal for the risk avoidance priority is read out (S125).

[0098] Then, the memory / read processing unit 39 reads out the data of the recommended screen frame stored in the storage unit 3000 (S126).

[0099] Finally, the creation unit 36 creates a recommended screen as shown in FIG. 24 based on each piece of recommended information read in step S124, or creates a recommended screen as shown in FIG. 26 based on each piece of recommended information read in step S125 (S126). At this point, the check boxes are not checked. FIG. 24 is a diagram showing a display example of the recommended screen in the case of fee priority. FIG. 26 is a diagram showing a display example of the recommended screen in the case of risk avoidance priority. Note that FIG. 25 is a diagram showing a display example of the recommended screen after the display change in the case of fee priority.

[0100] <Redisplay process of the cash flow screen> Subsequently, returning to FIG. 20, the process of redisplaying the cash flow screen will be described.

[0101] First, after the narrowing-down process of the recommended information is completed in step S44 above, the transmission / reception unit 31 transmits all the recommended information narrowed down in step S44 and the data of the recommended screen frame read in step S126 to the user terminal 1 (S45). As a result, the transmission / reception unit 11 of the user terminal 1 receives all the recommended information and the data of the recommended screen frame.

[0102] Next, in the user terminal 1, the display control unit 14 includes the recommended information in the recommended screen frame received in step S45, and displays a recommended screen as shown in FIG. 24 (or FIG. 26) on the display 106 of the user terminal 1 (S46).

[0103] (Recommended screen (fee rate priority)) Here, the case where the recommended screen indicates fee rate priority will be described with reference to FIG. 24. FIG. 24 is a diagram showing a display example of the recommended screen in the case of fee rate priority.

[0104] As shown in FIG. 24, the recommended screen 250 includes each piece of recommended information (the business partner which is information about the form used for financing, the type of financing target, the transaction amount, the scheduled payment date, the type of financing which is information about the financing source, the financing source, the commission rate, the adjustment amount, the deposit date, and the creditworthiness of the business partner). Also, on the left side of each piece of recommended information, a check box for selection is shown. Note that the transaction amount is the amount that the user expects to obtain from the business partner. Also, the financing amount is the amount obtained from the fund-providing service company (financing source) with the commission deducted. Also, it is displayed with all the check boxes being checked from the beginning.

[0105] Furthermore, on the lower left side of the recommended screen 250, the total financing amount and the shortage amount are shown. The total financing amount indicates the total of the financing amounts of the recommended information for which user A1 has checked the check box. From the beginning, the total financing amount is displayed as the lowest total amount that exceeds the shortage amount.

[0106] Also, on the lower right side of the recommended screen 250, an "OK" button 257 and a "View Other Recommendations" button 259 are shown. The "OK" button 257 is a button for user A1 to press when finalizing the display content in FIG. 24. When the "OK" button 257 is pressed, the user terminal 1 transmits confirmation information indicating finalization to the proposal server 3. The "View Other Recommendations" button 258 is a button for the user to press when displaying other examples among the recommended information.

[0107] In this state, when user A1 presses the "View Other Recommendations" button 258, the display control unit 14 changes to a recommended screen 251 as shown in FIG. 25 (S47). Here, two new pieces of recommended information are displayed, but the check boxes are not checked. That is, the recommended information displayed in FIG. 24 has undergone tertiary filtering.

[0108] On the lower right side, instead of the "View Other Recommendations" button 258, a "Return to the First Recommendation" button 259 is displayed. When the "Return to the First Recommendation" button 259 is pressed, the display control unit 14 returns the display from the recommendation screen 251 in FIG. 25 to the recommendation screen 250 in FIG. 24.

[0109] Note that in the recommendation screen in FIG. 25, information related to the forms used for financing and information related to the financing destination are displayed as described above. However, only the information related to the forms used for financing may be displayed, or only the information related to the financing destination may be displayed.

[0110] (Recommendation Screen (Risk Avoidance Priority)) Also, with reference to FIG. 26, the case where the recommendation screen indicates risk avoidance priority will be described. FIG. 26 is a diagram showing an example of the display of the recommendation screen in the case of risk avoidance priority.

[0111] In this case, the configuration is basically the same as that of the recommendation screen with fee rate priority. That is, as shown in FIG. 26, in the recommendation screen 260, each piece of recommendation information (the business partner, the type of financing target, the transaction amount, the scheduled payment date, which are information related to the forms used for financing, and the type of financing, the financing destination, the fee rate, the adjustment amount, the deposit date, and the creditworthiness of the business partner, which are information related to the financing destination) is included. Also, on the left side of each piece of recommendation information, a check box for selection is shown.

[0112] Furthermore, on the lower left side of the recommendation screen 260, the total financing amount and the shortage amount are shown. The total financing amount indicates the combination of the financing amounts of the recommendation information that user A1 has checked in the check box. Also, the "Confirm" button 268 and the "View Other Recommendations" button 269 on the lower right side of the recommendation screen 260 are the same as the "Confirm" button 257 and the "View Other Recommendations" button 258 on the lower right side of the recommendation screen 250 in FIG. 24, respectively.

[0113] Here, the case where user A1 presses the "Confirm" button 257 while the three check boxes in FIG. 24 are checked will be continuously described.

[0114] When user A1 presses the "Confirm" button 257, as shown in FIG. 20, the reception unit 12 receives the recommended information selected by the checkbox (S48). Then, the transmission / reception unit 11 transmits the recommended information selected in step S48 to the proposal server 3 (S49). As a result, the transmission / reception unit 31 of the proposal server 3 receives the selected recommended information.

[0115] Next, in the proposal server 3, the creation unit 36 creates a cash flow screen as shown in FIG. 27 by reflecting the recommended information received in step S49 (S50).

[0116] Subsequently, after the creation process of the cash flow screen reflecting the recommended information in step S50 is completed, the display control unit 14 of the user terminal 1 displays the recommended screen created in step S50 on the display 106 of the user terminal 1 by means of the Web browser function (S51).

[0117] Also in this case, it can be changed to a recommended screen as shown in FIG. 26, but the description is omitted.

[0118] Note that on the recommended screen in FIG. 26, information regarding the forms used for financing and information regarding the financing destination are displayed as described above. However, only the information regarding the forms used for financing may be displayed, or only the information regarding the financing destination may be displayed.

[0119] (Cash flow screen reflecting recommended information) Here, with reference to FIG. 27, the cash flow screen 220 reflecting the recommended information in the case of fee rate priority will be described. FIG. 27 is a diagram showing a display example of the cash flow screen reflecting the recommended information in the case of fee rate priority.

[0120] As shown in FIG. 27, on the cash flow screen 220, new information 2251 indicating that 2,069,000 yen can be raised through financing when funds are provided is displayed with respect to the cash flow screen 210 of FIG. 19. Also, due to the financing of 2,069,000 yen, the income and cash balance after October 2020 are changed. In particular, since the funds raised by user A1 in October 2020 will not be included in the subsequent income, information 2261, 2262, 2263 indicating the amount that will not be included in this income is displayed.

[0121] Also, on the lower right side of the cash flow screen 220, a "Confirm" button 229 is included. The "Confirm" button 229 is a button for user A1 to press when checking the content shown in FIG. 27 and closing the screen 220 of FIG. 27. Also, when user A1 presses the "Confirm" button 228 in FIG. 27, as shown in FIG. 20, the reception unit 12 receives the fact that the confirmation has been made (S50). Then, the transmission / reception unit 11 transmits confirmation information indicating that the content displayed in step S49 has been confirmed to the proposal server 3 (S53). As a result, the transmission / reception unit 31 of the proposal server 3 receives the confirmation information.

[0122] Thus, the process of redisplaying the cash flow screen ends.

[0123] 〔Main effects of this embodiment〕 As described above, according to this embodiment, the proposal server 3 transmits to the user terminal 1 a specific financing destination that conducts financing satisfying the predetermined conditions required by user A1. That is, the proposal server 3 makes a proposal to the user terminal 1 indicating "where" to apply for financing, thereby solving the problem that it is difficult for user A1 to find a financing destination that meets the conditions assumed by oneself.

[0124] In addition, the proposal server 3 transmits information indicating a specific form determined based on predetermined conditions among a plurality of forms issued when the user A1 provides a product or service to the user terminal 1. That is, the proposal server 3 makes a proposal to the user terminal 1 indicating what should be applied for as a target of financing to a predetermined financing source, so that the user A1 can solve the problem that it is difficult to find a financing source that meets the conditions assumed by the user himself / herself.

[0125] 〔Supplementary Explanation〕 Note that after the above step S53 in FIG. 20, the proposal server 3 may perform the application in step S of FIG. 1 on behalf of the user A1.

[0126] Note that the user terminal 1 is an example of a communication terminal. The user terminal 1 includes not only a PC but also a smartwatch, a game machine, a dedicated video call device, and the like. The explainer terminal is an example of another communication terminal.

[0127] Each component such as each CPU 101 may be single or multiple.

[0128] In addition, each function in the above-described embodiment can be realized by one or a plurality of processing circuits. Here, the "processing circuit" in the present embodiment includes a processor programmed to execute each function by software like a processor implemented by an electronic circuit, an ASIC (Application Specific Integrated Circuit), a DSP (Digital Signal Processor), an FPGA (Field Programmable Gate Array), an SOC (System on a chip), a GPU, and devices such as conventional circuit modules designed to execute the above-described respective functions.

[0129] Also, each of the servers 3, 5, and 7 described in the above embodiment merely represents one of a plurality of computing environments for implementing the embodiments disclosed in this specification. For example, the proposal server 3 may include a plurality of computing devices such as a server cluster. The plurality of computing devices are configured to communicate with each other via any type of communication link including a communication network or a shared memory, and implement the processes disclosed in this specification. Similarly, the proposal server 3 can include a plurality of computing devices configured to communicate with each other.

[0130] Furthermore, the proposal server 3 can be configured to share the disclosed processing steps in various combinations. For example, the process executed by the proposal server 3 can be executed by other servers. Similarly, the functions of the proposal server 3 can be executed by other servers. Also, each element of the proposal server 3 and other servers may be integrated into one server or divided into a plurality of devices.

Explanation of Signs

[0131] 1 User terminal 3 Proposal server 11 Transmission / reception unit 12 Reception unit 14 Display control unit 15 Judgment unit 19 Storage / reading processing unit 31 Transmission / reception unit (an example of transmission means, an example of reception means) 33 Calculation unit 35 Judgment unit 36 Creation unit 39 Storage / reading processing unit 100 Communication network

Prior Art Documents

Patent Documents

[0132]

Patent Document 1

Claims

1. A fund raising support server that supports fund raising based on a form issued by a user who has provided a product or service to a business partner, a receiving means for receiving condition information indicating predetermined conditions relating to the document and fundraising from the user terminal of the user; an analysis means for extracting a plurality of funding candidates based on the business partners, amounts, and payment deadlines included in the form, and calculating a commission rate and a funding amount for each of the funding candidates; a transmitting means for identifying a fund-raising source based on the predetermined conditions and the calculation results of the commission rate and the fund-raising amount, and transmitting information related to the fund-raising source to the user terminal; A fundraising support server comprising:

2. The analysis means calculates recommendation information for each of the fundraising candidates based on the creditworthiness of the business partner, past payment history, and creditworthiness obtained from a third-party credit information database; The fundraising support server according to claim 1 , wherein the information related to the fundraising source includes the recommended information.

3. A fundraising assistance server as described in claim 1 or 2, wherein the transmission means identifies the fundraising source from among the plurality of fundraising candidates calculated by the analysis means based on at least one of the priorities of lowest commission rate, earliest deposit date, and highest creditworthiness of the trading partner, and transmits information related to the fundraising source to the user terminal.

4. A fundraising support server as described in Claim 2, wherein the user terminal transmits the recommended information for a selected fundraising source from among the multiple presented fundraising sources.

5. The fundraising object type included in the document is either an invoice, a purchase order, or an estimate, The fundraising support server according to claim 2 , wherein the recommendation information includes the type of fundraising object.

6. An information processing device that supports fundraising based on a document issued by a user who has provided goods or services to a business partner, a receiving means for receiving condition information indicating predetermined conditions relating to the document and fundraising from the user terminal of the user; an analysis means for extracting a plurality of funding candidates based on the business partners, amounts, and payment deadlines included in the form, and calculating a commission rate and a funding amount for each of the funding candidates; a transmitting means for identifying a fund-raising source based on the predetermined conditions and the calculation results of the commission rate and the fund-raising amount, and transmitting information related to the fund-raising source to the user terminal; An information processing device comprising:

7. A fundraising support method executed by a fundraising support server that supports fundraising based on a document issued by a user who has provided goods or services to a business partner, comprising: a receiving step of receiving condition information indicating predetermined conditions related to the document and fundraising from the user terminal of the user; an analysis step of extracting funding candidates that are candidates for funding sources based on the business partners, amounts, and payment deadlines included in the form, and calculating a commission rate and a funding amount for each of the funding candidates; a transmission step of identifying a fund-raising source based on the predetermined conditions and the calculation results of the commission rate and the fund-raising amount, and transmitting information related to the fund-raising source to the user terminal; A fundraising support method comprising:

8. A computer that controls a fundraising support server that supports fundraising based on a document issued by a user who has provided goods or services to a business partner, a receiving means for receiving condition information indicating predetermined conditions relating to the document and fundraising from the user terminal of the user; an analysis means for extracting a plurality of funding candidates based on the business partners, amounts, and payment deadlines included in the form, and calculating a commission rate and a funding amount for each of the funding candidates; a transmitting means for identifying a fund-raising source based on the predetermined conditions and the calculation results of the commission rate and the fund-raising amount, and transmitting information related to the fund-raising source to the user terminal; A program to make it function as such.

Images