JP7793983B2 - Intermediation server, intermediation system, communication system, intermediation method, and program - Google Patents

Description

This disclosure relates to an intermediary server, an intermediary system, a communication system, an intermediary method, and a program.

In the world of commercial transactions, factoring, a method of raising funds by quickly converting accounts receivable arising from transactions into cash, is widely used. For example, Patent Document 1 discloses technology that uses a computer system to enable factoring users to apply for factoring.

Patent No. 6707700

However, even if a computer system is used, users of fundraising services such as factoring must enter the information used to raise funds for accounts receivable, etc., which creates the problem of application being time-consuming.

The invention of claim 1 is an intermediary server that communicates with one or more document management servers that create documents related to commercial transactions with business partners in response to requests from users and send the documents to the business partners, and is characterized by having: a receiving means that receives a request for review of fundraising using the document and document identification information for identifying the document, sent by the document management server based on a request for review of fundraising using the document from the user terminal of the user; and a sending means that sends the request for review of fundraising to an address of the party reviewing the fundraising , and sends review request information that includes the document identification information of the document but does not include the document .

As described above, according to the present invention, the intermediary server transmits the form identification information of the form created by the form management server to the examiner terminal, thereby eliminating the problem of fundraising users having to go through the trouble of inputting information used for fundraising.

FIG. 2 is a diagram illustrating the relationships between companies according to the present embodiment. 1 is a schematic diagram of a communication system according to an embodiment of the present invention; 2 is a hardware configuration diagram of a user terminal, an intermediary server, an examiner terminal, and a form management server according to the present embodiment. FIG. FIG. 2 is a functional block diagram of the communication system according to the embodiment. FIG. 10 is a conceptual diagram of a tenant information management table. FIG. 10 is a conceptual diagram of a billing information management table. FIG. 10 is a conceptual diagram of an invoice information management table. FIG. 10 is a conceptual diagram of a funding source management table. FIG. 10 is a conceptual diagram of an examination item information management table. FIG. 10 is a conceptual diagram of an examination management table. FIG. 10 is a conceptual diagram of an application information management table. FIG. 10 is a conceptual diagram of an account transaction details information management table. FIG. 10 is a sequence diagram showing a process in which an intermediary company sends an invoice to a trading partner company on behalf of a service using company. FIG. 10 is a diagram showing an invoice sending screen. FIG. 10 is a sequence diagram showing a process for an intermediary company to send an invoice to a trading partner company on behalf of a service using company. FIG. 10 is a diagram showing a funding source selection screen. A sequence diagram showing the registration process of provisional screening information. A figure showing an example of the display of a provisional screening information registration screen. FIG. 10 is a sequence diagram showing a process for mediating a provisional review request. FIG. 10 is a diagram showing an invoice confirmation screen. FIG. 10 is a conceptual diagram of an application information management table according to a modified example. This is a flowchart showing the initial display processing of the provisional screening information registration screen. A figure showing the provisional screening information registration screen in the second initial display mode. A figure showing a provisional screening information registration screen in the third initial display mode. This is a flowchart showing the display change process of the provisional screening information registration screen. A figure showing a provisional screening information registration screen in a submission method selection display mode. A figure showing the provisional screening information registration screen in manual transmission display mode. A sequence diagram showing the process of registering provisional screening results. A sequence diagram showing the process of registering provisional screening results. A sequence diagram showing the process of registering provisional screening results. A diagram showing a provisional review list screen. FIG. 10 is a diagram showing a deposit/withdrawal information screen. FIG. 10 is a diagram showing a transaction history information screen. FIG. 10 is a diagram showing a transaction detail information screen. FIG. 10 is a diagram showing a provisional screening result registration screen. FIG. 10 is a diagram showing an examination item setting screen. FIG. 10 is a sequence diagram showing the registration process of this review information. FIG. 10 is a diagram showing a fundraising application list screen. FIG. 10 is a diagram showing a provisional screening result list screen.

[Inter-company relationships]
The relationships between the companies will be described with reference to Figure 1. Figure 1 is a diagram showing the relationships between the companies according to this embodiment.

As shown in Figure 1, service user company A is a company that uses the service provided by intermediary company C to apply for funding on behalf of other companies. Client company B is a client of service user company A. In this case, a relationship may arise in which service user company A is the creditor and client company B is the debtor. Intermediary company C is a company that provides the above service to service user company A.

Factoring service company D, accounts receivable financing service company E, PO finance company F, and quotation finance service company G are companies that provide the services listed above, and are all funding service companies. From the perspective of service user company A, funding service companies are sources of funding.

Factoring service company D is a collective term for multiple factoring service companies D1, D2, ... Dn. Accounts receivable secured loan service company E is a collective term for multiple accounts receivable secured loan service companies E1, E2, ... En. PO finance service company F is a collective term for multiple PO finance service companies F1, F2, ... Fn. Quotation finance service company G is a collective term for quotation finance service companies G1, G2, ... Gn.

Here, we will provide an overview of the processing in this embodiment.

First, service user company A provides or plans to provide goods or services to trading partner company B, resulting in accounts receivable. In this state, service user company A uses the document management service provided by intermediary company C to request intermediary company C to send an invoice to trading partner company B (S1). In response, intermediary company C issues an invoice and sends it to trading partner company B (S2). The processing up to this point represents the invoice issuance service provided by intermediary company C.

Furthermore, service user company A uses the intermediary service provided by intermediary company C to request that intermediary company C apply for funding on its behalf to the funding service company (S3). As a result, intermediary company C reuses the invoice issued by the invoice issuance service to apply for funding on its behalf to the funding service company (S4). Service user company A then raises funds from the funding service company (S5).

Thereafter, trading partner company B pays the accounts receivable related to the invoice to service user company A on the due date (S6). As a result, service user company A repays the funding to the funding service company (S7).

[Communication system overview]
2 is a schematic diagram of the communication system of this embodiment, showing the terminals or servers of each company in FIG.

User company A is equipped with a user terminal 1, such as a PC (personal computer), which is operated by user A1. Intermediary company C is equipped with a form management server 2 and an intermediary server 3. The form management server 2 and intermediary server 3 constitute an intermediary system 4.

Factoring service company D, accounts receivable financing service company E, PO finance service company F, and quotation finance service company G are each provided with examiner terminals 5d, 5e, 5f, and 5g, such as PCs. Examiner terminals 5d, 5e, 5f, and 5g are operated by examiners D1, E1, F1, and G1, respectively.

The user terminal 1, examiner terminals 5d, 5e, 5f, and 5g, the form management server 2, and the intermediary server 3 can communicate via a communications network 100 such as the Internet. Hereinafter, the examiner terminals 5d, 5e, 5f, and 5g will be collectively referred to as the "examiner terminal 5."

[Hardware configuration of communication system]
Next, the hardware configuration of each terminal and server that constitutes the communication system shown in Fig. 1 will be explained using Fig. 3. Since all of them have the same configuration, the hardware configuration of the user terminal 1 will be explained, and the explanation of the hardware configuration of each server will be omitted.

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

Of these, CPU 101 controls the operation of the entire computer. ROM 102 stores programs used to drive CPU 101, such as IPL. RAM 103 is used as a work area for CPU 101. HD 104 stores various data, such as programs. HDD controller 105 controls the reading and writing of various data from HD 104 under the control of CPU 101. Display 106 displays various information, such as a cursor, menu, window, text, or image. External device connection I/F 108 is an interface for connecting various external devices. In this case, external devices include, for example, USB (Universal Serial Bus) memory and printers. Network I/F 109 is an interface for data communication using communication network 100. Bus line 110 is an address bus, data bus, etc. for electrically connecting each component, such as CPU 101, shown in Figure 3.

The keyboard 111 is a type of input device equipped with multiple keys for inputting characters, numbers, various instructions, etc. The pointing device 112 is a type of input device for selecting and executing various instructions, selecting processing targets, moving the cursor, etc. The DVD-RW drive 114 controls the reading and writing of various data from a DVD-RW 113, which is an example of a removable recording medium. Note that this is not limited to a DVD-RW, and may also be a DVD-R or Blu-ray Disc (registered trademark). The media I/F 116 controls the reading and writing (storage) of data from a recording medium 115, such as a flash memory.

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

[Functional configuration of the communication system]
Next, the functional configuration of the communication system of this embodiment will be described with reference to Figures 3 to 12. Figure 4 is a block diagram showing the functions of the communication system according to this embodiment.

<Functional configuration of user terminal>
First, the functional configuration of the user terminal 1 will be described using Figures 3 and 4. As shown in Figure 4, the user terminal 1 has a transmission/reception unit 11, a reception unit 12, a display control unit 14, a determination unit 15, and a storage/readout processing unit 19. Each of these units is a function or a means for performing a function that is realized when any of the components shown in Figure 3 operates in response to an instruction from the CPU 101 in accordance with a program loaded from the HD 104 onto the RAM 103. The user terminal 1 also has a storage unit 1000 constructed by the RAM 103 and HD 104 shown in Figure 3.

(Functional configuration of user terminal)
Next, we will explain each component of the user terminal 1. The transmission/reception unit 11 is realized by commands from the CPU 101 shown in Fig. 3, 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.

The reception unit 12 is realized mainly by commands from the CPU 101 shown in Figure 3, as well as the keyboard 111 and pointing device 112, and receives various inputs from the user.

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

The judgment unit 15 is mainly realized by commands from the CPU 101 shown in Figure 3, and makes various judgments.

The storage/read processing unit 19 is mainly realized by commands from the CPU 101 and the HDD controller 105 shown in Figure 3, and performs processes such as storing various data in the storage unit 1000 and reading various data stored in the storage unit 1000.

<Functional configuration of the report management server>
Next, the functional configuration of the form management server 2 will be described with reference to Figures 3 to 7. As shown in Figure 4, the form management server 2 has a transmission/reception unit 21, a determination unit 25, a creation unit 26, and a storage/readout processing unit 29. Each of these units is a function or a means for performing a function that is realized when any of the components shown in Figure 3 operates in response to an instruction from the CPU 101 in accordance with a program loaded from the HD 104 onto the RAM 103. The form management server 2 also has a storage unit 2000 constructed by the RAM 103 and HD 104 shown in Figure 3.

(Tenant Information Management Table)
5 is a conceptual diagram showing a tenant information management table. A tenant information management DB 2001 configured with a tenant information management table such as that shown in FIG. 5 is created in the storage unit 2000. This table shows information related to tenants as service-using companies. Therefore, in this table, the tenant ID, the tenant name (company name, trade name, etc.), the tenant address (location), the tenant's industry, the start date and time of use of the form management service, bank account information, and connection destination information (URL, etc.) for the linked service are associated and managed as tenant information.

(Billing Information Management Table)
Fig. 6 is a conceptual diagram showing a billing information management table. A billing information management DB 2002 configured with a billing information management table such as that shown in Fig. 6 is constructed in the storage unit 2000. This table shows details related to corporate information to which invoices are sent for each tenant as a service using company. In this table, for each tenant ID indicating the source of the bill, a billing ID, billing name (or individual name), address, telephone number, email address, name of person in charge, and bank account information are associated and managed as billing information.

(Invoice information management table)
7 is a conceptual diagram showing an invoice information management table. The storage unit 2000 has an invoice information management DB 2003 configured with an invoice information management table such as the one shown in FIG. 7. This table shows the contents of invoices created by intermediary company C on behalf of service-using companies. Therefore, in this table, for each tenant ID, the following information is associated and managed as invoice information: invoice number (document ID), invoice recipient ID, invoice recipient name, invoice amount, payment due date, invoice image, delivery date, payment status, payment date, and deposit account.

(Functional configuration of the form management server)
Next, a detailed description will be given of each functional configuration of the form management server 2. In the following, when describing each functional configuration of the form management server 2, the relationship between each component shown in Fig. 3 and the main components for realizing each functional configuration of the form management server 2 will also be described.

The transmission/reception unit 21 of the document management server 2 shown in Figure 4 is realized by commands from the CPU 101 and the network I/F 109 shown in Figure 3, and transmits and receives various data (or information) to and from other terminals, devices, or systems via the communication network 100.

The judgment unit 25 is implemented by commands from the CPU 101 shown in Figure 3 and makes a predetermined judgment. The contents of the judgment will be described later.

The creation unit 26 is implemented by commands from the CPU 101 shown in Figure 3, and creates the screens to be displayed, etc.

The storage/readout processing unit 29 is realized by commands from the CPU 101 and the HDD controller 105 shown in Figure 3, and performs processes such as storing various data in the storage unit 3000 and reading various data stored in the storage unit 3000.

<Functional configuration of the intermediary server>
Next, the functional configuration of the intermediary server 3 will be described using Figures 3, 4, and 8 to 12. As shown in Figure 4, the intermediary server 3 has a transmission/reception unit 31, a determination unit 33, a judgment unit 35, a creation unit 36, and a storage/readout processing unit 39. Each of these units is a function or a means for performing a function that is realized when any of the components shown in Figure 3 operates in response to an instruction from the CPU 101 in accordance with a program loaded from the HD 104 onto the RAM 103. The intermediary server 3 also has a storage unit 3000 constructed by the RAM 103 and HD 104 shown in Figure 3.

(Funding source management table)
FIG. 8 is a conceptual diagram showing a fund-raising source management table. A fund-raising source management DB 3001, which is configured using the fund-raising source management table shown in FIG. 8, is stored in the storage unit 3000. This table displays information about companies that are fund-raising sources. Therefore, this table manages the fund-raising source information by associating the following: type of fund-raising source, service name (company name), industries in which the fund-raising source specializes, industries in which the fund-raising source does not support, regions in which the fund-raising source can provide funding, whether or not the fund-raising source supports sole proprietorships, the maximum amount supported, deposit speed, the username, password, email address, and name of the person in charge at the fund-raising service company, and the details of the PR input contract for the fund-raising service company. This person in charge corresponds to the examiners D1, E1, F1, and G1 in FIG. 2.

(Examination item information management table)
FIG. 9 is a conceptual diagram showing an examination item information management table. A examination item information management DB 3002 configured with an examination item information management table such as that shown in FIG. 9 is constructed in the storage unit 3000. This table indicates the period (in months) of evidential information required for the examination of fund-raising at a fund-providing service company (service name). Therefore, this table associates and manages the period of evidential information for each service name. For example, when service user company A (or intermediary company C) applies for fund-raising to a fund-providing service company, which is service D1, the service user company A must prepare information such as deposit and withdrawal transactions of the service user company for the past six months as evidential information for the examination by the fund-providing service company.

In addition, the screening item information is registered in advance in the screening item information management DB 3002 by an administrator at intermediary company C based on the screening conditions disclosed by each funding service.

(Review management table)
Figure 10 is a conceptual diagram showing an examination management table. A examination management DB 3003 configured with an examination management table such as that shown in Figure 10 is constructed in the storage unit 3000. This table shows the examination status of each fundraising application for each fund-providing service company. Therefore, this table associates and manages, for each service provider as a fund-providing service company, the fund-raising application ID, provisional examination status, main examination status, and examination result information, which is information related to the examination result.

(Application Information Management Table)
11 is a conceptual diagram showing an application information management table. The storage unit 3000 has constructed an application information management DB 3004 configured with the application information management table shown in FIG. 11 . This table shows information related to fundraising applications. Therefore, this table associates and manages information related to the application ID, invoice number (document ID), information related to the service using company (name of the company making the request, address of the company making the request), information related to the business partner company (name of the company to be billed, address of the company to be billed), the billed amount, the due date for payment of the invoice, the date of issuance of the invoice, and the application date, which is the date on which the application for review of fundraising using the invoice was made.

(Account Transaction Detail Information Management Table)
Figure 12 is a conceptual diagram showing an account transaction statement information management table. A fund provision service management DB 3005, which is configured using the account transaction statement information management table shown in Figure 12, is stored in the storage unit 3000. This table manages transaction statement information for the bank accounts of service-using companies. Therefore, this table manages information related to the transaction date and time, payment amount, payee, deposit amount, deposit source, and balance in association with each other.

<Functional configuration of examiner terminal>
Next, the functional configuration of the examiner terminal 5 will be described with reference to Figures 3 and 4. As shown in Figure 4, the examiner terminal 5 has a transmission/reception unit 51, a reception unit 52, a display control unit 54, a judgment unit 55, and a storage/readout processing unit 59. Each of these units is a function or a means for performing a function that is realized when any of the components shown in Figure 3 operates in response to an instruction from the CPU 101 in accordance with a program loaded from the HD 104 onto the RAM 103. The user terminal 1 also has a memory unit 5000 constructed by the RAM 103 and HD 104 shown in Figure 3.

Note that the individual components of the examiner terminal 5 (transmission/reception unit 51, reception unit 52, display control unit 54, judgment unit 55, and storage/readout processing unit 59) perform the same functions as the individual components of the user terminal 1 (transmission/reception unit 11, reception unit 12, display control unit 14, judgment unit 15, and storage/readout processing unit 19), and therefore will not be described here.

[Processing or Operation of the Embodiment]
Next, the processing or operation of this embodiment will be described with reference to FIGS.

<Invoice sending process>
First, the process of sending an invoice on behalf of a service user company by an intermediary company will be described with reference to Figures 13 and 14. Figure 13 is a sequence diagram showing the process of sending an invoice to a business partner company on behalf of a service user company. Figure 14 is a diagram showing the invoice sending screen.

First, in the user terminal 1 of service using company A, the reception unit 12 receives an operation from user A1 to instruct the display of an invoice sending screen (S41). Specifically, the reception unit 12 receives an operation by user A1 to click a button included in a specific screen displayed on the user terminal 1. Before receiving the operation from user A1 to instruct the display of the invoice sending screen, the reception unit 12 also receives authentication information, such as a tenant ID, entered by user A1. The transmission/reception unit 11 then transmits the authentication information to the form management server 2, which then performs a specific authentication process. Therefore, the reception unit 12 can only receive an operation from user A1 to instruct the display of the invoice sending screen if user A1 has been authenticated.

Next, the transmission/reception unit 11 of the user terminal 1 sends a request for the invoice delivery screen to the form management server 2 (S42). As a result, the transmission/reception unit 21 of the form management server 2 receives the request for the invoice delivery screen.

Next, in the form management server 2, the creation unit 26 creates screen data for the invoice delivery screen as shown in FIG. 14 in response to the request for the invoice delivery screen (S43). The transmission/reception unit 21 then transmits the created screen data to the user terminal 1 (S44). The display control unit 14 of the user terminal 1 displays the invoice delivery screen on the display 106 based on the transmitted screen data (S45).

Figure 14 is a diagram showing an example of the invoice delivery screen displayed on user terminal 1. As shown in Figure 14, the invoice delivery screen includes items such as a first check box c21 for setting whether to request a preliminary review of funding using the invoice to be sent, a second check box c22 for setting whether to send the invoice by mail, and a delivery instruction button b21 for instructing delivery. In addition, the subject and body of the invoice when sent by email are displayed on the invoice delivery screen. Pre-registered information may be set as the subject and body, or user A1 may set them by inputting them via a specified screen.

Using this invoice sending screen, user A1 sets the email address to which the invoice will be sent by email, then uses the first checkbox c21 to set whether or not to request a preliminary funding review using the invoice to be sent, uses the second checkbox c22 to set whether or not to send the invoice by mail, and finally clicks the send instruction button b21 to instruct the invoice to be sent. The reception unit 12 of the user terminal 1 accepts the operation to instruct the invoice to be sent (S46).

Next, the transceiver unit 11 of the user terminal transmits to the document management server 2 a request to send the invoice, the invoice number, and information indicating whether or not a preliminary review of fundraising using the invoice has been requested (S47).

Next, on the document management server 2, the storage/readout processing unit 29 searches the invoice information management DB 2003 using the transmitted invoice number as a search key to identify the invoice information corresponding to that invoice number, and registers the date on which the invoice was instructed to be sent as the field value of the sending date field included in the invoice information (S48).

Finally, the sending/receiving unit 21 of the document management server 2 sends an email with an invoice image of the invoice attached as an attachment to the email address set by user A1 (S49). Furthermore, if the second checkbox c22 is set to send the invoice by mail, the sending/receiving unit 21 sends the invoice image of the invoice to a printing device, which prints out the invoice image. The invoice is then sent from service using company A to business partner company B.

<Proxy invoice sending process>
Next, the proxy invoice sending process will be described with reference to Figures 15 and 16. Figure 15 is a sequence diagram showing the process by which an intermediary company sends an invoice to a trading partner company on behalf of a service user company. Figure 16 is a diagram showing a funding source selection screen.

First, in the document management server 2, the judgment unit 25 judges whether a fundraising review request is necessary based on information indicating whether or not a request for a provisional fundraising review using an invoice sent from the user terminal 1 has been made (S61). That is, the judgment unit 25 judges that a fundraising review request is "necessary" when user A1 instructs the sending of an invoice by checking the first checkbox c21 on the invoice sending screen, and judges that a fundraising review request is "unnecessary" when user A1 instructs the sending of an invoice by unchecking the first checkbox c21 on the invoice sending screen. The following describes the processing that occurs when the judgment unit 25 judges that a fundraising review request is "necessary."

Next, the storage/read processing unit 29 searches the tenant information management DB 2001 using the tenant ID of user A1 as a search key, and reads out the tenant information corresponding to the tenant ID as billing information (S62). The storage/read processing unit 29 then reads out the invoice information identified in step S61, and searches the invoice information management DB 2002 using the billing destination ID included in the invoice information as a search key, and reads out the billing destination information corresponding to the billing destination ID (S63).

Next, the transmitter/receiver unit 21 transmits a request for preliminary funding review, invoice information, billing source information, and billing destination information to the intermediary server 3.

Next, in the intermediary server 3, the determination unit 33 determines fundraisers from which an examination can be requested based on the transmitted requestor information (S65). Specifically, the determination unit 33 determines whether the requestor's business type is a sole proprietorship based on the company name and trade name included in the requestor information, and obtains the address and industry included in the requestor information. The storage/reading processing unit 39 then reads out fundraising information corresponding to the requestor's business type, the region indicated by the address, and the industry from each piece of fundraising source information registered in the fundraising source management DB 3001. The determination unit 33 determines the fundraising source corresponding to the read fundraising information as a fundraising source from which an examination can be requested.

Next, the creation unit 36 of the intermediary server 3 creates screen data for a funding source selection screen based on the funding source information of the determined funding source (S66). Specifically, the creation unit 36 creates screen data for a funding source list screen that displays information such as the service name and PR input contract included in the funding source information. The transmission/reception unit 31 then transmits the created screen data to the user terminal 1 (S67). The display control unit 14 of the user terminal 1 displays the funding source selection screen on the display 106 based on the transmitted screen data (S68).

Figure 16 is an example of a fundraising source selection screen displayed on user terminal 1. As shown in Figure 16, the fundraising source selection screen includes the service name and promotional information for each fundraising source, check boxes c31, c32, c33, c34, and c35 for selecting the fundraising source for which a provisional screening is to be applied, and a button b31 for confirming the selection of the fundraising source and moving to the next screen. User A1 can select the fundraising source for which a provisional screening is to be applied by checking the check box corresponding to the fundraising source for which they wish to apply for a provisional screening and clicking button b31.

<Registration process for provisional screening information>
Next, the provisional screening information registration process will be explained using Figures 17, 18 and 19. Figure 17 is a sequence diagram showing the provisional screening information registration process. Figure 18 is a diagram showing an example of the display of the provisional screening information registration screen. Figure 19 is a diagram showing an invoice confirmation screen.

First, on the user terminal 1, the reception unit 12 receives an operation to select a fundraising source (S81). Specifically, the reception unit 12 receives an operation to check a checkbox corresponding to the fundraising source and an operation to click button b31. Then, the transmission/reception unit 11 transmits a request for the screening information registration screen and the service name of the selected fundraising source to the intermediary server 3 (S82).

Next, in the intermediary server 3, the determination unit 33 determines the period of evidential documentation required for the review. Specifically, the storage/read processing unit 39 searches the review item information management table using the service name of the fundraising source transmitted as a search key, thereby reading out the period of evidential information corresponding to each service name. The determination unit 33 then determines the longest period of the periods of each piece of evidential information read out as the period of evidential documentation required for the review. For example, if user A1 selects service D1, service D2, service D3, and service D4, the periods of evidential information corresponding to these services, respectively, are identified as 6 months, 24 months, 12 months, and 7 months. Of these, the longest period, 24 months, is determined as the period of evidential documentation required for the review (S83).

Next, the transmitter/receiver unit 31 of the intermediary server 3 sends a request for first review information, the billing source ID, the billing recipient ID, and the determined period for the evidential documents to the document management server 2 (S84). The first review information is information indicating the history of commercial transactions between service using company A and trading partner company B, such as invoice information for invoices issued by service using company A to trading partner company B, and information indicating the payment status from trading partner company B to service using company A for the amount claimed on the invoice.

Next, the storage and readout processing unit 29 of the document management server 2 identifies the range of invoice information to read based on the period of the transmitted documentary evidence and the current date. In other words, it identifies the range of sending dates included in the invoice information. For example, if the period of the documentary evidence is "24 months," it identifies the range from the current date to 24 months prior to the current date. Then, the storage and readout processing unit 29 searches the invoice information management DB 2003 using the transmitted billing source ID, billing destination ID, and the identified range of sending dates as search keys, and reads out invoice information including the billing source ID and billing destination ID within the range defined by the period of the documentary evidence as first review information (S85).

Next, the transmission/reception unit 21 of the document management server 2 transmits the read first review information to the intermediary server 3 (S86). Then, in the intermediary server 3, the creation unit 36 creates screen data for a provisional review information registration screen, including the invoice number and information indicating whether or not a linked service is being used, based on the invoice information, billing source information, and billing destination information transmitted in step S64 and the first review information transmitted in step S86 (S87). Then, the transmission/reception unit 31 transmits the created screen data to the user terminal 1 (S88).

Next, on the user terminal 1, the display control unit 14 displays the provisional screening information registration screen on the display 106 based on the transmitted screen data (S89).

Figure 18 is an example of the provisional screening information registration screen displayed on the user terminal 1. As shown in Figure 18, the provisional screening information registration screen includes a field f41 indicating the invoice number, a confirmation button b41 for confirming the invoice image, a registration button b42 for registering the financial statement, a registration button b43 for registering the basic contract, a setting area a41 for setting the method of submitting evidentiary information, a back button b48, and an execute button b49. The provisional screening information registration screen also includes billing source information (your company information) such as the billing company name and address, and billing destination information (accounts receivable information) such as the billing recipient company name and address. Furthermore, the setting area a41 includes a radio button for setting whether or not to automatically send transaction history. The radio button has two options: "Yes" r41 and "No" r42.

Next, on the user terminal 1, the reception unit 12 receives an instruction to obtain an invoice image (S90). Specifically, the reception unit 12 receives an instruction to click the confirmation button b41. The transmission/reception unit 11 then transmits a request for an invoice image and the invoice number of the requested invoice to the document management server 2 (S91).

Next, on the document management server 2, the storage/read processing unit 29 searches the invoice information management DB 2003 using the transmitted invoice number as a search key to identify the storage location of the invoice image corresponding to the invoice number, and reads the invoice image from the identified storage location (S92). The transmission/reception unit 21 transmits the read invoice image to the user terminal 1 (S93).

Finally, the display control unit 14 of the user terminal 1 displays an invoice confirmation screen including the transmitted invoice image (S94). Figure 19 is an example of the invoice confirmation screen displayed on the user terminal 1. As shown in Figure 19, the invoice confirmation screen includes an invoice image g51 and an OK button b51. When user A1 checks the invoice image g51 and clicks the OK button b51, the invoice confirmation screen closes and the provisional screening information registration screen is displayed.

<Intermediary processing of preliminary screening requests>
Next, the intermediation process for a provisional review request will be described with reference to Fig. 20. Fig. 20 is a sequence diagram showing the process for intermediating a provisional review request.

First, on the user terminal 1, the reception unit 12 receives an operation to set the method for submitting documentary evidence (S101). Specifically, the reception unit 12 receives an operation to select either the radio button options "Yes" r41 or "No" r42. If "Yes" r41 is selected, the examination is performed using the first examination information received by the intermediary server 3 in step S88. On the other hand, if "No" r42 is selected, the examination is performed using the second examination information described below.

Next, the reception unit 12 accepts an operation to input provisional screening information (S102). Specifically, the reception unit 12 accepts an operation to press the registration button b42 and an operation to select an image of the financial statement to be registered. The reception unit 12 also accepts an operation to press the registration button b43 and an operation to select an image of the master contract to be registered. Furthermore, the reception unit 12 accepts an operation to modify billing source information (your company information), such as the billing company name and address, and billing destination information (accounts receivable information), such as the billing recipient company name and address. This completes the input of the information required for the provisional screening.

Next, the reception unit 12 receives an operation to request a provisional review (S103). Specifically, the reception unit 12 receives an operation to click the Execute button b49. Note that clicking the Back button b48 returns to the fundraising source selection screen of FIG. 16. The transmission/reception unit 11 then transmits the provisional review request request and the input information entered via the provisional review information registration screen to the intermediary server 3 (S104).

Next, in the intermediary server 3, the judgment unit 35 judges whether or not to automatically transmit deposit and withdrawal information based on the input information transmitted (S105). Specifically, based on the information contained in the input information indicating whether or not to automatically transmit the transaction history, the judgment unit 35 judges that automatic transmission of deposit and withdrawal information is "not permitted" if automatic transmission of the transaction history is to be permitted, and on the other hand, judges that automatic transmission of deposit and withdrawal information is "permitted" if automatic transmission of the transaction history is not to be permitted. Below, the processing performed when it is determined that automatic transmission of deposit and withdrawal information is "permitted" will be described.

The transmitter/receiver unit 31 of the intermediary server 3 sends a request for deposit/withdrawal information and the tenant ID to the document management server 2 (S106). Then, in the document management server 2, the storage/readout processing unit 29 acquires the deposit/withdrawal information corresponding to the transmitted tenant ID (S107), and the transmitter/receiver unit 21 transmits the acquired deposit/withdrawal information to the intermediary server 3 (S108).

Next, in the intermediary server 3, the storage/read processing unit 39 associates the received deposit/withdrawal information with the tenant ID and registers it in the funding service management DB 3005 (S109). The storage/read processing unit 39 also registers the provisional review request information in the application information management DB 3004 (S110). Specifically, the storage/read processing unit 39 associates the invoice information received in step S64 and the input information received in step S104 with an application ID for identifying the provisional review request information to be registered and registers them in the application information management DB 3004. Furthermore, the storage/read processing unit 39 registers information such as the application ID of the provisional review request information registered in the application information management DB 3004 in the review management DB 3003 for each service to which the review is requested (S111). Here, the storage/read processing unit 39 registers "Under review" as the item value for the provisional review status and "Empty" as the item values for the main review status and review result information.

Finally, the transmission/reception unit 31 of the intermediary server 3 transmits the registered provisional review request information and provisional review request notice to the examiner terminal 5 (S112). Specifically, the storage/read processing unit 39 obtains email addresses corresponding to each of the services for which the review has been requested from the funding source management DB 3001, and the transmission/reception unit 31 creates an email containing the registered provisional review request information and sends the email to each of the obtained email addresses. Note that the method of transmitting the provisional review request information and provisional review request notice is not limited to email. For example, a message containing the provisional review request information may be sent to the examiner terminal 5 via a messenger app.

The examiner then conducts the provisional examination based on the provisional examination request information sent to the examiner terminal 5 and registers the results of the provisional examination in the examination management DB 3003.

<Initial display process of provisional screening information registration screen>
In the example of the provisional screening information registration screen shown in Figure 18, it is possible to input whether or not to automatically send transaction history as evidence information, and the intermediary server 3 determines whether or not to automatically send deposit and withdrawal information based on the input information on the provisional screening information registration screen (see S105). Below, we will explain a modified example in which it is possible to input whether or not to automatically send deposit and withdrawal information on the provisional screening information registration screen, and to manually send deposit and withdrawal information as needed.

(Application Information Management Table)
21 is a conceptual diagram showing an application information management table in this modified example. In this application information management table, information related to the application ID, invoice number (document ID), information about the service using company (name of the billing company, address of the billing company, email address of the billing company), information about the business partner company (name of the billing company, address of the billing company), invoice amount, invoice payment due date, invoice issue date, and application date, which is the date on which the application for funding review using the invoice was made, as well as information related to the storage location of images showing deposit and withdrawal information, the storage location of images showing the basic contract, and the storage location of images showing the financial statement are managed in association with each other.

The display processing of the provisional screening information registration screen of the modified example will be explained using Figures 22 to 24. Figure 22 is a flowchart showing the initial display processing of the provisional screening information registration screen of the modified example. The flowchart shown in Figure 22 is executed in step S89 when the display control unit 14 displays the provisional screening information registration screen.

First, on the user terminal 1, the judgment unit 15 calculates the period from the tenant's start date of use to a specified date (S891). To this end, in this modified example, in step S87, the creation unit 36 of the intermediary server 3 includes the service user company A's start date of use and the period of the supporting documents required for the review in the screen data of the provisional review information registration screen. The specified date is the date used as the basis for calculating the period from the start date of use, and is, for example, the current date, the last day of the previous month, or the first day of the previous month.

Next, the judgment unit 15 of the user terminal 1 determines whether the period calculated in step S891 exceeds the period of the documentary evidence required for the review (S892). If the calculated period is less than or equal to the period of the documentary evidence required for the review (NO), the judgment unit 15 determines whether a linked service is available based on information indicating whether a linked service is being used, contained in the screen data of the provisional review information registration screen (S893). On the other hand, if the calculated period exceeds the period of the documentary evidence required for the review (YES), the display control unit 14 displays the provisional review information registration screen on the display 106 in the first initial display mode (S894).

If it is determined in step S893 that a linked service exists (YES), the display control unit 14 displays the provisional screening information registration screen on the display 106 in the second initial display mode (S895). On the other hand, if it is determined in step S893 that a linked service does not exist (NO), the display control unit 14 displays the provisional screening information registration screen on the display 106 in the third initial display mode (S896).

Figure 18 shows an example of the display of the provisional screening information registration screen in the first initial display mode. As shown in Figure 18, in the first initial display mode, the setting area a41 includes radio buttons with the options "Yes" r41 and "No" r42 for automatically sending transaction history. In the first initial display mode, "Yes" r41 is displayed selected.

Figure 23 is a diagram showing an example of the display of the provisional screening information registration screen in the second initial display mode. As shown in Figure 23, on the provisional screening information registration screen in the second initial display mode, the setting area a41 includes radio buttons with the options "Yes" r41 and "No" r42 for automatically sending transaction history, as well as radio buttons with the options "Automatically send deposit/withdrawal information" r43 and "Manually send deposit/withdrawal information" r44, and a register button b44 for registering deposit/withdrawal information. In the second initial display mode, "Yes" r41 and "Automatically send deposit/withdrawal information" r43 are displayed in a selected state. The register button b44 is initially displayed in a non-pressable state. The register button b44 becomes pressable when "Manually send deposit/withdrawal information" r44 is selected.

Figure 24 shows an example of the display of the provisional screening information registration screen in the third initial display mode. As shown in Figure 24, on the provisional screening information registration screen in the third initial display mode, the setting area a41 includes radio buttons with the options "Yes" r41 and "No" r42 for automatically sending transaction history, as well as a registration button b44 for registering deposit and withdrawal information.

<Display change process on the provisional screening information registration screen>
The display change process of the provisional screening information registration screen of the modified example will be explained using Figures 25 to 27. Figure 25 is a flowchart showing the display change process of the provisional screening information registration screen of the modified example. The flowchart shown in Figure 25 is executed when the reception unit 12 receives an operation to select "Do not automatically send" r42 of the transaction history in step S101.

First, on the user terminal 1, the reception unit 12 receives an operation to select "Do not automatically send" r42 for transaction history (S1011). Next, the judgment unit 15 determines whether the provisional screening information registration screen is displayed in the first initial display mode (S1012). If it is displayed in the first initial display mode (YES), the judgment unit 15 determines whether a linked service is available based on information indicating whether a linked service is being used, which is included in the screen data of the provisional screening information registration screen (S1013). On the other hand, if it is not displayed in the first initial display mode (NO), the processing is terminated.

If it is determined in step S1013 that a linked service is available (YES), the display control unit 14 re-displays the provisional screening information registration screen on the display 106 in the submission method selection display mode (S1014). On the other hand, if it is determined in step S1013 that a linked service is not available (NO), the display control unit 14 re-displays the provisional screening information registration screen on the display 106 in the manual transmission display mode (S1015).

Figure 26 is a diagram showing an example of the display of the provisional screening information registration screen in the submission method selection display mode. As shown in Figure 26, in the submission method selection display mode, the setting area a41 includes radio buttons with the options "Yes" r41 and "No" r42 for automatically sending transaction history, as well as radio buttons with the options "Automatically send deposit/withdrawal information" r43 and "Manually send deposit/withdrawal information" r44, and a registration button b44 for registering deposit/withdrawal information. In the submission method selection display mode, "No" r42 and "Automatically send deposit/withdrawal information" r43 are displayed selected.

Figure 27 shows an example of the display of the provisional screening information registration screen in the manual transmission display mode. As shown in Figure 27, on the provisional screening information registration screen in the manual transmission display mode, the setting area a41 includes radio buttons with the options "Yes" r41 and "No" r42 for automatically transmitting transaction history, as well as a registration button b44 for registering deposit and withdrawal information.

<Registration process for provisional screening results>
Next, the process of registering the provisional screening results will be described with reference to Figures 28 to 36. Figures 28 to 30 are sequence diagrams showing the process of conducting a provisional screening based on provisional screening request information and registering the results.

First, at the examiner terminal 5 of the funding service company, the reception unit 52 receives an operation from the examiner to instruct the display of the provisional review list screen (S121). Specifically, the reception unit 52 receives an operation by the examiner to click a button included in a specific screen displayed on the examiner terminal 5. The reception unit 52 also receives authentication information entered by the examiner before receiving an operation from the examiner to instruct the display of the provisional review list screen. The transmission/reception unit 51 then transmits the authentication information to the intermediary server 3, and the intermediary server 3 performs a specific authentication process. Therefore, the reception unit 52 can only receive an operation from the examiner to instruct the display of the provisional review list screen if the examiner is authenticated.

Next, the transmission/reception unit 51 of the examiner terminal 5 sends a request for the provisional examination list screen to the intermediary server 3 (S122). As a result, the transmission/reception unit 31 of the intermediary server 3 receives the request for the provisional examination list screen.

Next, in the intermediary server 3, the storage/read processing unit 39 reads out the review information registered in the review management DB 3003 and the application information registered in the application information management DB 3004. The creation unit 36 creates screen data for a provisional review list screen such as that shown in FIG. 31 based on the read review information and application information (S123). The transmission/reception unit 31 then transmits the created screen data to the examiner terminal 5 (S124). The display control unit 54 of the examiner terminal 5 displays the provisional review list screen on the display 106 based on the transmitted screen data (S125).

Figure 31 is a diagram showing an example of the provisional review list screen displayed on the examiner terminal 5. As shown in Figure 31, the provisional review list screen includes a display area a61 for displaying a list of application information, a display button b67 for displaying the review item setting screen, a display button b68 for displaying all application information, and a display button b69 for displaying only application information currently under provisional review. Each application information displayed in the display area a61 includes a confirmation button b61 for checking the invoice image, a display button b62 for displaying the deposit/withdrawal information screen, a display button b63 for displaying the transaction history information screen, a display button b64 for displaying the transaction detail information screen, and a display button b65 for displaying the provisional review result registration screen.

Returning to Figure 28, the explanation will be made. On the examiner terminal 5, the reception unit 52 receives an operation to instruct the acquisition of an invoice image (S126). Specifically, the reception unit 52 receives an operation to click the confirmation button b61 on the provisional examination list screen. Then, the transmission/reception unit 51 transmits a request for the invoice image and the invoice number to the document management server 2 (S127).

Next, on the document management server 2, the storage/readout processing unit 29 searches the invoice information management DB 2003 using the transmitted invoice number as a search key to identify the storage location of the invoice image corresponding to the invoice number, and reads out the invoice image from the identified storage location (S128). The transmission/reception unit 21 transmits the read-out invoice image to the examiner terminal 5 (S129).

Next, the display control unit 54 of the examiner terminal 5 displays an invoice confirmation screen including the transmitted invoice image (S130). An example of the invoice confirmation screen displayed on the examiner terminal 5 is shown in Figure 19. When the examiner checks the invoice image g51 and clicks the OK button b51, the invoice confirmation screen closes and the provisional review list screen is displayed.

Next, on the examiner terminal 5, the reception unit 52 receives an operation from the examiner instructing the display of the deposit/withdrawal information screen (S131). Specifically, the reception unit 52 receives an operation to click the display button b62 on the provisional examination list screen. The transmission/reception unit 51 then transmits a request for the deposit/withdrawal information screen and the tenant ID to the intermediary server 3 (S132). As a result, the transmission/reception unit 31 of the intermediary server 3 receives the request for the deposit/withdrawal information screen and the tenant ID.

Next, in the intermediary server 3, the storage/read processing unit 39 reads the deposit/withdrawal information corresponding to the transmitted tenant ID from the funding service management DB 3005. The creation unit 36 creates screen data for a deposit/withdrawal information screen such as that shown in FIG. 32 based on the read deposit/withdrawal information (S133). The transmission/reception unit 31 then transmits the created screen data to the examiner terminal 5 (S134). The display control unit 54 of the examiner terminal 5 displays the deposit/withdrawal information screen on the display 106 based on the transmitted screen data (S135).

Figure 32 is a diagram showing an example of the deposit/withdrawal information screen displayed on the examiner terminal 5. As shown in Figure 32, the deposit/withdrawal information screen includes deposit/withdrawal list display tabs t71 and t72 for displaying a list of deposit/withdrawal information for each bank account, a confirmation button b76 for confirming the passbook image, a print button b77, and an OK button b78. The same number of deposit/withdrawal list display tabs are displayed as there are bank accounts registered in the tenant information management DB 2001.

When the reception unit 52 receives an operation to click the confirmation button b76, the transmission/reception unit 51 transmits a request for a deposit/withdrawal information image and the invoice number to the intermediary server 3. In the intermediary server 3, the storage/readout processing unit 39 searches the application information management DB 3004 using the transmitted invoice number as a search key to identify the storage location of the deposit/withdrawal information image corresponding to the invoice number, and reads out the deposit/withdrawal information image from the identified storage location. The transmission/reception unit 31 transmits the read-out deposit/withdrawal information image to the examiner terminal 5. In the examiner terminal 5, the display control unit 54 displays the transmitted deposit/withdrawal information image.

When the reception unit 52 accepts the operation of clicking the print button b77, the transmission/reception unit 51 sends an image representing the contents of the displayed deposit/withdrawal list display tab to the printing device, causing the deposit/withdrawal information to be printed out. When the reception unit 52 accepts the operation of clicking the OK button b78, the deposit/withdrawal information screen closes and the provisional screening list screen is displayed.

Referring back to Figure 29, the explanation will be made below. At the examiner terminal 5, the reception unit 52 receives an operation from the examiner instructing the display of the transaction history information screen (S136). Specifically, the reception unit 52 receives an operation to click the display button b63 on the provisional examination list screen. Then, the transmission/reception unit 51 transmits a request for the transaction history information screen, the billing destination ID, and the tenant ID to the intermediary server 3 (S137). At the intermediary server 3, the transmission/reception unit 31 transmits a request for transaction history information, the billing destination ID, and the tenant ID to the document management server 2 (S138).

Next, in the document management server 2, the storage/read processing unit 29 uses the transmitted billing ID as a search key to search the billing information management table corresponding to the tenant ID, thereby reading out the billing information related to the billing ID (S139). Hereinafter, the billing information related to a specific tenant ID and billing ID will also be referred to as "transaction history information." The transmission/reception unit 21 transmits the read-out transaction history information to the intermediary server 3 (S140).

Next, in the intermediary server 3, the creation unit 36 creates screen data for a transaction history information screen such as that shown in FIG. 33 based on the transmitted transaction history information (S141). The transmission/reception unit 31 then transmits the created screen data to the examiner terminal 5 (S142). The display control unit 54 of the examiner terminal 5 displays the transaction history information screen on the display 106 based on the transmitted screen data (S143).

Figure 33 shows an example of the transaction history information screen displayed on the examiner terminal 5. As shown in Figure 33, the transaction history information screen includes a display area a81 for displaying a list of transaction history information, a print button b87, and an OK button b88.

When the reception unit 52 receives a click on the print button b87, the transmission/reception unit 51 sends an image representing the contents of the transaction history list to a printing device, causing the transaction history to be printed out. When the reception unit 52 receives a click on the OK button b88, the transaction history information screen closes and the provisional review list screen is displayed.

Returning to Figure 29, the explanation will be made below. At the examiner terminal 5, the reception unit 52 receives an operation from the examiner instructing the display of the transaction detail information screen (S144). Specifically, the reception unit 52 receives an operation to click the display button b64 on the provisional examination list screen. The transmission/reception unit 51 then transmits a request for the transaction detail information screen, the billing destination ID, and the tenant ID to the intermediary server 3 (S145). As a result, the transmission/reception unit 31 of the intermediary server 3 receives the request for the transaction detail information screen.

Next, in the intermediary server 3, the creation unit 36 creates screen data for the transaction detail information screen as shown in FIG. 34 in response to the request for the transaction detail information screen (S146). The transmission/reception unit 31 then transmits the created screen data to the examiner terminal 5 (S147). The display control unit 54 of the examiner terminal 5 displays the transaction detail information screen on the display 106 based on the transmitted screen data (S148).

Figure 34 shows an example of the transaction detail information screen displayed on the examiner terminal 5. As shown in Figure 34, the transaction detail information screen includes a display area a91 for displaying the transaction status, a confirmation button b96 for confirming the basic contract image, a confirmation button b97 for confirming the financial statement image, and an OK button b98.

Display area a91 displays the transaction status based on the transaction history information received from the document management server 2 in step S140. Examples of transaction status include the transaction start date, number of transactions, average transaction amount, maximum transaction amount, and number of delays. The transaction start date is the oldest sent date in the transaction history information. The number of transactions is the number of transaction history information items. The transaction amount is the total invoice amount in the transaction history information. The number of delays is the number of transaction history information items in which the payment date is later than the payment due date.

When the reception unit 52 receives the operation of clicking the confirmation button b96, the transmission/reception unit 51 sends a request for the basic contract image and the invoice number to the intermediary server 3. In the intermediary server 3, the storage/read processing unit 39 searches the application information management DB 3004 using the transmitted invoice number as a search key to identify the storage location of the basic contract image corresponding to the invoice number, and reads the basic contract image from the identified storage location. The transmission/reception unit 31 sends the read basic contract image to the examiner terminal 5. In the examiner terminal 5, the display control unit 54 displays the transmitted basic contract image.

When the reception unit 52 receives an operation to click the confirmation button b97, the transmission/reception unit 51 transmits a request for the financial statement image and the invoice number to the intermediary server 3. In the intermediary server 3, the storage/readout processing unit 39 searches the application information management DB 3004 using the transmitted invoice number as a search key to identify the storage location of the financial statement image corresponding to the invoice number, and reads out the financial statement image from the identified storage location. The transmission/reception unit 31 transmits the read-out financial statement image to the examiner terminal 5. In the examiner terminal 5, the display control unit 54 displays the transmitted financial statement image.

When the reception unit 52 accepts the operation of clicking the OK button b98, the transaction detail information screen closes and the provisional review list screen is displayed.

Returning to Figure 30, the explanation will be made. At the examiner terminal 5, the reception unit 52 receives an operation from the examiner instructing the display of the provisional examination result registration screen (S149). Specifically, the reception unit 52 receives an operation to click the display button b65 on the provisional examination list screen. Then, the transmission/reception unit 51 transmits a request for the provisional examination result registration screen and the application ID to the intermediary server 3 (S150). As a result, the transmission/reception unit 31 of the intermediary server 3 receives the request for the provisional examination result registration screen and the application ID.

Next, in the intermediary server 3, the storage/readout processing unit 39 searches the application information management DB 3004 using the transmitted application ID as a search key to read out the application information related to the application ID. The creation unit 36 creates screen data for a provisional screening result registration screen such as that shown in FIG. 35 based on the read-out application information (S151). The transmission/reception unit 31 then transmits the created screen data to the examiner terminal 5 (S152). The display control unit 54 of the examiner terminal 5 displays the provisional screening result registration screen on the display 106 based on the transmitted screen data (S153).

Figure 35 is a diagram showing an example of the provisional screening result registration screen displayed on the examiner terminal 5. As shown in Figure 35, the provisional screening result registration screen includes radio buttons with the options "Provisional screening permitted" r101 and "Provisional screening not permitted" r102, a setting area a104 for setting the provisional screening result, a registration button b108, and a cancel button b109. The setting area a104 is not displayed when the provisional screening result registration screen is initially displayed. When "Provisional screening permitted" r101 is selected, the setting area a104 is displayed.

Items of the provisional screening results displayed in the setting area a104 include, for example, the invoice amount, fees, miscellaneous expenses, transfer amount, scheduled transfer date, and repayment due date. Note that miscellaneous expenses are the total amount of stamp duty, transfer fees, and travel expenses. Furthermore, the transfer amount is the invoice amount minus fees and miscellaneous expenses, and is the amount actually transferred from the funding service company to service user company A. The repayment due date is generally set to the payment due date of the invoice information, but may also be set to a specified date after that (for example, the last business day of the following month).

Some items in the provisional screening results are set automatically by the creation unit 36, while others are manually entered by the reviewer. Items that are set automatically and items that are manually entered are displayed so that the reviewer can distinguish between them using the type or color of the border or the color of the input text. In the example display of the provisional screening results registration screen shown in Figure 35, items that are manually entered (fee rate, miscellaneous expenses, and scheduled transfer date) are displayed with a thick border, and items that are automatically set (fee amount, transfer amount, and repayment due date) are displayed with a thin border.

Returning to Figure 30, the explanation will be given below. The reception unit 52 receives an operation to input provisional screening results (S154). Specifically, the reception unit 52 receives an operation to click the registration button b108. Note that when the cancel button b109 is clicked, the provisional screening result registration screen closes and the screen returns to the provisional screening list screen of Figure 31. The transmission/reception unit 51 then transmits the provisional screening result registration request, application ID, and provisional screening result information entered via the provisional screening result registration screen to the intermediary server 3 (S155).

Next, in the intermediary server 3, the storage/read processing unit 39 searches the review management DB 3003 using the transmitted application ID as a search key to identify the review information related to the application ID. The storage/read processing unit 39 also updates the identified review information based on the transmitted provisional review result information (S156). Here, the storage/read processing unit 39 updates the item value of the provisional review status to "OK" and the item value of the final review status to "waiting for response." The storage/read processing unit 39 also updates the item value of the review result information to the transmitted provisional review result information.

Next, on the intermediary server 3, the creation unit 36 creates an audit completion message to notify the user that the provisional audit has been completed (S157). The audit completion message includes a URL link for viewing the provisional audit results.

Finally, the transmission/reception unit 31 of the intermediary server 3 sends a provisional screening completion notice including the screening completion statement to the user terminal 1 (S158). Specifically, the storage/readout processing unit 39 obtains the email address corresponding to service using company A from the application information management DB 3004, and the transmission/reception unit 31 creates an email including the screening completion statement and sends the email to the obtained email address. Note that the method of sending the provisional screening completion notice is not limited to email. For example, a message including the screening completion statement may be sent to the user terminal 1 via a messenger app.

When the reception unit 52 receives an operation to click the display button b67 on the provisional screening list screen, the display control unit 54 displays the screening item setting screen shown in FIG. 36 on the display 106.

Figure 36 is a diagram showing an example of the review item setting screen displayed on the examiner terminal 5. As shown in Figure 36, the review item setting screen includes an input field a111 for setting the type of document that can be used as review document, an input field a112 for setting the period of evidential information, a register button b118, and a cancel button b119. The input field a111 includes a check box c113 for accepting financial statements as review documents, a check box c114 for accepting basic design documents as review documents, and a check box c115 for accepting corporate registration copies as review documents. The input field a112 includes a slider bar s116 for setting the period of evidential document required for review.

When the reception unit 52 receives an operation to click the registration button b118, the transmission/reception unit 51 transmits the input information entered via the examination item setting screen to the intermediary server 3. Note that when the cancel button b119 is clicked, the examination item setting screen closes and the screen returns to the provisional examination list screen of Figure 31. In the intermediary server 3, the storage/readout processing unit 39 updates the examination item information stored in the examination item information management DB 3002 based on the transmitted input information.

<Registration process for this review information>
Next, the registration process of the actual screening information will be explained using Figures 37 to 39. Figure 37 is a sequence diagram showing the registration process of the actual screening information. Figure 38 is a diagram showing a fundraising application list screen. Figure 39 is a diagram showing a provisional screening result list screen.

First, on the user terminal 1, the reception unit 12 receives an operation to display a fundraising application list screen (S161). Specifically, the reception unit 12 receives an operation to click on a URL link included in the provisional screening completion notice sent to the user terminal 1. Then, the transmission/reception unit 11 sends a request for the fundraising application list screen to the intermediary server 3 (S162). As a result, the transmission/reception unit 31 of the intermediary server 3 receives the request for the fundraising application list screen.

Next, in the intermediary server 3, the storage/read processing unit 39 reads out the review information registered in the review management DB 3003 and the application information registered in the application information management DB 3004. The creation unit 36 creates screen data for a fundraising application list screen such as that shown in FIG. 38 based on the read review information and application information (S163). The transmission/reception unit 31 then transmits the created screen data to the user terminal 1 (S164). The display control unit 14 of the user terminal 1 displays the fundraising application list screen on the display 106 based on the transmitted screen data (S165).

Figure 38 is a diagram showing an example of the display of the fundraising application list screen. As shown in Figure 38, the fundraising application list screen includes a display area a121 for displaying a list of fundraising application information. Each piece of fundraising application information displayed in display area a121 includes a display button b122 for displaying a provisional screening results list screen.

Returning to Figure 37, the explanation will be given below. The reception unit 12 receives an operation to display a provisional screening result list screen (S166). Specifically, the reception unit 12 receives an operation to click the display button b122. The display control unit 14 then displays a provisional screening result list screen such as that shown in Figure 39 on the display 106 based on the screening information and application information read in step S163 (S167).

Figure 39 shows an example of the display of the provisional review results list screen. As shown in Figure 39, the provisional review results list screen includes a display area a131 for displaying a list of provisional review results, radio buttons r132 with options corresponding to each provisional review result that was approved in the provisional review (provisional review status is "OK"), and a request button b138 for requesting a full review.

Referring back to Figure 37, the reception unit 12 receives an operation to select a fundraising source (S168). Specifically, the reception unit 12 receives an operation to select one of the fundraising sources r132a or r132b approved in the preliminary screening, which are radio button options. The judgment unit 15 then determines that the fundraising source for which the radio button r132 is selected is a fundraising source for which a full screening will be requested, and that the fundraising source for which the radio button r132 is not selected is a fundraising source for which a full screening will not be requested.

Next, the reception unit 12 receives an operation to request a real review (S169). Specifically, the reception unit 12 receives an operation to click the request button b138. The transmission/reception unit 11 then transmits the request for the real review, the application ID, and the service provider ID to the intermediary server 3 (S170). As a result, the transmission/reception unit 31 of the intermediary server 3 receives the request for the real review, the application ID, and the service provider ID.

Next, in the intermediary server 3, the storage/read processing unit 39 searches the review management DB 3003 using the transmitted application ID as a search key to identify the review information corresponding to each service provider ID. The storage/read processing unit 39 also updates the item value of the main review status of the review information corresponding to the transmitted service provider ID to "Request confirmed." Furthermore, the storage/read processing unit 39 updates the item value of the main review status of the review information corresponding to a service provider ID other than the transmitted one to "Rejection confirmed" (S171).

Next, in the intermediary server 3, the storage/read processing unit 39 searches the review management DB 3003 and the application information management DB 3004 using the transmitted application ID as a search key, thereby reading out the review information and application information related to the application ID. The creation unit 36 creates a statement indicating the result of the review request based on the read review information and application information (S172). Note that the statement indicating the result of the review request includes a statement requesting a review to be sent to funding service companies that are requesting a review, and a statement not requesting a review to be sent to funding service companies that are not requesting a review.

Finally, the transmission/reception unit 31 of the intermediary server 3 sends a confirmation notice of the request for review to the examiner terminal 5, including a message indicating the result of the request for review (S173). Specifically, the storage/readout processing unit 39 of the transmission/reception unit 31 retrieves email addresses corresponding to each service requested for review from the funding source management DB 3001, and sends an email including a message requesting the review to the examiner terminal 5 of the funding service company requesting the review. In addition, an email including a message indicating that the review is not being requested is sent to the examiner terminal 5 of the funding service company not requesting the review. Note that the method of sending the confirmation notice of the request for review is not limited to email. For example, a message including a message indicating the result of the request for review may be sent to the examiner terminal 5 via a messenger app.

[Major Effects of the Present Embodiment]
As described above, according to this embodiment, the intermediary server 3 (intermediary system 4) transmits the document identification information of the document created by the document management server 2 to the examiner terminal 5, thereby eliminating the problem that fundraising users have to go through the trouble of inputting information used for fundraising.

〔supplement〕
In the above embodiment, the preliminary examination (1) is followed by the final examination (2), but all processing related to the preliminary examination (1), such as the request for preliminary examination, may be carried out as the final examination, and the final examination (2) may be omitted.

Furthermore, the user terminal 1 is an example of a communication terminal. User terminals 1 include not only PCs, but also smart watches, game consoles, and devices dedicated to video calls. The presenter terminal is an example of another communication terminal.

Each component, such as each CPU 101, may be single or multiple.

Furthermore, each function in the above-described embodiments can be realized by one or more processing circuits. Here, the "processing circuit" in this embodiment includes a processor programmed to perform each function by software, such as a processor implemented by an electronic circuit, as well as devices such as an ASIC (Application Specific Integrated Circuit), DSP (Digital Signal Processor), FPGA (Field Programmable Gate Array), SOC (System on a Chip), GPU, and conventional circuit modules designed to perform each of the above-described functions.

Furthermore, each of the servers 2 and 3 described in the above embodiments merely represents one of multiple computing environments for implementing the embodiments disclosed herein. For example, the intermediary server 3 may include multiple computing devices, such as a server cluster. The multiple computing devices are configured to communicate with each other via any type of communication link, including a communication network, shared memory, etc., and perform the processing disclosed herein. Similarly, the intermediary server 3 may include multiple computing devices configured to communicate with each other.

Furthermore, the intermediary server 3 can be configured to share the disclosed processing steps in various combinations. For example, the processes performed by the intermediary server 3 can be performed by other servers. Similarly, the functions of the intermediary server 3 can be performed by other servers. Furthermore, the elements of the intermediary server 3 and other servers may be combined into a single server or separated into multiple devices.

Furthermore, in communications between the user terminal 1, the form management server 2, the intermediary server 3, and the examiner terminal 5, other servers, routers, etc. may relay data.

〔summary〕
The present embodiment will be summarized below. Note that the descriptions in parentheses do not limit the scope of the claims, but are merely examples.

(1) In response to a request from the form management server, the intermediary server displays a screen for inputting fundraising application information.
That is, an intermediary server that communicates with one or more form management servers that create forms related to business transactions with business partners in response to requests from users and send the forms to the business partners,
receiving a request for review of fundraising using the form and form identification information for identifying the form, which are transmitted by the form management server based on a request for review of fundraising using the form from the user terminal of the user (see S47, S64);
A request for review of the fundraising is sent to the address of the party reviewing the fundraising, and at least the form identification information of the form is sent (S113).
An intermediary server comprising:

(2) The intermediary server transmits the data of the examination information registration screen.
That is, the intermediary server in (1) above:
Data of a registration screen for registering information to be used in the examination of the fundraising is transmitted to the user terminal (S88).
The input information input via the registration screen transmitted from the user terminal is received (S104).
The input information is registered in association with the form identification information of the form (S111).

(3) The intermediary server in (1) or (2) above refers to the transaction history.
That is, the intermediary server:
Based on the request for review of fundraising using the form sent by the form management server (see S64), first review information indicating the history of commercial transactions between the user and the business partner to which the form was sent is received (S84, S86);
The first examination information is registered in association with the form identification information of the form (S111).

1 User terminal 2 Document management server 3 Intermediation server 4 Intermediation system 31 Transmitting/receiving unit (an example of a transmitting means, an example of a receiving means)
33 Determination unit 34 Judgment unit 36 Creation unit 39 Storage and reading processing unit (an example of a registration means)
100 Communication Network

Claims (11)

An intermediary server that communicates with one or more form management servers that create forms related to business transactions with business partners in response to requests from users and send the forms to the business partners,
a receiving means for receiving a request for review of fundraising using the form and form identification information for identifying the form, the request being transmitted by a form management server based on a request for review of fundraising using the form from the user terminal of the user;
a transmitting means for transmitting a request for review of the fundraising to a destination of the party reviewing the fundraising , and transmitting review request information including document identification information of the document but not including the document ;
An intermediary server comprising: The intermediation server according to claim 1,
the transmitting means transmits to the user terminal data of a registration screen for registering information to be used in the examination of the fundraising;
the receiving means receives input information input via the registration screen, which is transmitted from the user terminal;
The intermediary server comprises a registration means for registering the input information in association with form identification information of the form. The transmission means transmits data of a result registration screen for registering an examination result for the examination request to an examiner terminal of an examiner who examines the examination request;
The receiving means receives the examination results input via the result registration screen transmitted from the examiner terminal,
The intermediary server according to claim 2, wherein the registration means registers the examination result in association with form identification information of the form. The transmission means transmits to the user terminal data of a result display screen for displaying the examination request in which the examination result is registered,
the receiving means receives a second examination request for the examination request selected via the result display screen, the second examination request being sent from the user terminal;
4. The intermediary server according to claim 3, wherein the registration means registers the second examination request in association with form identification information of the form. The receiving means receives, based on a request for review of fundraising using the form sent by the form management server, first review information indicating a history of commercial transactions between the user and the business partner to which the form is sent, and
The intermediary server according to any one of claims 2 to 4, wherein the registration means registers the first examination information in association with form identification information of the form. The receiving means further receives second review information indicating deposit and withdrawal information of an account associated with the user based on a request for review of fundraising using the form sent by the form management server;
The intermediary server according to claim 5, wherein the registration means registers the second examination information in association with form identification information of the form. An intermediary system that creates a document relating to a commercial transaction with a trading partner in response to a request from a user and sends the document to the trading partner,
a receiving means for receiving a request for review of fundraising using the form, the request being sent from the user terminal of the user;
a transmitting means for transmitting the fundraising review request to the address of the party reviewing the fundraising based on the review request , and transmitting review request information including the document identification information of the document but not including the document ;
An intermediation system comprising: A communication system having an intermediary system that creates a document relating to a commercial transaction with a trading partner in response to a request from a user and sends the document to the trading partner, and a user terminal of the user that communicates with the intermediary system via a communication network,
The user terminal transmits a request for review of fundraising using the form,
The intermediation system includes:
receiving the request for review;
A communication system characterized by transmitting a request for review of the fundraising to the address of the party reviewing the fundraising based on the review request , and transmitting review request information that includes document identification information of the document but does not include the document . A communication system having an intermediary server that creates a document relating to a commercial transaction with a trading partner in response to a request from a user and sends the document to the trading partner, and a user terminal of the user that communicates with the intermediary server via a communication network,
The user terminal
a transmission means for transmitting a request for review of fundraising using the form;
The intermediary server
a receiving means for receiving the examination request;
a transmitting means for transmitting the fundraising review request to the address of the party reviewing the fundraising based on the review request , and transmitting review request information including the document identification information of the document but not including the document ;
A communication system comprising: An intermediation method executed by an intermediary server that communicates with a form management server that creates a form related to a commercial transaction with a trading partner in response to a request from a user and sends the form to the trading partner,
a receiving step of receiving a request for review of fundraising using the form and form identification information for identifying the form, which are transmitted by a form management server based on a request for review of fundraising using the form from the user terminal of the user;
a sending step of sending a request for review of the fundraising to an examiner terminal of an examiner who reviews the fundraising , and transmitting review request information that includes document identification information of the document but does not include the document ;
An intermediation method comprising: A program that causes a computer to execute the mediation method described in claim 10.