Management System

Abstract

The objective is to provide an early payment management system and an early payment management method that can manage the payment of remuneration to subcontractors in advance. [Solution] The early payment management server 30 determines the payment amount to the primary contractor based on the primary order information received from the prime contractor, and further determines the remuneration amount for each secondary contractor based on the data received from the primary contractor. Subsequently, the early payment management server 30 receives the amount available for early payment to the secondary contractor from the primary contractor terminal 10, and when an early payment request is made from the secondary contractor terminal 20, it controls the server to transfer an amount corresponding to the requested early payment amount to the secondary contractor's financial institution account based on the amount available for early payment.

Description

Technical Field

[0006] , ,

[0001] This invention relates to an early payment management system for managing early payment of corporate rewards.

Background Art

[0002] Companies and the like often use subcontractors when performing work. In this case, the prime contractor that has received the work from the client will perform the work. Here, the prime contractor can, by contract, have the subcontractor perform the work. The company that first directly undertakes the work from the prime contractor becomes the primary subcontractor (hereinafter referred to as the primary contractor).

[0003] [[ID=·15]] Furthermore, a secondary subcontractor (hereinafter referred to as the secondary contractor) may undertake the work (secondary subcontracting (so-called grandchild subcontracting)), and the work of the secondary contractor may be undertaken by a tertiary subcontractor (hereinafter referred to as the tertiary contractor), and furthermore, the work of the tertiary contractor may be undertaken by a quaternary subcontractor (hereinafter referred to as the quaternary contractor), and so on. Subsequently, companies that perform subcontracting work can be hierarchically set.

[0004] A system for managing the payment of rewards for each company in such a hierarchical subcontracting structure is disclosed in Patent Document 1. The system of Patent Document 1 is a system for performing settlements between companies in the same supply chain, and is configured to create virtual account data for the vertex company and subcontracting companies in the same supply chain, and perform transactions between companies not in cash but by electronic money between virtual accounts.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0006] In the hierarchical subcontracting structure described above, the remuneration for the second-tier subcontractor is often paid at the end of the month following the month in which the work is completed and subsequent inspections such as acceptance are finished. For example, if the prime contractor completes the inspection of the work in April, the prime contractor will pay the first-tier subcontractor at the end of May, and then the first-tier subcontractor will pay the second-tier subcontractor at the end of June.

[0007] Such delays in payment by second-tier subcontractors result in them bearing the burden of labor costs, other expenses, and in some cases, raw material costs related to the work during that period for an extended period, which puts pressure on the company's cash flow. Furthermore, this cash flow problem is also faced by other subcontractors besides second-tier subcontractors, such as first-tier subcontractors and third-tier and below subcontractors.

[0008] However, while the system described in Reference 1 allows for payments to subcontractors and sub-subcontractors using electronic money between virtual accounts, it does not resolve the delays in receiving payment mentioned above.

[0009] Therefore, the object of the present invention is to provide an early payment management system and an early payment management method that can manage the payment of remuneration to subcontractors in advance. [Means for solving the problem]

[0010] The invention according to the first embodiment of the present invention has the following configuration. A management system (for example, early payment management system 1, 101, 201, 301 according to the first to fourth embodiments) that includes a management server (for example, early payment management server 30) for managing the payment of remuneration to a third user (for example, a second-tier subcontractor) when a second user (for example, a primary subcontractor) that has received a job order from a first user (for example, a prime contractor) places an order for the work related to the received job order with a third user (for example, a secondary subcontractor), The aforementioned management server A primary order information receiving means that receives primary order information (for example, transfer data including prime contractor ID, primary contract ID, and remuneration amount) from the first user, including the amount of remuneration for work ordered from the first user to the second user (for example, receiving primary order information in various ways), A secondary order information receiving means that receives secondary order information (for example, receiving secondary order information by various methods) regarding work ordered by the second user to the third user, A first payment request receiving means that receives a first payment request (for example, an early payment request including an early payment request amount entered by the third user) specifying at least a portion of the amount of remuneration for work ordered by the second user from the third user in response to an operation on a computer used by the third user (for example, a secondary subcontractor terminal 20), The system includes a first value provision means that, upon receiving the first payment request, controls the provision of value corresponding to the amount specified in the first payment request to the third user in a predetermined manner (e.g., transfer to a financial institution account, payment by electronic money, etc.) under predetermined conditions (e.g., not exceeding the early payment limit), A management system characterized in that it can provide the third user with value corresponding to the amount specified in the first payment request before the value corresponding to the reward amount included in the primary order information is paid in a predetermined manner (for example, the first user pays the final amount in various ways to a payment agency that operates and manages the management system, etc.) (for example, early payment can be made even after the first user has paid the final amount (see Figure 23)).

[0011] The invention according to the second embodiment of the present invention has the following configuration in the first embodiment. After the value corresponding to the remuneration amount included in the primary order information has been paid, the system is configured to provide the second user with a value corresponding to the amount obtained by subtracting the value provided to the third user by the first payment request from the remuneration amount included in the primary order information (this value is the sum of the remuneration amount of the primary contractor and the amount paid to the secondary contractor, and if the secondary contractor has applied for early payment, the amount of the early payment is subtracted from the original payment amount. For example, the transfer is made based on the transfer data for the primary contractor) (for example, the early payment management systems 1 and 101 according to the first and second embodiments).

[0012] The invention according to the third embodiment of the present invention has the following configuration in the first embodiment. The system includes a third user information providing means that provides third user information (e.g., secondary payment data) to the second user after the value corresponding to the remuneration amount included in the primary order information has been paid, The aforementioned third user information is, Information on the value corresponding to the amount obtained by subtracting the value provided to the third user by the first payment request from the amount of compensation for the work ordered by the second user to the third user, The information includes information relating to the value provided by the corresponding third user (data for making payments to subcontractors, where if the subcontractor has applied for early payment, the amount of the early payment is deducted from the original payment amount) (for example, the early payment management systems 1, 101, and 201 according to the first to third embodiments).

[0013] The invention according to the fourth embodiment of the present invention has the following configuration in the first embodiment. The value provided to the third user, corresponding to the amount specified in the first payment request, is configured to be the value after deducting a predetermined fee (and if there are remaining due dates, the fee may be deducted there as well).

[0014] The invention according to the fifth embodiment of the present invention has the following configuration in the first embodiment. The predetermined conditions for providing value corresponding to the amount specified in the first payment request are configured to include not exceeding a pre-set payable amount (for example, automatically set by a second user or the system).

[0015] The invention according to the sixth embodiment of the present invention has the following configuration in the fifth embodiment. The second user is configured to be able to set the payable amount using a computer used by the second user (for example, the primary contractor's terminal 10).

[0016] The invention according to the seventh embodiment of the present invention has the following configuration in the fifth embodiment. The payable amount is configured to be set as an individual or common upper limit for each of the third users, or as a single overall upper limit for all the third users included in one of the secondary order information.

[0017] The invention according to the eighth embodiment of the present invention has the following configuration in the first embodiment. A second payment request receiving means that receives a second payment request (which may include, for example, an early payment request including an early payment request amount entered by the second user, and a request for payment to the third user) specifying at least a portion of the amount of compensation for work ordered by the first user to the second user, The system includes a second value provision means that, upon receiving the second payment request, controls the provision of value corresponding to the amount specified in the second payment request to the second user in a predetermined manner (e.g., bank transfer to a financial institution account, payment via electronic money, etc.) under predetermined conditions (e.g., not exceeding the total remuneration amount included in the primary order information), Before the value corresponding to the remuneration amount included in the primary order information is paid by a predetermined method (for example, before the first user pays the determined amount to the payment substituting company that operates and manages the management system), the second payment claim is configured to be able to provide the second user with a value corresponding to the amount specified in the bill for payment (for example, the early payment management system 201 according to the third embodiment).

[0018] The invention according to the ninth embodiment of the present invention has the following configuration in the eighth embodiment. After the value corresponding to the remuneration amount included in the primary order information is paid, the value corresponding to the amount obtained by subtracting from the remuneration amount included in the primary order information the value provided to the third user by the first payment claim and the value provided to the second user by the second payment claim is provided to the second user (it is the value obtained by summing the remuneration portion of the primary contractor and the payment amount to the subcontractor, and when the subcontractor has applied for early payment, the early payment amount is subtracted from the original payment amount, and further, when the primary contractor has applied for early payment, the early payment amount is subtracted. For example, the transfer is made based on the transfer data for the primary contractor). It is configured to control as follows (for example, the early payment management system 201 according to the third embodiment).

[0019] The invention according to the tenth embodiment of the present invention has the following configuration in the first embodiment. After the value corresponding to the remuneration amount included in the primary order information is paid, the value corresponding to the amount obtained by subtracting from the remuneration amount included in the primary order information the value provided to the third user by the first payment claim is provided to the corresponding third user (it is the value obtained by summing the remuneration portion of the primary contractor and the payment amount to the subcontractor, and when the subcontractor has applied for early payment, the early payment amount is subtracted from the original payment amount. For example, the transfer is made based on the transfer data for the subcontractor). It is configured to control as follows (for example, the early payment management system 301 according to the fourth embodiment).

Advantages of the Invention

[0020] The early payment management system according to the present invention makes it possible to manage the payment of remuneration to subcontractors in advance. [Brief explanation of the drawing]

[0021] [Figure 1] This is a schematic diagram illustrating the traditional timing of payments to primary and secondary contractors. [Figure 2] This is a schematic diagram showing an overview of the early payment management system according to the first embodiment of the present invention. [Figure 3] This is a schematic diagram showing an example of the hardware configuration of a primary contractor terminal in the early payment management system according to the first embodiment of the present invention. [Figure 4] This is a schematic diagram showing an example of the hardware configuration of the early payment management server of the early payment management system according to the first embodiment of the present invention. [Figure 5] This is a functional block diagram of the primary contractor terminal of the early payment management system according to the first embodiment of the present invention. [Figure 6] This is a functional block diagram of the secondary subcontractor terminal of the early payment management system according to the first embodiment of the present invention. [Figure 7] This is a functional block diagram of the early payment management server of the early payment management system according to the first embodiment of the present invention. [Figure 8] This is a schematic diagram showing an example of a table for an early payment management system according to the first embodiment of the present invention. [Figure 9] This is a schematic diagram showing an example of a table for an early payment management system according to the first embodiment of the present invention. [Figure 10] This diagram illustrates the processing and operation flow in the early payment management system according to the first embodiment of the present invention. [Figure 11] This figure shows the portion relating to amounts in processing and operations in the early payment management system according to the first embodiment of the present invention. [Figure 12] This diagram illustrates the processing and operation flow in the early payment management system according to the second embodiment of the present invention. [Figure 13]This figure shows the portion relating to amounts in processing and operations in the early payment management system according to the second embodiment of the present invention. [Figure 14] This diagram illustrates the processing and operation flow in the early payment management system according to the third embodiment of the present invention. [Figure 15] This figure shows an example of a setting pattern for the amount that can be paid early in the early payment management system of the present invention. [Figure 16] This figure shows an example of a setting pattern for the amount that can be paid early in the early payment management system of the present invention. [Figure 17] This figure shows an example of a setting pattern for the amount that can be paid early in the early payment management system of the present invention. [Figure 18] This figure shows an example of a GUI in the early payment management system of the present invention. [Figure 19] This figure shows an example of a GUI in the early payment management system of the present invention. [Figure 20] This figure shows an example of a GUI in the early payment management system of the present invention. [Figure 21] This figure shows an example of a GUI in the early payment management system of the present invention. [Figure 22] This figure shows an example of a GUI in the early payment management system of the present invention. [Figure 23] This diagram illustrates the processing and operation flow in the early payment management system according to the fourth embodiment of the present invention. [Modes for carrying out the invention]

[0022] First, let's explain the typical timing of payment (e.g., remuneration) in the past, referring to Figure 1. The prime contractor, having received a job from a client, then places an order for that work with a primary contractor, who in turn subcontracts the work to a secondary contractor. In the example shown in Figure 1, these orders are placed during April.

[0023] Here, we assume that the second-tier subcontractor completed the work related to the contracted project by the end of April. The content of such work can vary, and could include, for example, the provision of services such as performing specified tasks, or the provision of goods including the manufacturing and procurement of products.

[0024] The primary contractor, upon receiving completion of the work by the secondary contractor, will verify the details of the work and, if there are no problems, will deliver the product and report the completion of the work to the main contractor.

[0025] Next, the main contractor receives the product, checks its quality, and inspects the results of the work and deliverables. In the example in Figure 1, it is assumed that the above-mentioned checks and inspections were carried out in April. If there are no problems with these checks and inspections, the main contractor will determine the amount to be paid to the primary contractor, for example, around May 20th of the following month. Also, if there are any changes in specifications along the way, these changes will be reflected, and the payment amount may be changed.

[0026] Subsequently, in the example shown in Figure 1, the prime contractor pays the finalized payment to the primary contractor on, for example, May 30th or 31st. This payment is typically made by transferring the funds from the prime contractor to the primary contractor's bank account. Note that May 30th and 31st are assumed to be business days for financial institutions.

[0027] The primary contractor then pays the secondary contractor the payment (remuneration), for example, on June 30th, which is the end of the month following the month in which the work is confirmed and accepted, as shown in Figure 1. This payment is typically made by transferring the funds from the primary contractor to the secondary contractor's bank account. Note that June 30th is assumed to be a business day for financial institutions.

[0028] Under this traditional payment timing, secondary subcontractors only receive payment for their work at the end of the month two months after the work is completed and confirmed / accepted. During this time, they have to bear the costs of personnel expenses and other expenses related to the work, and such payment delays put a significant strain on the cash flow, especially for smaller companies.

[0029] Furthermore, a tertiary subcontractor that receives work from a second-tier subcontractor may receive payment (from the second-tier subcontractor) at the end of the month, for example, three months after the work is completed. Similarly, a quaternary subcontractor that receives work from a third-tier subcontractor may receive payment (from the third-tier subcontractor) at the end of the month, for example, four months after the work is completed. Thus, the financial pressure on subcontractors from the third tier onward can be more severe than that on second-tier subcontractors.

[0030] On the other hand, primary contractors receive payment at the end of the month following the completion of work, but even these primary contractors may prefer to receive payment earlier, depending on the circumstances.

[0031] To improve the timing of these conventional payments and enable subcontractors to achieve a healthier financial situation, the early payment management system of this application is proposed. In this specification, "early payment" refers to payment being made earlier than the conventional timing. For example, in the example in Figure 1, conventionally, a secondary subcontractor receives payment from the primary subcontractor for work completed in April at the end of the month following the completion of the work (for example, June 30th), but with the "early payment" of this application, payment will be made at an earlier time. The early payment management system of this application allows the amount of payment from the prime contractor to the primary subcontractor to be tracked, and "early payments" to secondary subcontractors become possible within the scope of that payment amount. In this case, for the purpose of "early payment" to the secondary subcontractor, the financial institution making the payment to the secondary subcontractor (for example, a payment agency that operates and manages an early payment management system) can recover the early payment at the end of May, for example, when the secondary subcontractor completes the work and finishes the verification and acceptance process in April, because the main contractor will transfer the confirmed payment amount at the end of May, which is the end of the following month. This reduces the risk for the financial institution and eliminates the need to manage credit for the primary and secondary subcontractors.

[0032] [1. First Embodiment] Next, with reference to Figure 2, the configuration of the early payment management system according to the first embodiment of the present application will be described. The early payment management system 1 in Figure 2 is configured to include at least an early payment management server 30. This early payment management server 30 is operated and managed by, for example, a payment agency, and is located at the payment agency's site, and is connected to the primary contractor terminal 10, the secondary contractor terminal 20, and the transaction management server 50 via a network including the Internet. The early payment management server 30 may also be configured as a cloud server or may be configured by multiple computers.

[0033] The primary contractor terminal 10 is a computer used by the primary contractor as described above, and can be, for example, a PC (personal computer) or a mobile device such as a smartphone. Furthermore, the application (including a web application) of the early payment management system 1 executed on the primary contractor terminal 10 can transmit order details to secondary contractors (secondary order information) and the maximum amount of early payment available to secondary contractors (early payment amount) to the early payment management server 30. Note that the transmission of secondary order information and early payment amount to the early payment management server 30 can also be carried out by various methods other than the above application, such as email or documents.

[0034] Furthermore, the primary contractor terminal 10 issues a due date payment instruction to the financial institution as needed, instructing it to pay the payment (remuneration) to the secondary contractor. In this process, the early payment management system 1 of this application can, for example, display the amount of the due date payment. The aforementioned due date payment instruction corresponds, for example, to the "amount transfer (due date payment)" on June 30 in Figure 10, which will be described later, and this transfer amount is the payment to be made to the secondary contractor. However, the amount that has been paid early to the secondary contractor is deducted here.

[0035] The secondary subcontractor terminal 20 is a computer used by the aforementioned secondary subcontractor, such as a PC (personal computer) or a mobile device like a smartphone. The application (including a web application) of the early payment management system 1, which runs on the secondary subcontractor terminal 20, notifies the company of the maximum amount of early payment (early payment available amount). The application also sends an early payment request (payment request for the desired early payment amount) to the early payment management server 30. The notification of the early payment available amount and the early payment request can also be carried out by various methods other than the above application, such as email or documents.

[0036] The prime contractor terminal 40 is a computer used by the prime contractor as described above, and can be, for example, a PC (personal computer) or a mobile device such as a smartphone. The prime contractor terminal 40 also transmits primary order information, including transfer data representing the payment details to the primary contractor, to the early payment management server 30. In this case, the prime contractor terminal 40 can transmit this primary order information to the early payment management server 30 via the network. For example, the primary order information can be transmitted to the early payment management server 30 by sharing it using a designated cloud storage service, sending it by email, or using an application (including a web application) of the early payment management system 1 executed on the prime contractor terminal 40. Alternatively, the primary order information may be input to the early payment management server 30 via offline transmission, such as mailing a storage medium containing the primary order information or a document printed with the primary order information. In addition, primary order information can be input from the prime contractor terminal 40 to the early payment management server 30 in various other ways.

[0037] Furthermore, the prime contractor's terminal 40 sends, for example, fixed-amount payment data to the Zengin System 60 instructing it to pay the primary contractor. In response, the financial institution's transaction management server 50 controls the transfer of the fixed amount from the prime contractor's account to the payment agent's account. The aforementioned payment of the fixed amount corresponds, for example, to the "fixed amount payment" on May 30 in Figure 10, which will be described later. The transfer amount is the order amount (remuneration amount) set at the time of ordering from the prime contractor to the primary contractor, that is, the primary contractor's order amount (or the changed amount if it has been changed since then).

[0038] The early payment management server 30 transmits, for example, early payment transfer data instructing the transfer of early payments to secondary subcontractors and primary subcontractor transfer data instructing the transfer to primary subcontractors to the Zengin System 60, thereby facilitating fund settlements between financial institution accounts. The financial institution's transaction management server 50 controls the transfer of early payments from the payment agent company's account to the secondary subcontractor's account based on the early payment transfer data, and controls the transfer of funds from the payment agent company's account to the primary subcontractor's account based on the primary subcontractor transfer data.

[0039] Furthermore, the early payment management server 30 transmits payment data for secondary subcontractors to the primary subcontractor terminal 10 for the purpose of transferring due payments to secondary subcontractors.

[0040] Payments made via early payment transfer data correspond, for example, to the "Amount Transfer (Early Payment)" timing between May 15th and 29th shown in Figure 10 below. The amount transferred is the amount requested for early payment by the secondary subcontractor through a payment request, or an amount set by other means.

[0041] Payments made using the primary contractor's transfer data correspond to, for example, the "transfer of funds (full remaining amount)" on May 29th in Figure 10, which will be described later. This transfer amount is the sum of the remuneration paid to the primary contractor and the remuneration paid to the secondary contractor. However, any amount paid early to the secondary contractor is deducted.

[0042] The primary contractor makes a due date payment to the secondary contractor based on the transfer data for the secondary contractor received at the primary contractor terminal 10. This payment corresponds, for example, to the "amount transfer (due date payment)" on June 30 in Figure 10, which will be described later. The amount transferred is the original remuneration to the secondary contractor minus any early payment.

[0043] In the example in Figure 2, the payment processing company operating and managing the early payment management server 30 and the financial institution operating and managing the transaction management server 50 are depicted as different entities. However, these may be the same company or organization, and the early payment management server 30 and the transaction management server 50 can be integrated into a single computer, or they can be configured using multiple computers, for example, each with a different function.

[0044] Furthermore, for convenience, the payment agent company account, prime contractor company account, first-tier contractor company account, and second-tier contractor company account are set up as a single financial institution account here, but it is not necessary for each account to be a financial institution account of the same financial institution. Also, regarding payment methods, it is not mandatory to use a financial institution account; various other payment methods such as electronic money and cryptocurrency can be used.

[0045] Next, with reference to Figure 3, an example of the hardware configuration of the primary contractor terminal 10 will be described. The secondary contractor terminal 20 can have a similar configuration. The configuration in Figure 3 is merely an example of a typical terminal configuration such as a PC (personal computer), and various other computers, including mobile devices such as smartphones, can be used as the primary contractor terminal 10 and the secondary contractor terminal 20.

[0046] The primary contractor terminal 10 in Figure 3 includes a CPU (Central Processing Unit) 11, memory 12, display controller 14, display 14a, input device interface 15, keyboard 15a, mouse 15b, external storage device 16, external storage medium interface 17, and a bus 18 that connects these components to each other. Furthermore, if the primary contractor terminal 10 needs to send and receive data with other computers, it is configured to include a network interface 13 for connecting to other computers via a network 70, including the Internet, for example.

[0047] The CPU 11 controls the operation of each component of the primary contractor terminal 10 and executes predetermined processes under the control of the OS. In this embodiment, for example, it executes processes related to screen display such as input of secondary orders by the primary contractor, input of the amount available for early payment, and display of early payment results.

[0048] Memory 12 consists of non-volatile memory, ROM (Read Only Memory), and volatile memory, RAM (Random Access Memory). ROM stores programs that are executed when the primary client terminal 10 starts up. RAM temporarily stores programs executed by the CPU 11, as well as data created and used by those programs during execution.

[0049] The display controller 14 is a dedicated controller for actually processing drawing commands issued by the CPU 11. The drawing data processed by the display controller 14 is, for example, written to graphics memory and then output to the display 14a. The display 14a is a display device composed of, for example, an LCD (Liquid Crystal Display). It can also be a touch panel capable of detecting user touch operations.

[0050] The input device interface 15 receives signals from input devices such as a keyboard 15a and a mouse 15b, and transmits a predetermined command to the CPU 11 according to the signal pattern. If the display 14a is configured as a touch panel, the input device interface 15 detects user touch operations on the display and transmits a touch operation detection signal to the CPU 11.

[0051] The external storage device 16 is, for example, a storage device such as a hard disk drive (HDD), and the program and data according to the present invention are recorded in this device and, at execution time, are read from there into the RAM of memory 12 as needed.

[0052] The external recording medium interface 17 accesses a portable external recording medium 17a, reads the data recorded thereon, and transfers the read data to an external storage device 16 or memory 12. The external recording medium interface 17 includes, for example, a drive device that accesses the recording surface of a CD (Compact Disc), DVD (Digital Versatile Disc), BD (Blu-ray® Disc), etc., and a USB interface that accesses data stored on a USB memory or a device connected via a USB cable.

[0053] The network interface 13 connects to the network 70 and controls the transmission and reception of data via the network 70.

[0054] The external recording medium 17a can store programs for realizing each of the functions according to the present invention. The data recorded on the external recording medium 17a is read via the external recording medium interface 17 and then stored in the external storage device 16. If it is a program, it is loaded into the RAM of the memory 12 at runtime.

[0055] Furthermore, programs for realizing each of the functions according to the present invention may be provided from other computers via the network interface 13 described above and a network including the Internet.

[0056] The primary contractor terminal 10 may also be equipped with an audio output device, which is, for example, a speaker, and receives audio data from an application running under the OS and outputs audio.

[0057] Figure 3 shows the configuration of a terminal such as a PC (personal computer), but as mentioned above, the primary contractor terminal 10 can also be configured with a portable device such as a smartphone. In this case, the storage device includes, for example, semiconductor memory called flash memory or a hard disk, and programs and various data for realizing each function executed by the CPU are stored in this storage device.

[0058] Furthermore, the programs executed by the CPU to realize each function of the present invention are obtained from an external storage medium or via a network such as a mobile phone network or the internet. For example, a primary contractor terminal 10, which is a smartphone, accesses a predetermined site to download a specific program (a so-called app), and it is executed by the CPU.

[0059] The configuration of the secondary subcontractor terminal 20 and the prime contractor terminal 40 is the same as the configuration of the primary subcontractor terminal 10 described above.

[0060] Next, with reference to Figure 4, an example of the hardware configuration of the early payment management server 30 will be described. However, the early payment management server 30 in Figure 4 is merely an example of a typical configuration for a general server computer. Various other computers can be used as the early payment management server 30.

[0061] The early payment management server 30 includes a CPU 31, memory 32, network interface 33, display controller 34, display 34a, input device interface 35, keyboard 35a, mouse 35b, external storage device 36, and external recording medium interface 37, and a bus 38 that connects these components to each other.

[0062] The CPU 31 controls the operation of each component of the early payment management server 30 and executes each function under the control of the OS.

[0063] Memory 32 typically consists of non-volatile memory, ROM (Read Only Memory), and volatile memory, RAM (Random Access Memory). ROM stores programs executed when the early payment management server 30 starts up. RAM temporarily stores programs executed by the CPU 31 and data used by those programs during execution.

[0064] The network interface 33 is, for example, an interface for connecting to a network 80, including the Internet.

[0065] The display controller 34 is a dedicated controller for actually processing drawing commands issued by the CPU 31. The drawing data processed by the display controller 34 is first written to graphics memory and then output to the display 34a. The display 34a is a display device composed of, for example, an LCD (Liquid Crystal Display). It can also be a touch panel capable of detecting user touch operations.

[0066] The input device interface 35 receives signals from the keyboard 35a and mouse 35b and transmits a predetermined command to the CPU 31 according to the signal pattern.

[0067] The external storage device 36 is, for example, a storage device such as a hard disk drive (HDD), and the aforementioned programs and data are recorded in this device and, at execution time, are read from there into the RAM of memory 32 as needed.

[0068] The external recording medium interface 37 accesses a portable external recording medium 37a, reads the data recorded therein, and transfers the read data to an external storage device 36 or memory 32. The external recording medium interface 37 includes, for example, a drive device that accesses the recording surface of a CD (Compact Disc), DVD (Digital Versatile Disc), BD (Blu-ray® Disc), etc., and a USB interface that accesses data stored on a USB memory or device connected via a USB cable.

[0069] Furthermore, in the case of the early payment management server 30, if operation by a person in charge or administrator is not required, or if it is operated via remote connection, the display controller 34, display 34a, input device interface 35, keyboard 35a, and mouse 35b described above are not necessary.

[0070] Next, with reference to the functional block diagram in Figure 5, an overview of the functions of the primary contractor terminal 10 according to the first embodiment of the present invention will be described. As shown in Figure 5, the primary contractor terminal 10 includes an access control unit 151, an early payment control unit 152, an early payment performance display control unit 153, an input / output control unit 154, and a network I / F unit 155.

[0071] The access control unit 151 accesses the early payment management server 30 to control the login of users operating the primary contractor terminal 10. Login is permitted only if the user is legitimate, and subsequent processing is then possible.

[0072] The early payment control unit 152 exchanges data with the early payment management server 30 in response to user operations, and controls the system to enable the input of secondary order information and the amount available for early payment. It can also receive secondary payment data from the early payment management server 30 at predetermined timings. Furthermore, the early payment management system 201 according to the third embodiment, described later, controls the system to enable the input of early payment applications by the primary contractor.

[0073] The early payment performance display control unit 153 exchanges data with the early payment management server 30 in response to user operations and controls the display of screens such as the early payment performance display screen 450 shown in Figure 22, which will be described later.

[0074] The input / output control unit 154 transmits signals related to user operations obtained via the display 14a and input device interface 15 of the primary contractor terminal 10 shown in Figure 3 to the CPU 11, and controls the display controller 14 to display screens such as secondary order information input and early payment amount input, as well as the early payment performance display screen, on the display 14a based on commands from the CPU 11.

[0075] The network interface unit 155 controls the network interface 13 of the primary contractor terminal 10 shown in Figure 3 to enable data transmission and reception with the early payment management server 30.

[0076] The access control unit 151, the early payment control unit 152, and the early payment performance display control unit 153 can be implemented using a dedicated application installed on the primary contractor terminal 10 (for example, an application downloadable from a designated site), but they can also be implemented by loading HTML etc. from a web server using a general web browser. Furthermore, the functions of the web server can also be implemented by the early payment management server 30.

[0077] The basic configuration of the primary contractor terminal 10 shown in Figure 5 is generally similar in other embodiments of the early payment management system.

[0078] Next, with reference to the functional block diagram in Figure 6, an overview of the functions of the secondary subcontracting company terminal 20 according to the first embodiment of the present invention will be described. As shown in Figure 6, the secondary subcontracting company terminal 20 includes an access control unit 251, an early payment control unit 252, an input / output control unit 254, and a network I / F unit 255.

[0079] The access control unit 251, input / output control unit 254, and network I / F unit 255 have the same functions as the access control unit 151, input / output control unit 154, and network I / F unit 155 of the primary contractor terminal 10 shown in Figure 5, respectively, so their explanation is omitted here.

[0080] The early payment control unit 252 exchanges data with the early payment management server 30 in response to user operations, and controls the system to receive notifications of available early payment amounts and to enable early payment applications (input of desired early payment amount). In addition, the early payment management system 101 according to the second embodiment, which will be described later, also controls the system to receive notifications of available early payment amounts for extra-early payments and to enable extra-early payment applications (input of desired extra-early payment amount).

[0081] The access control unit 251 and the early payment control unit 252 can be implemented using a dedicated application installed on the secondary subcontractor terminal 20 (for example, an application downloadable from a designated site), but they can also be implemented by loading HTML etc. from a web server using a general web browser. Furthermore, the functions of the web server can also be implemented by the early payment management server 30.

[0082] The basic configuration of the secondary subcontractor terminal 20 shown in Figure 6 is generally similar in other embodiments of the early payment management system.

[0083] Next, with reference to the functional block diagram in Figure 7, an overview of the functions of the early payment management server 30 according to the first embodiment of the present invention will be described. As shown in Figure 7, the early payment management server 30 includes an access control unit 351, an early payment management unit 352, a prime contractor information receiving unit 353, a transfer control unit 354, and a network I / F unit 355. In addition, the external storage device 36 stores a company information management table 361, an order information table 362, and a secondary order management table 363.

[0084] The access control unit 351 performs user authentication, for example using a password, for access from the primary contractor terminal 10 and the secondary contractor terminal 20, and returns the result to each terminal. Login to that terminal is permitted only if it is determined that the user is legitimate.

[0085] The Early Payment Management Unit 352 receives information when the primary contractor enters secondary order information or the amount available for early payment using the primary contractor terminal 10, and stores this information in a predetermined table. Furthermore, when a secondary contractor enters an early payment request (desired early payment amount), the unit decides to transfer the entered early payment amount to the secondary contractor under predetermined conditions.

[0086] Furthermore, in the early payment management system 101 according to the second embodiment described later, when a secondary subcontractor enters an early payment request (desired early payment amount), it is decided to transfer the entered early payment amount to the secondary subcontractor under predetermined conditions. Furthermore, in the early payment management system 201 according to the third embodiment described later, when a primary subcontractor enters an early payment request (desired early payment amount), it is decided to transfer the entered early payment amount to the primary subcontractor under predetermined conditions.

[0087] Furthermore, when the primary contractor instructs the primary contractor terminal 10 to display performance information, etc., the early payment management unit 352 accesses a predetermined table and transmits data for display to the primary contractor terminal 10.

[0088] The prime contractor information receiving unit 353 receives primary order information, including payment data, from the prime contractor using a predetermined method. The primary order information is, for example, data related to the order, and includes, for example, a prime contractor ID that identifies the prime contractor, a primary contractor ID that identifies the primary contractor, and the order amount (remuneration amount).

[0089] The transfer control unit 354 generates early payment transfer data when transferring the early payment request amount entered by the secondary subcontractor to the secondary subcontractor's financial institution account, and this early payment transfer data enables the transfer to the secondary subcontractor's financial institution account.

[0090] Furthermore, when the transfer control unit 354 transfers the amount of compensation other than the amount paid early at a predetermined time to the primary contractor's financial institution account, it generates primary contractor transfer data, and the transfer to the primary contractor's financial institution account is realized using this primary contractor transfer data. Subsequently, it transmits (or displays on the display) secondary contractor transfer data that can be used when the primary contractor makes a transfer to the secondary contractor's financial institution account.

[0091] Furthermore, in the early payment management system 101 according to the second embodiment described later, when the secondary subcontractor inputs an early payment request (desired early payment amount) and it is decided to transfer the requested early payment amount to the secondary subcontractor, the transfer control unit 354 generates early payment transfer data, and this early payment transfer data is used to transfer the funds to the secondary subcontractor's financial institution account. Furthermore, in the early payment management system 201 according to the third embodiment described later, when the primary subcontractor inputs an early payment request (desired early payment amount) and it is decided to transfer the requested early payment amount to the primary subcontractor, primary subcontractor early payment transfer data is generated, and this primary subcontractor early payment transfer data is used to transfer the funds to the primary subcontractor's financial institution account.

[0092] The network interface unit 355 controls the network interface 33 of the early payment management server 30 shown in Figure 4, connects to a network such as the Internet, and enables data transmission and reception between the primary contractor terminal 10 and the secondary contractor terminal 20.

[0093] The company information management table 361, illustrated in Figure 8(A), stores information about prime contractors, primary contractors, and secondary contractors, and includes the following fields: company ID, type, company name, financial institution account, and password. The company ID is an ID used to identify prime contractors, primary contractors, and secondary contractors, and the type field indicates whether the company is a prime contractor, primary contractor, or secondary contractor. Of course, depending on the order details, the same company may be a primary contractor or a secondary contractor.

[0094] The company name indicates the name of the company, and the financial institution account indicates the transaction account at the financial institution used by the company. The password is the password for logging into the early payment management system of this application. The company information stored in the company information management table 361 is, for example, the information that the company registered by written document, data, online, etc., when it started using the early payment management system.

[0095] The example of the order information table 362 shown in Figure 8(B) stores information about an order and includes the following items: order ID, order date, prime contractor ID, primary contractor ID, work completion flag, confirmation completion flag, confirmation date, order amount (remuneration amount), early payment application period, and specification method. The order ID is, for example, an ID assigned when a primary contractor enters the details of an order (secondary order information). The order date is the date of the order, the prime contractor ID is the ordering party of the order and corresponds to the ID (type = "prime contractor") stored as the company ID in the company information management table 361. The primary contractor ID is the recipient of the order and corresponds to the ID (type = "primary") stored as the company ID in the company information management table 361. The work completion flag is a flag indicating whether the work related to the order has been completed, and the confirmation completion flag is a flag indicating whether the work related to the order has been confirmed and accepted by the prime contractor.

[0096] The confirmation date is, for example, the date on which the prime contractor, having completed confirmation and acceptance of the work related to the order, sends the primary order information, including the data for transferring the order amount (transfer data), to the early payment management system. The order amount is the remuneration for the order and the amount that the primary contractor receives. The early payment application period indicates the period during which the secondary contractor can apply for early payment. The designation method indicates how the primary contractor will specify the amount of early payment (early payment possible amount) that the secondary contractor can request.

[0097] In this example, the period during which early payment can be requested is defined by a fixed date. However, it is also possible to set the start date of the early payment request period dynamically, for example, by setting it after the date on which the initial order information is received from the prime contractor, and the end date of the early payment request period by setting it on the date on which the final payment is made by the prime contractor.

[0098] The secondary order management table 363, illustrated in Figure 9, stores information about secondary subcontractors in an order, including order ID, secondary subcontract ID, early payment number, order amount, early payment available amount, desired early payment amount, and early payment date.

[0099] The order ID is an ID assigned when, for example, a primary contractor enters the details of an order (secondary order information), and this order ID corresponds to the order ID stored in the order information table 362 in Figure 8(B).

[0100] The secondary subcontracting ID is an ID used to identify the secondary subcontracting company to which the primary subcontracting company that placed the order corresponding to the order ID places a further order (secondary order). It corresponds to the ID (type = "secondary") stored as the company ID in the company information management table 361. The early payment number indicates the number of times the secondary subcontracting company has made an early payment.

[0101] The order amount is the amount (remuneration amount) that the primary contractor ordered from the secondary contractor, and the early payment amount is the maximum amount that the primary contractor has set for each secondary contractor that can be paid early. The requested early payment amount is the amount that the secondary contractor wishes to pay early, within the range of the early payment amount, and the early payment date is the date on which the secondary contractor specified the requested early payment amount and the payment was subsequently transferred to the secondary contractor's bank account. In this example, the early payment amount is set individually for each secondary contractor.

[0102] In this example, a subcontractor C2 with order ID "0001" can apply for early payment multiple times for a single order. For example, subcontractor C2 received an early payment of 1 million yen as its first application with early payment No. "1", and then another early payment of 600,000 yen as its second application with early payment No. "2". It is also possible to restrict this to only one early payment application during the application period, rather than allowing multiple early payments.

[0103] Next, with reference to Figure 10, the processing and operation flow in the early payment management system 1 according to the first embodiment of this application will be described.

[0104] Figure 10 shows the processing, actions, and operations performed by the prime contractor, first-tier subcontractor, second-tier subcontractor, and the Early Payment Management System 1, using the processing from April to June as an example. Rectangles indicate processing by the Early Payment Management System 1, while ellipses indicate operations and actions, including input operations to the Early Payment Management System 1.

[0105] In April, the prime contractor places orders for work with first-tier subcontractors, who then place orders for that work with second-tier subcontractors (second-tier ordering). In this scenario, there is one prime contractor, but there can be multiple first-tier subcontractors. Similarly, there can be multiple second-tier subcontractors for a single first-tier subcontractor.

[0106] In this example, the initial order and subsequent sub-orders are placed in April, but they could be placed earlier. Furthermore, it is assumed that the work of the secondary subcontractor is completed in April, after which the primary subcontractor checks the work as needed. The prime contractor then checks and accepts the work (e.g., goods or services), and that it is determined to be satisfactory in April.

[0107] Next, the prime contractor sends primary order information, including data on the finalized remuneration amount (order amount), to the Early Payment Management System 1 for work that was confirmed and accepted during April. The timing for sending the primary order information is, for example, between May 15th and 20th or between May 1st and 20th. This primary order information can be sent to the Early Payment Management System 1 in various ways, such as by sharing it using a designated cloud storage service, sending it by email, or using the Early Payment Management System 1 application (including a web application) executed on the prime contractor's terminal 40, as described above.

[0108] The primary order information mentioned above includes, for example, a prime contractor ID to identify the prime contractor, a primary contractor ID to identify the primary contractor, and payment data such as the confirmed remuneration amount (order amount). It should be noted that in the Early Payment Management System 1, the prime contractor ID, primary contractor ID, and secondary contractor ID to identify the prime contractor, primary contractor, and secondary contractor, respectively, are assumed to be registered prior to the required timing. Furthermore, it is assumed that information necessary for transactions and settlements, such as the financial institution accounts of the prime contractor, primary contractor, and secondary contractor, are also registered in advance.

[0109] When the early payment management system 1 receives primary order information, it assigns an order ID and notifies the primary contractor and the prime contractor of the order ID. The order ID may be notified by email or other means, or, in the case of the primary contractor, by an application of the early payment management system 1 (including a web application) running on the primary contractor's terminal 10.

[0110] Next, the primary contractor logs in to the application of the Early Payment Management System 1, which runs on the primary contractor terminal 10, and enters the details of the secondary order (secondary order information). In this example, the order ID, secondary contract ID, and the amount of the secondary order for each secondary contractor are entered from the input screen. Furthermore, the application of the Early Payment Management System 1, which runs on the primary contractor terminal 10, enters the amount available for early payment. Here, the amount available for early payment is the amount that the primary contractor has ordered from the secondary contractor that can be paid earlier than the conventional timing (for example, the timing of June 30th in Figure 1), and various setting methods are possible, such as setting it for each secondary contractor or setting it for each order (order ID). Note that the amount available for early payment can also be automatically set by the Early Payment Management System 1 based on the amount of the secondary order, etc., in which case the primary contractor does not need to enter the amount available for early payment.

[0111] The Early Payment Management System 1 notifies each of the secondary subcontractors of the amount that has been set as available for early payment. For example, when a secondary subcontractor logs in to the Early Payment Management System 1 application running on the secondary subcontractor terminal 20, they can check the amount that has been set as available for early payment by the primary subcontractor on a designated system screen. The Early Payment Management System 1 can also notify secondary subcontractors of the amount that has been set as available for early payment via email or other means.

[0112] The secondary subcontractor then uses the application of the early payment management system 1, which runs on the secondary subcontractor terminal 20, to input the desired early payment amount and submit an early payment request (payment request). The desired early payment amount must be specified within the range of the early payment allowance mentioned above. For example, if the early payment allowance is set for each order (order ID), the entire early payment allowance will be granted to the secondary subcontractors in the order in which they submitted their requests (first-come, first-served basis).

[0113] When the Early Payment Management System 1 receives an Early Payment Request from the Secondary Subcontractor Terminal 20, if it meets certain conditions, such as the requested Early Payment amount being within the range of the available Early Payment amount, it transmits Early Payment Transfer Data to, for example, the Zengin System 60. As a result, the Early Payment Management System 1 transfers the requested Early Payment amount specified by the secondary subcontractor from the payment agent company account managed by the Early Payment Management System 1 (see Figure 2) to the secondary subcontractor (Amount Transfer (Early Payment)). Here, the Early Payment Transfer Data includes, for example, the secondary subcontractor ID and the amount.

[0114] Such early payments may, for example, be transferred to the secondary contractor's bank account on the same day or the next business day after the early payment request is made. Furthermore, as shown in Figure 10, such early payment requests and corresponding transfers (early payments) are possible from the date the primary order information is sent until May 29th, but this can be set in any way depending on the timing of the primary order information's transmission. For example, the application period may be from May 15th to 29th, or if the primary order information is sent between May 1st and around May 20th, it may be from May 1st to 29th.

[0115] In this way, secondary subcontractors can receive payment for their work earlier than the usual payment date, such as June 30th, allowing them to continue operating with a more stable financial position.

[0116] Subsequently, for example, on May 30, when the prime contractor transfers the finalized amount (i.e., the remuneration amount included in the primary order information) to the payment agent company account managed by the Early Payment Management System 1 (see Figure 2), the Early Payment Management System 1 checks whether the transferred amount matches the order amount (remuneration amount) in the primary order information received from the prime contractor between May 15 and 20. If there are no problems, it sends primary contractor transfer data instructing the transfer to the primary contractor to, for example, the Zengin System 60.

[0117] The primary contract transfer data includes, for example, the primary contract ID and the amount. As a result, a transfer is made from the payment agent's account to the primary contracting company's account. The transfer amount in a payment using the primary contract transfer data is the sum of the payment to the primary contracting company and the payment to the secondary contracting company. However, any amount paid early to the secondary contracting company is deducted.

[0118] Furthermore, at this time, the Early Payment Management System 1 can send secondary payment data to the primary contractor. This secondary payment data includes, for example, the secondary payment ID and the amount. This amount is the remuneration to be paid to the secondary contractor, but the amount that has been paid early has been deducted. The secondary payment data can also be viewed or downloaded from the system screen displayed after logging in to the application of the Early Payment Management System 1, which is run on the primary contractor's terminal 110. The Early Payment Management System 1 can also notify the primary contractor of the secondary payment data via email or other means.

[0119] On June 30th, the primary contractor, for example, uses its terminal 10 to instruct the secondary contractor to transfer funds (on a due date) to the secondary contractor's bank account, if necessary. For this process, the primary contractor can utilize the secondary contractor's transfer data. The aforementioned due date transfer amount is the payment from the primary contractor to the secondary contractor. However, any amounts already paid to the secondary contractor in advance are deducted.

[0120] The above explanation, with reference to Figure 10, describes the processing flow in the early payment management system 1 according to the first embodiment of the present application. However, the dates used are merely specific months and days for the sake of explanation. Furthermore, if the primary order information is transmitted between May 1st and 20th, the period during which secondary contractors can apply for early payment, as shown in Figure 10, can start as early as May 1st, depending on the timing of the primary contractor's input of secondary order information and early payment amount. Of course, if the primary order information is transmitted earlier than May 1st, the start time of the period during which secondary contractors can apply for early payment can be set accordingly to before May 1st.

[0121] Furthermore, taxes such as consumption tax have been omitted for the sake of simplicity. In addition, fees related to the Early Payment Management System 1 and fees related to early payments have been omitted here and will be explained later.

[0122] Figure 11 illustrates the parts related to amounts, etc., in the processing of the Early Payment Management System 1 shown in Figure 10, when the work of the primary contractor to the secondary contractor is carried out continuously every month.

[0123] Let's say a secondary subcontractor completed work for a fee of 500,000 yen in April, and the prime contractor sent the primary order information to the Early Payment Management System 1 on May 15th. Then, for example, on May 15th, the primary subcontractor uses the primary subcontractor terminal 10 to input secondary order information, including the order amount for each secondary subcontractor. After that, when the secondary subcontractor uses the secondary subcontractor terminal 20 to input the desired early payment amount and submits an early payment request, the Early Payment Management System 1 transfers the predetermined amount as an early payment to the secondary subcontractor's financial institution account.

[0124] The maximum amount at this time is 500,000 yen, which is the remuneration for April, but it can be set to a lower amount depending on the primary contractor's settings and the early payment management system 1. As a result, from May 15th to 29th, secondary contractors can receive at least a portion of their remuneration through early payment.

[0125] Subsequently, on June 30th, if there are still outstanding payments for April, the primary contractor will transfer the funds to the secondary contractor (payment on due date). This amount is the original order amount minus any early payments already made. The early payment management system 1 displays, for example, the remaining balance of the secondary contractor to be transferred on the primary contractor's terminal 10.

[0126] Let's say a secondary subcontractor completed work for a fee of 750,000 yen in May, and the prime contractor sent the primary order information to the Early Payment Management System 1 on June 15th. Then, for example, on June 15th, the primary subcontractor uses the primary subcontractor terminal 10 to input secondary order information, including the order amount for each secondary subcontractor. After that, when the secondary subcontractor uses the secondary subcontractor terminal 20 to input the desired early payment amount and submits an early payment request, the Early Payment Management System 1 transfers the predetermined amount as an early payment to the secondary subcontractor's financial institution account.

[0127] The maximum amount at this time is 750,000 yen, which is the compensation for May, but it can also be set at a lower amount depending on the amount that the primary contractor allows for early payment. As a result, from June 15th to 28th, the secondary contractor can receive at least a portion of the compensation through early payment.

[0128] Subsequently, on July 31st, if there are still outstanding payments for May, the primary contractor will transfer the funds to the secondary contractor (payment on due date). This amount is the original order amount minus any early payments already made. The early payment management system 1 displays, for example, the remaining balance of the secondary contractor to be transferred on the primary contractor's terminal 10.

[0129] Similarly, suppose a secondary subcontractor completes work for a fee of 150,000 yen in June, and the prime contractor sends the primary order information to the Early Payment Management System 1 on July 15th. Then, for example, on July 15th, the primary subcontractor uses the primary subcontractor terminal 10 to input secondary order information, including the order amount for each secondary subcontractor. Subsequently, when the secondary subcontractor uses the secondary subcontractor terminal 20 to input the desired early payment amount and submits an early payment request, the Early Payment Management System 1 transfers the predetermined amount as an early payment to the secondary subcontractor's financial institution account.

[0130] The maximum amount at this time is 150,000 yen, which is the payment for June, but it can also be set at a lower amount depending on the amount that the primary contractor allows for early payment. As a result, from July 15th to 29th, the secondary contractor can receive at least a portion of the payment through early payment.

[0131] Although not shown in Figure 11, on August 31st, if there are still outstanding payments for June, the primary contractor will transfer the funds to the secondary contractor (payment on due date). This amount is the original order amount minus any early payments already made. The early payment management system 1 displays, for example, the remaining balance of the secondary contractor to be transferred on the primary contractor's terminal 10.

[0132] Similarly, subcontractors can receive payment for their work earlier than before. Also, as with Figure 10, the dates used are merely specific months and days for the sake of explanation. Furthermore, taxes such as consumption tax have been omitted for the sake of simplicity. In addition, fees related to the Early Payment Management System 1 and fees related to early payments are omitted here and will be explained later.

[0133] [2. Second Embodiment] The early payment management system 101 according to the second embodiment of this application, in addition to the functions and processes of the early payment management system 1 according to the first embodiment, enables payment to subcontractors at an earlier time than the early payment. Here, for convenience, payment at an earlier time than the early payment in the first embodiment will be referred to as "ultra-early payment" or "ultra-early payment."

[0134] The early payment management system 101 according to the second embodiment of the present application is similar to the early payment management system 1 according to the first embodiment in that it includes at least an early payment management server 130 (a server operated and managed by a payment agency, etc., and located on the site of the payment agency), and the early payment management server 130 is connected to the primary contractor terminal 110, the secondary contractor terminal 120, and the transaction management server 150 via a network including the Internet.

[0135] The early payment management server 130, the primary contractor terminal 110, the secondary contractor terminal 120, and the transaction management server 150 generally correspond to the early payment management server 30, primary contractor terminal 10, secondary contractor terminal 20, and transaction management server 50 of the first embodiment, respectively. The exchange of data between the early payment management server 130 and the primary contractor terminal 110, secondary contractor terminal 120, and transaction management server 150, as well as the settlement of funds between financial institution accounts, will be explained below.

[0136] Next, with reference to Figure 12, the processing flow in the early payment management system 101 according to the second embodiment of the present application will be explained.

[0137] Figure 12 shows the processing, actions, and operations performed by the prime contractor, first-tier subcontractor, second-tier subcontractor, and the early payment management system 101, using the processing from April to June as an example. Rectangles indicate processing performed by the early payment management system 101, while ellipses indicate operations and actions, including input operations to the early payment management system 101.

[0138] In April, the prime contractor places orders for work with first-tier subcontractors, who then place orders for that work with second-tier subcontractors (second-tier ordering). In this scenario, there is one prime contractor, but there can be multiple first-tier subcontractors. Similarly, there can be multiple second-tier subcontractors for a single first-tier subcontractor.

[0139] In this example, the initial order and secondary orders were placed in April, but they could have been placed earlier. Furthermore, it is assumed that the secondary contractor's work is completed in April, and the primary contractor then verifies the work as needed.

[0140] Subsequently, the primary contractor logs in to the application of the early payment management system 101, which is run on the primary contractor terminal 110, and enters the secondary order information. In this example, the prime contractor ID, secondary contractor ID, and remuneration amount (order amount for each secondary contractor) are entered.

[0141] Next, when the early payment management system 101 receives secondary order information, it assigns an order ID and notifies the primary contractor and the prime contractor of the order ID. The order ID may be notified by email or other means, or, in the case of the primary contractor, by an application (including a web application) of the early payment management system 101 running on the primary contractor's terminal 110.

[0142] Subsequently, the primary contractor enters the amount available for early payment using the application of the early payment management system 101, which is executed on the primary contractor's terminal 110. Here, the amount available for early payment is the amount that the primary contractor has ordered from the secondary contractor and can pay earlier than the conventional timing (for example, the timing of June 30th in Figure 1). Various setting methods are possible, such as settings for each secondary contractor or settings for each order (order ID). Note that the amount available for early payment entered here is the amount to be paid based on the secondary order amount at a stage before the prime contractor has completed confirmation and acceptance. Note that the amount available for early payment can also be automatically set by the early payment management system 101 based on the secondary order amount, etc., in which case the amount available for early payment by the primary contractor is not required.

[0143] Subsequently, the main contractor will confirm and inspect the contents of the work (e.g., goods or services), and if it is determined that there are no problems by the end of April, this will be considered acceptable.

[0144] Between May 1st and 14th, the Early Payment Management System 101 will notify each of the secondary subcontractors of the early payment amount set above. For example, a secondary subcontractor can log in to the Early Payment Management System 101 application running on their secondary subcontractor terminal 120 and check the early payment amount set by the primary subcontractor on a designated system screen. The Early Payment Management System 101 can also notify secondary subcontractors of the early payment amount via email or other means.

[0145] The secondary subcontractor then uses the application of the early payment management system 101, which is executed on the secondary subcontractor terminal 120, to input the desired amount for early payment and submit an early payment request (payment request). The desired amount for early payment must be specified within the range of the early payment allowance mentioned above. For example, if the early payment allowance is set for each order (order ID), the entire early payment allowance will be approved in the order of the secondary subcontractor's application (early payment request) (first-come, first-served basis).

[0146] When the Early Payment Management System 101 receives an early payment request from a secondary subcontractor terminal 120, and if it meets certain conditions, such as the requested early payment amount being within the range of the available early payment amount, it transmits the early payment transfer data to, for example, the nationwide interbank payment system 160. As a result, the Early Payment Management System 101 transfers the requested early payment amount specified by the secondary subcontractor from the payment agent company account managed by the Early Payment Management System 101 (see Figure 2) to the secondary subcontractor (amount transfer (early payment)). Here, the early payment transfer data includes, for example, the secondary subcontractor ID and the amount.

[0147] The requested amount for such an early payment request will be transferred to the secondary contractor's bank account on the same day or the next business day. Furthermore, as shown in Figure 12, such early payment requests and corresponding transfers (early payments) are possible, for example, from May 1st to 14th. It is also possible to allow early payment requests to be approved before May 1st, before the prime contractor conducts work verification and acceptance testing.

[0148] In this way, secondary subcontractors can receive at least a portion of the payment for their work earlier than the usual payment date, such as June 30th, and even earlier than the early payment timing in the early payment management system 1 of the first embodiment, enabling them to continue operating with a more stable financial position.

[0149] The prime contractor sends primary order information, including transfer data for the confirmed remuneration amount (order amount), to the early payment management system 101 for work that was confirmed and accepted in April. The timing for sending primary order information is, for example, between May 15th and 20th.

[0150] The primary order information described above includes, for example, the order ID and the confirmed remuneration amount (order amount). It may also include a prime contractor ID to identify the prime contractor and a primary contractor ID to identify the primary contractor. Here, it is assumed that the early payment management system 1 has registered the prime contractor ID, primary contractor ID, and secondary contractor ID to identify the prime contractor, primary contractor, and secondary contractor, respectively, before the time when they are needed. It is also assumed that information necessary for transactions and settlements, such as the financial institution accounts of the prime contractor, primary contractor, and secondary contractor, has been registered in advance. Furthermore, when the early payment management system 101 receives primary order information, it notifies the primary contractor accordingly.

[0151] Next, the primary contractor logs in to the application of the early payment management system 101, which is run on the primary contractor's terminal 110, and enters the secondary order information. Although the secondary order information has already been entered, it is entered here as needed, for example, when there are changes to the secondary order amount of the secondary contractor due to the finalization of the amount by the prime contractor. The secondary order information includes, for example, the order ID, secondary contract ID, and the remuneration amount for each secondary contractor.

[0152] Furthermore, if necessary, the amount available for early payment is entered via the application of the early payment management system 101, which is executed on the primary contractor's terminal 110. Here, the amount available for early payment is the amount that the primary contractor has ordered from the secondary contractor that can be paid by May 29th (earlier than the conventional timing), and various setting methods are possible, such as settings for each secondary contractor or settings for each order (order ID). However, the amount that has already been paid through the ultra-early payment system is deducted here.

[0153] Furthermore, the amount available for early payment here differs in nature from the amount available for early payment set between May 1st and May 14th. That is, the amount available for early payment set between May 1st and May 14th was the upper limit for extremely early payments, whereas the amount available for early payment this time is the amount available for "early payment" based on the amount of the secondary order that has been confirmed and accepted by the main contractor. Therefore, these two amounts available for early payment may be completely revised or maintained as they are. The early payment management system 101 may also automatically change these amounts available for early payment.

[0154] The early payment management system 101 notifies each of the secondary subcontractors of the early payment amount set in this manner, as needed. For example, when a secondary subcontractor logs in to the application of the early payment management system 101 running on the secondary subcontractor terminal 120, they can check the early payment amount set by the primary subcontractor (the amount for extra-early payment is deducted by the early payment management system 101) on a designated system screen. The early payment management system 101 can also notify secondary subcontractors of the early payment amount via email or other means.

[0155] The secondary subcontractor then uses the application of the early payment management system 101, which runs on the secondary subcontractor terminal 120, to input the desired early payment amount and submit an early payment request (payment request). The desired early payment amount must be specified within the range of the early payment allowance mentioned above. For example, if the early payment allowance is set for each order (order ID), the entire early payment allowance will be approved in the order of the secondary subcontractor's application (early payment request) (first-come, first-served basis).

[0156] When the early payment management system 101 receives an early payment request from the secondary subcontractor terminal 120, and if it meets certain conditions, such as the requested early payment amount being within the range of the available early payment amount, it transmits the early payment transfer data to, for example, the nationwide interbank payment system 160. As a result, the early payment management system 101 transfers the requested early payment amount specified by the secondary subcontractor from the payment agent company account managed by the system (see Figure 2) to the secondary subcontractor (amount transfer (early payment)). Here, the early payment transfer data includes, for example, the secondary subcontractor ID and the remuneration amount.

[0157] Such early payments involve transferring the requested amount to the secondary contractor's bank account on the same day or the next business day after the early payment request is submitted. As shown in Figure 12, these early payment requests and corresponding payments are possible from the date the primary order information is sent until May 29th, but this can be set in any way depending on the timing of the primary order information submission. For example, the application period may be from May 15th to 29th, or if the primary order information is sent between May 1st and around May 20th, it may be from May 1st to 29th.

[0158] In this way, secondary subcontractors can receive payment for their work earlier than the usual payment date, such as June 30th, allowing them to continue operating with a more stable financial position.

[0159] Subsequently, for example, on May 30, when the final amount from the prime contractor is transferred to the payment agent company account (see Figure 2) managed by the early payment management system 101, the early payment management system 101 checks whether the transferred amount matches the remuneration amount (order amount) in the primary order information received from the prime contractor between May 15 and 20. If there are no problems, it sends primary contractor transfer data instructing the primary contractor to make the transfer, for example, to the Zengin System 160.

[0160] The primary contract transfer data includes, for example, the primary contract ID and the remuneration amount. As a result, a transfer is made from the payment agent's account to the primary contracting company's account. The transfer amount in a payment using the primary contract transfer data is the sum of the payment to the primary contracting company and the payment to the secondary contracting company. However, any amounts paid to the secondary contracting company in extra-early payment or early payment are deducted.

[0161] Furthermore, at this time, the early payment management system 101 can send secondary payment data to the primary contractor. This secondary payment data includes, for example, the secondary payment ID and the amount of compensation. Note that the amount here is calculated after deducting any amounts already paid to the secondary contractor in advance or in advance. The secondary payment data can also be viewed or downloaded from the system screen displayed after logging in to the application of the early payment management system 101 running on the primary contractor's terminal 110. The early payment management system 101 can also notify the primary contractor of the secondary payment data via email or other means.

[0162] On June 30th, the primary contractor, for example, using the primary contractor's terminal 110, will, if necessary, instruct the secondary contractor to transfer funds (payment on due date) to the secondary contractor's financial institution account. For this process, the primary contractor can utilize the secondary contractor's transfer data. The aforementioned due date transfer amount is the payment from the primary contractor to the secondary contractor. However, any amounts already paid to the secondary contractor in advance, and any amounts already paid early, will be deducted.

[0163] The above explanation has described the processing flow in the early payment management system 101 according to the second embodiment of the present application with reference to Figure 12, but the dates used are merely specific months for the sake of explanation. As in the first embodiment, if the primary order information is sent between May 1st and 20th, the period during which secondary contractors can apply for ultra-early payment, as shown in Figure 12, can be, for example, from May 1st to the day before the primary order information is sent (or immediately before the sending time), and the period during which secondary contractors can apply for early payment can be from the date the primary order information is sent. Of course, as mentioned above, it is also possible to set the start date for ultra-early payment applications to before May 1st, depending on the timing of inputting the secondary order information.

[0164] Furthermore, taxes such as consumption tax have been omitted for the sake of simplicity. In addition, fees related to the early payment management system 101 and fees related to early payments have been omitted here and will be explained later.

[0165] Figure 13 is a diagram summarizing the parts related to amounts, etc., when the work of the secondary subcontractor from the primary subcontractor is carried out continuously every month in the early payment management system 101 shown in Figure 12.

[0166] In April, the second-tier subcontractor completes work for a fee of 500,000 yen. In relation to this, the primary subcontractor, for example, at the end of April, uses the primary subcontractor terminal 110 to input secondary order information, including the order amount for each secondary subcontractor.

[0167] Here, if a secondary subcontractor uses the secondary subcontractor terminal 120 between May 1st and 14th to input the desired early payment amount and submits an early payment application, the early payment management system 101 will transfer the predetermined amount to the secondary subcontractor's financial institution account as an early payment.

[0168] The maximum amount at this time is 500,000 yen, which is the remuneration for April, but it can be set to a lower amount depending on the primary contractor's settings and the early payment management system 101. As a result, from May 1st to 14th, secondary contractors can receive at least a portion of their remuneration through early payment.

[0169] Next, let's assume that the main contractor has completed the confirmation and acceptance of the work, etc., and has sent the primary order information to the early payment management system 101 on May 15th. Subsequently, the primary contractor enters the secondary order information using the primary contractor terminal 110, for example, on May 15th. However, since the secondary order information was already entered at the end of April, it is only entered as needed, such as in the case of any subsequent corrections.

[0170] Subsequently, when the secondary subcontractor uses the secondary subcontractor terminal 120 to input the desired early payment amount and submits an early payment application, the early payment management system 101 transfers the predetermined amount as an early payment to the secondary subcontractor's financial institution account.

[0171] The maximum amount at this time is 500,000 yen, which is the remuneration for April, but it can be set to a lower amount depending on the primary contractor's settings and the early payment management system 101. Also, if a payment has been made through the aforementioned extra-early payment system, that amount may be deducted from the early payment amount. As a result, from May 15th to 29th, secondary contractors can receive at least a portion of their remuneration through early payment.

[0172] Subsequently, on June 30th, if there are still outstanding payments for April, the primary contractor will transfer the funds to the secondary contractor (payment on due date). This amount is the original order amount minus any amounts already paid as extra-early payments or early payments. The transfer will be carried out using conventional methods, and the early payment management system 101 will display, for example, the remaining balance of the secondary contractor to be transferred on the primary contractor's terminal 110.

[0173] In May, the second-tier subcontractor completes work for a fee of 750,000 yen. In relation to this, the primary subcontractor, for example, at the end of May, uses the primary subcontractor terminal 110 to input secondary order information, including the order amount for each secondary subcontractor.

[0174] Here, if a secondary subcontractor uses the secondary subcontractor terminal 120 between June 1st and 14th to input the desired early payment amount and submits an early payment application, the early payment management system 101 will transfer the predetermined amount to the secondary subcontractor's financial institution account as an early payment.

[0175] The maximum amount at this time is 750,000 yen, which is the compensation for May, but it can also be set to a lower amount depending on the primary contractor's settings and the early payment management system 101. As a result, from June 1st to 14th, secondary contractors can receive at least a portion of their compensation through early payment.

[0176] Next, let's assume that the main contractor has completed the confirmation and acceptance of the work, etc., and has sent the primary order information to the early payment management system 101 on June 15th. Subsequently, the primary contractor enters the secondary order information using the primary contractor terminal 110, for example, on June 15th. However, since the secondary order information was already entered at the end of May, it is only entered as needed, such as in the case of any subsequent corrections.

[0177] Subsequently, when the secondary subcontractor uses the secondary subcontractor terminal 120 to input the desired early payment amount and submits an early payment application, the early payment management system 101 transfers the predetermined amount as an early payment to the secondary subcontractor's financial institution account.

[0178] The maximum amount at this time is 750,000 yen, which is the compensation for May, but it can be set to a lower amount depending on the primary contractor's settings and the early payment management system 101. Also, if a payment has been made through the aforementioned extra-early payment system, that amount may be deducted from the early payment system. As a result, from June 15th to 28th, secondary contractors can receive at least a portion of their compensation through early payment.

[0179] Subsequently, on July 31st, if there are still outstanding payments for May, the primary contractor will transfer the funds to the secondary contractor (payment on due date). This amount is the original order amount minus the amount already paid as an extra-early payment and an early payment. The early payment management system 101 displays, for example, the remaining balance of the secondary contractor to be transferred on the primary contractor's terminal 110.

[0180] Similarly, a secondary subcontractor completes work for a fee of 150,000 yen in June, and in relation to this, the primary subcontractor, for example, at the end of June, uses the primary subcontractor terminal 110 to input secondary order information, including the order amount (fee) for each secondary subcontractor.

[0181] Here, if a secondary subcontractor uses the secondary subcontractor terminal 120 between July 1st and 14th to input the desired early payment amount and submits an early payment application, the early payment management system 101 will transfer the predetermined amount as an early payment to the secondary subcontractor's financial institution account.

[0182] The maximum amount at this time is 150,000 yen, which is the payment for June, but it can be set to a lower amount depending on the primary contractor's settings and the early payment management system 101. As a result, from July 1st to 14th, secondary contractors can receive at least a portion of their payment through the early payment system.

[0183] Next, let's assume that the main contractor has completed the confirmation and acceptance of the work, etc., and has sent the primary order information to the early payment management system 101 on July 15th. Subsequently, the primary contractor enters the secondary order information using the primary contractor terminal 110, for example, on July 15th. However, since the secondary order information was already entered at the end of June, it is only entered as needed, such as in the case of any subsequent corrections.

[0184] Subsequently, when the secondary subcontractor uses the secondary subcontractor terminal 120 to input the desired early payment amount and submits an early payment application, the early payment management system 101 transfers the predetermined amount as an early payment to the secondary subcontractor's financial institution account.

[0185] The maximum amount at this time is 150,000 yen, which is the payment for June. It can also be set to a lower amount depending on the primary contractor's settings and the early payment management system 101. Furthermore, if a payment has already been made through the aforementioned extra-early payment system, that amount may be deducted from the early payment amount. As a result, from July 15th to 29th, secondary contractors can receive at least a portion of their payment through early payment.

[0186] Although not shown in Figure 13, on August 31st, if there are still outstanding payments for June, the primary contractor will transfer the funds to the secondary contractor (payment on due date). This amount is the original order amount minus the amount already paid as an extra-early payment and an early payment. The early payment management system 101 displays, for example, the remaining balance of the secondary contractor to be transferred on the primary contractor's terminal 110.

[0187] Similarly, subcontractors can receive payment for their work earlier than before. Furthermore, the configuration of this early payment management system 101 gives subcontractors the opportunity to receive payment in advance at any time, as long as they are performing work each month. Taxes such as consumption tax have been omitted for the sake of simplicity. In addition, fees related to the early payment management system 101 and fees related to early payments have been omitted here and will be explained later.

[0188] [3. Third Embodiment] The early payment management system 201 according to the third embodiment of the present application enables payment to primary contractors at an earlier time than before, in addition to the functions and processes of the early payment management system 1 according to the first embodiment. Conventionally, as shown in Figure 1, primary contractors are generally paid their remuneration at the end of the month following the month in which the main contractor's confirmation and acceptance are completed, which is earlier than for secondary contractors. However, even under such circumstances, many primary contractors would like to receive their remuneration even earlier.

[0189] The early payment management system 201 according to the second embodiment of the present application also realizes early payments to primary contractors. The early payment management system 201 is the same as the early payment management system 1 according to the first embodiment in that it is configured to include at least an early payment management server 230 (a server operated and managed by a payment agent company, etc., and located on the payment agent company's site, etc.), and the early payment management server 230 is connected to the primary contractor terminal 210, the secondary contractor terminal 220, and the transaction management server 250 via a network including the Internet.

[0190] The early payment management server 230, the primary contractor terminal 210, the secondary contractor terminal 220, and the transaction management server 250 generally correspond to the early payment management server 30, primary contractor terminal 10, secondary contractor terminal 20, and transaction management server 50 of the first embodiment, respectively. The exchange of data between the early payment management server 230 and the primary contractor terminal 210, secondary contractor terminal 220, and transaction management server 250, as well as the settlement of funds between financial institution accounts, will be explained below.

[0191] Next, with reference to Figure 14, the processing flow in the early payment management system 201 according to the second embodiment of the present application will be explained.

[0192] Figure 14 shows the processing, actions, and operations performed by the prime contractor, first-tier subcontractor, second-tier subcontractor, and the early payment management system 201, using the processing from April to June as an example. Rectangles indicate processing performed by the early payment management system 201, while ellipses indicate operations and actions, including input operations to the early payment management system 201.

[0193] In April, the prime contractor places orders for work with first-tier subcontractors, who then place orders for that work with second-tier subcontractors (second-tier ordering). In this scenario, there is one prime contractor, but there can be multiple first-tier subcontractors. Similarly, there can be multiple second-tier subcontractors for a single first-tier subcontractor.

[0194] In this example, the initial order and subsequent sub-orders are placed in April, but they could be placed earlier. Furthermore, it is assumed that the work of the secondary subcontractor is completed in April, after which the primary subcontractor checks the work as needed. The prime contractor then checks and accepts the work (e.g., goods or services), and that it is determined to be satisfactory in April.

[0195] Next, the prime contractor sends primary order information, including transfer data for the confirmed remuneration amount (order amount), to the early payment management system 201 for work that was confirmed and accepted in April. The timing for sending the primary order information is, for example, between May 15th and 20th or between May 1st and 20th. This primary order information can be sent to the early payment management system 201 in various ways, such as by sharing it using a designated cloud storage service, sending it by email, or using the early payment management system 201 application (including a web application) executed on the prime contractor's terminal 240, as described above.

[0196] The primary order information mentioned above includes, for example, a prime contractor ID to identify the prime contractor, a primary contractor ID to identify the primary contractor, and the confirmed remuneration amount (order amount). It should be noted that in the Early Payment Management System 201, the prime contractor ID, primary contractor ID, and secondary contractor ID to identify the prime contractor, primary contractor, and secondary contractor, respectively, are assumed to be registered prior to the required timing. Furthermore, information necessary for transactions and settlements, such as the financial institution accounts of the prime contractor, primary contractor, and secondary contractor, is also assumed to be registered in advance.

[0197] When the early payment management system 1 receives primary order information, it assigns an order ID and notifies the primary contractor and the prime contractor of the order ID. The order ID may be notified by email or other means, or, in the case of the primary contractor, by an application (including a web application) of the early payment management system 201 running on the primary contractor's terminal 210.

[0198] Next, the primary contractor logs in to the application of the early payment management system 201, which runs on the primary contractor terminal 210, and enters the secondary order information. In this example, the order ID, secondary order ID, and the amount of the secondary order for each secondary contractor are entered. Furthermore, the application of the early payment management system 201, which runs on the primary contractor terminal 210, enters the amount available for early payment. Here, the amount available for early payment is the amount of the order placed by the primary contractor with the secondary contractor that can be paid earlier than the conventional timing (for example, the timing of June 30th in Figure 1), and various setting methods are possible, such as setting it for each secondary contractor or setting it for each order (order ID). Note that the amount available for early payment can also be automatically set by the early payment management system 201 based on the amount of the secondary order, etc., in which case the primary contractor does not need to enter the amount available for early payment.

[0199] Here, the primary contractor further uses the primary contractor terminal 210 to input the amount it wishes to receive early (the primary contractor's early payment request amount) and sends it to the early payment management system 201 (payment request). At this time, the order ID and amount data are sent to the early payment management system 201 (it is assumed that the primary contractor's primary contractor ID is known through login, etc.). Here, the condition is that the primary contractor's early payment request amount does not exceed the total remuneration amount included in the primary order information (the total remuneration amount for the primary and secondary contractors). Also, when setting an amount that can be paid early to the secondary contractor, the condition is that the sum of the primary contractor's early payment request amount and the amount that can be paid early to the secondary contractor does not exceed the total remuneration amount included in the primary order information.

[0200] When the Early Payment Management System 201 receives an early payment request from the primary contractor, it transmits the primary contractor early payment transfer data to, for example, the Zengin System 260. As a result, the Early Payment Management System 201 transfers the specified early payment request amount to the primary contractor from the payment agent company account managed by the Early Payment Management System 201 (see Figure 2) (amount transfer (primary contractor early payment)). Here, the primary contractor early payment transfer data includes, for example, the primary contractor ID and the amount.

[0201] In such cases of early payment to the primary contractor, the requested amount is transferred to the primary contractor's bank account on the same day or the next business day after the early payment request is made. Furthermore, as shown in Figure 14, such early payment requests and corresponding transfers (early payments to primary contractors) are possible from the date the primary order information is sent until May 29th, but this can be set in any way depending on the timing of the primary order information transmission. For example, the application period may be from May 15th to 29th, or if the primary order information is sent between May 1st and around May 20th, it may be from May 1st to 29th.

[0202] In this way, primary contractors can receive payment for their work, at least a portion of it, earlier than the usual payment date, such as May 31st, allowing them to continue operating with a more stable financial position.

[0203] Furthermore, as mentioned above, the amount requested for early payment to the primary contractor must be less than or equal to the total remuneration amount, but other prescribed conditions (for example, an amount based on a percentage of past remuneration performance) may be attached.

[0204] Next, the early payment management system 201 notifies each of the secondary subcontractors of the amount they are eligible for early payment, which has been set for them. For example, when a secondary subcontractor logs in to the application of the early payment management system 201 running on their secondary subcontractor terminal 220, they can check the amount they are eligible for early payment, which has been set by the primary subcontractor, on a designated system screen. The early payment management system 201 can also notify secondary subcontractors of the amount they are eligible for early payment via email or other means.

[0205] The secondary subcontractor then uses the application of the early payment management system 201, which runs on the secondary subcontractor terminal 220, to input the desired early payment amount and submit an early payment request (payment request). The desired early payment amount must be specified within the range of the early payment allowance mentioned above. For example, if the early payment allowance is set for each order (order ID), the entire early payment allowance will be granted to the secondary subcontractors in the order in which they submitted their requests (first-come, first-served basis).

[0206] When the early payment management system 201 receives an early payment request from the secondary subcontractor terminal 220, and if it meets certain conditions, such as the requested early payment amount being within the range of the available early payment amount, it transmits the early payment transfer data to, for example, the nationwide interbank payment system 260. As a result, the early payment management system 201 transfers the requested early payment amount specified by the secondary subcontractor from the payment agent company account managed by the system (see Figure 2) to the secondary subcontractor (amount transfer (early payment)). Here, the early payment transfer data includes, for example, the secondary subcontractor ID and the amount.

[0207] Such early payments are, for example, transferred to the secondary contractor's bank account on the same day or the next business day after the early payment request is made. Furthermore, as shown in Figure 14, these early payment requests and corresponding transfers (early payments) are possible from the date the primary order information is sent until May 29th, but this can be set in any way depending on the timing of the primary order information's transmission. For example, the application period may be from May 15th to 29th, or if the primary order information is sent between May 1st and around May 20th, it may be from May 1st to 29th.

[0208] In this way, secondary subcontractors can receive payment for their work earlier than the usual payment date, such as June 30th, allowing them to continue operating with a more stable financial position.

[0209] Subsequently, for example, on May 30, when the final amount from the prime contractor is transferred to the payment agent company account (see Figure 2) managed by the early payment management system 201, the early payment management system 201 checks whether the transferred amount matches the remuneration amount (order amount) in the primary order information received from the prime contractor between May 15 and 20. If there are no problems, it sends primary contractor transfer data instructing the primary contractor to make the transfer, for example, to the Zengin System 260.

[0210] The primary contract payment data includes, for example, the primary contract ID and the amount. Based on this primary contract payment data, a transfer is made from the payment agent's account to the primary contracting company's account. The amount transferred based on the primary contract payment data is the sum of the remuneration amount to the primary contracting company and the remuneration amount to the secondary contracting company. However, any amounts paid early to the primary contracting company and amounts paid early to the secondary contracting company are deducted.

[0211] Furthermore, at this time, the early payment management system 201 can send secondary payment data to the primary contractor. This secondary payment data includes, for example, the secondary payment ID and the amount. Note that the amount here is after deducting the amount already paid to the secondary contractor. The secondary payment data can also be displayed on the system screen or downloaded by logging into the application of the early payment management system 201 running on the primary contractor's terminal 210. The early payment management system 201 can also notify the primary contractor of the secondary payment data via email or other means.

[0212] On June 30th, the primary contractor, for example, using the primary contractor's terminal 210, will, if necessary, instruct the secondary contractor to transfer funds (payment on due date) to the secondary contractor's financial institution account. For this process, the primary contractor can utilize the secondary contractor's transfer data. The aforementioned due date transfer amount is the payment from the primary contractor to the secondary contractor. However, any amount already paid to the secondary contractor in advance will be deducted.

[0213] The above explanation, with reference to Figure 14, describes the processing flow in the early payment management system 201 according to the third embodiment of this application. The dates used are merely specific months for the sake of explanation. As with the first embodiment, if the primary order information is transmitted between May 1st and 20th, the input period for the primary contractor's available early payment amount and the application period for the secondary contractor's early payment, as shown in Figure 14, can be as early as May 1st, although this depends on the timing of the primary contractor's input of the secondary order information and the available early payment amount. Of course, if the primary order information is transmitted earlier than May 1st, the start timing of the input period for the primary contractor's available early payment amount and the application period for the secondary contractor's early payment can be set to earlier than May 1st accordingly.

[0214] Furthermore, taxes such as consumption tax have been omitted for the sake of simplicity. In addition, fees related to the Early Payment Management System 201 and fees related to early payments have been omitted here and will be explained later.

[0215] Furthermore, the early payment management system 201, when combined with the configuration of the early payment management system 101 according to the second embodiment described above, can adopt an "ultra-early payment" system that allows primary contractors to pay earlier than the prime contractor's final payment date (for example, May 15th to 20th). In this case, while applications for early payment are possible from May 15th to 29th, applications for ultra-early payment can be set to be possible at various earlier times than early payment, including April when the secondary order is placed and May 1st to 14th.

[0216] [4. Patterns for setting the amount available for early payment] Next, referring to Figure 15, we will explain examples of patterns for setting the amount of early payment available at the primary contractor's terminal 10, etc. (including primary contractor's terminal 110 and primary contractor's terminal 210).

[0217] In the example in Figure 15, the prime contractor places an order for 10 million yen, and the primary contractor then subcontracts it to four secondary contractors (secondary subcontracting), with the primary contractor paying 2 million yen and the total payment to the secondary contractors amounting to 8 million yen. For the sake of simplicity, taxes such as consumption tax, as well as fees related to the early payment management system and fees related to early payment, are omitted here. Furthermore, setting patterns No. 1 and No. 2 relate to the early payment management systems 1 and 301 according to the first and second embodiments, respectively, where early payment to the primary contractor is not made. Setting patterns No. 3 to No. 7, like the early payment management system 201 according to the third embodiment, allow for early payment to the primary contractor.

[0218] In setting pattern No. 1, the amount that can be paid early to the secondary subcontractors is set at 8 million yen by the primary subcontractor. This setting means that all four secondary subcontractors can pay the full amount early.

[0219] In setting pattern No. 2, the amount that can be paid early to the secondary subcontractors is set at 4 million yen by the primary subcontractor. Alternatively, this could be set so that each of the four secondary subcontractors can pay 50% of the price early. Or, the four secondary subcontractors could collectively pay 50% early, in which case, for example, applications for early payment could be accepted on a first-come, first-served basis. It is also possible to set the amount that can be paid early for each of the four secondary subcontractors individually, resulting in a total of 50% being paid early.

[0220] From setting pattern No. 3 onwards, early payment to the primary contractor is also possible, as in the early payment management system 201 according to the third embodiment. In this setting, the primary contractor is able to pay the full amount (2 million yen) early, and all four secondary contractors are able to pay the full amount early.

[0221] In setting pattern No. 4, the primary contractor can make an early payment of the full amount (2 million yen). For the secondary contractors, the amount they can pay early is set at 4 million yen, and this can be set for all four secondary contractors collectively or individually, similar to setting pattern No. 2.

[0222] In setting pattern No. 5, the primary contractor can make an early payment of up to 4 million yen, exceeding the full amount of the payment (2 million yen). For the secondary contractors, the amount they can make an early payment of is set at 6 million yen. Similar to setting pattern No. 2, this amount can be set for all four secondary contractors collectively or individually. The primary contractor has received an early payment of 2 million yen in addition to the 2 million yen equivalent to their own payment. Therefore, when making the due payment to the secondary contractors on June 30th (see Figures 10, 12, and 14), they need to repay this 2 million yen to cover the due payment. Also, since the primary contractor has received an early payment of 4 million yen, the maximum amount that secondary contractors can make an early payment of is 6 million yen (because the total order amount is 10 million yen).

[0223] In setting pattern No. 6, the primary contractor can make an early payment of up to 4 million yen, exceeding the full amount of the payment (2 million yen). However, the amount that secondary contractors can make an early payment of is set to 0, meaning that the four secondary contractors cannot receive any early payment. The primary contractor has received an early payment of 2 million yen in addition to the 2 million yen equivalent to their own payment, so when they make the due payment to the secondary contractors on June 30th (see Figures 10, 12, and 14), they will need to repay this 2 million yen and use it for that due payment.

[0224] In setting pattern No. 7, the primary contractor can make early payments of up to 10 million yen, exceeding the full amount of the payment (2 million yen). However, the amount that secondary contractors can make early payments is set to 0, meaning that the four secondary contractors cannot receive any early payments. The primary contractor has received an additional 8 million yen in early payment on top of the 2 million yen that corresponds to their payment. Therefore, when making the due payment to the secondary contractors on June 30th (see Figures 10, 12, and 14), they must repay this 8 million yen and use it for that due payment.

[0225] As shown above, the setting patterns for the amount of early payment available can be varied, including cases where the primary contractor receives early payment. The setting pattern shown in Figure 15 is just one example, and various other setting patterns can be adopted.

[0226] Furthermore, as in the early payment management system 101 according to the second embodiment, it is also possible to implement ultra-early payment, where the transfer is made to the secondary subcontractor at an earlier time than the early payment, and it is also possible to implement ultra-early payment for the primary subcontractor. In these cases as well, the same early payment amount as the settings for early payment shown in Figure 15 can be set. Here, the early payment amount is also set as the upper limit for ultra-early payment.

[0227] Furthermore, it is possible to switch the setting for the amount available for early payment to different levels for early payment and extra early payment, that is, to change the upper limit.

[0228] Next, referring to Figure 16, we will explain the patterns for setting the amount available for early payment using more specific examples.

[0229] The order shown in Figure 16(A) (Order ID=0001) is, for example, one for which confirmation and acceptance by prime contractor A1 was completed in April. The payment from primary contractor B1 is 2 million yen, and the total payment from the four secondary contractors is 8 million yen. Primary contractor B1 sets the amount that secondary contractors can pay early on an "individual" basis.

[0230] The payments for subcontractors C1, C2, C3, and C4 are ¥1,000,000, ¥2,000,000, ¥2,000,000, and ¥3,000,000, respectively. The amounts available for early payment are set at ¥800,000, ¥1,600,000, ¥2,000,000, and ¥0 for subcontractors C1, C2, C3, and C4, respectively. As a result, subcontractors C1 and C2 are limited to an 80% early payment limit, subcontractor C3 can pay the entire amount early (100%), and subcontractor C4 is not allowed to make any early payments (0%).

[0231] Figure 16(B) shows, for example, two orders (Order 1 (Order ID=0002), Order 2 (Order ID=0003)) for which confirmation and acceptance by prime contractor A1 were completed in April. In Order 1, the payment to primary contractor B1 is 2 million yen, and the total payment to the four secondary contractors is 8 million yen. In Order 2, the payment to primary contractor B1 is 4 million yen, and the total payment to the four secondary contractors is 16 million yen. Here, primary contractor B1 sets the amount that secondary contractors can pay early "for each order".

[0232] The amounts due to subcontractors C1, C2, C3, and C4 for Order 1 are 1 million yen, 2 million yen, 2 million yen, and 3 million yen, respectively. The amount available for early payment is set at 6 million yen for Order 1 as a whole by the primary contractor B1. The amounts due to subcontractors C1, C5, C6, and C7 for Order 2 are 3 million yen, 4 million yen, 4 million yen, and 5 million yen, respectively. The amount available for early payment is set at 14 million yen for Order 2 as a whole by the primary contractor B1.

[0233] As a result, the subcontractors C1, C2, C3, and C4 of Order 1 will be granted early payment up to a limit of 6 million yen, in the order in which they applied for early payment. Therefore, if subcontractors C1, C2, C3, and C4 apply for early payment first, they will each be able to receive 100% of the payment in early payment.

[0234] Furthermore, the second-tier subcontractors C1, C5, C6, and C7 of Order 2 will be granted early payment up to a limit of 14 million yen, in the order in which they apply for early payment. Therefore, if the second-tier subcontractors C1, C5, C6, and C7 apply for early payment first, they will each be able to receive 100% of the payment in early payment.

[0235] Here, the secondary subcontractor C1 is involved in both Order 1 and Order 2, and can apply for early payment for both simultaneously. The early payment management system in each embodiment of the present invention allows the secondary subcontractor to input the desired early payment amount for each Order ID on the early payment application screen displayed on their terminal. Alternatively, one input field for the desired early payment amount can be provided on the early payment application screen, in which case the early payment management system can be configured to determine how to allocate the early payment amount from the available early payment amount for Order 1 (6 million yen) and the available early payment amount for Order 2 (14 million yen).

[0236] Figure 17 shows, for example, Order 1 (Order ID=0004), for which confirmation and acceptance by prime contractor A1 was completed in April, and Order 2 (Order ID=0005), for which confirmation and acceptance by prime contractor A2 was completed in April. In Order 1, the price from primary contractor B1 is 2 million yen, and the total price from the four secondary contractors is 8 million yen. In Order 2, the price from primary contractor B1 is 4 million yen, and the total price from the four secondary contractors is 16 million yen. Here, primary contractor B1 sets the amount of early payment available to the secondary contractors "together for both orders".

[0237] The payments to subcontractors C1, C2, C3, and C4 for Order 1 are 1 million yen, 2 million yen, 2 million yen, and 3 million yen, respectively. The payments to subcontractors C1, C5, C6, and C7 for Order 2 are 3 million yen, 4 million yen, 4 million yen, and 5 million yen, respectively. In addition, the amount available for early payment is set by the primary contractor B1 to 20 million yen for the total of both orders.

[0238] As a result, the second-tier subcontractors C1, C2, C3, C4, C5, C6, and C7 involved in orders 1 and 2 will be granted early payment up to a limit of 20 million yen, in the order in which they applied for early payment.

[0239] [5. GUI for the Early Payment Management System] Next, with reference to Figures 18 to 20, an overview of the GUI in the early payment management system of the present application (including the early payment management system 1 of the first embodiment, the early payment management system 101 of the second embodiment, the early payment management system 201 of the third embodiment, etc.) will be described.

[0240] The secondary order information input screen 400 shown in Figure 18(A) is a screen displayed by the primary contractor for inputting secondary order information. For example, after logging in to the early payment management system application (including a web application) running on the primary contractor's terminal, the screen is displayed on the primary contractor's terminal's display by selecting (touching or clicking with a mouse) the "Secondary Order Information Input" button on the menu screen (not shown).

[0241] On the secondary order information input screen 400, as described above, since this is an operation performed after logging in, for example, the login ID of the primary contractor (in this case, "S001") and the company name (in this case, "◇◇ Company") are displayed in the upper right corner.

[0242] Here, when a representative from the primary contractor enters the order ID of the order for which they intend to enter secondary order information into the order ID input field, the order date, confirmation date (date of primary order information transmission), prime contractor name, and order amount for the entered order ID will be displayed. The order ID is an ID assigned and notified by the early payment management system when the prime contractor completes confirmation and acceptance of the work etc. for the previous month and sends primary order information containing data on the confirmed amount to the early payment management system.

[0243] In the early payment management system 101 of the second embodiment, as described above, an order ID is assigned and notified after the secondary order information has been entered, so there is no need to enter an order ID.

[0244] The primary contractor's representative identifies the order by entering the order ID in the order ID input field. Then, to specify the secondary contractor and the order amount to that secondary contractor, they enter the secondary contractor ID and the order amount. When the secondary contractor ID is entered, the early payment management system displays the name of the secondary contractor corresponding to the registered secondary contractor ID. Multiple secondary contractors can also be registered by touching the "Add" button, etc. A checkbox is placed at the left end of the order display row representing the order amount of each secondary contractor. Checking this checkbox and touching the "Delete" button, etc., will delete that order display row.

[0245] When a representative from the primary contractor touches the "Register" button located at the bottom of the secondary order information input screen 400, the contents of the entered order display row are registered and associated with the order ID. On the other hand, if they touch the "Cancel" button, the entered secondary order information is canceled.

[0246] The early payment amount input screen 410 shown in Figure 18(B) is a screen displayed by the primary contractor to set the conditions for the amount to be paid early to the secondary contractor. For example, after logging in to the early payment management system application (including a web application) running on the primary contractor's terminal, the screen is displayed on the primary contractor's terminal's display by selecting (touching or clicking with a mouse) the "Early Payment Amount Input" button on the menu screen (not shown).

[0247] On screen 410, the early payment amount input screen, as described above, is an operation performed after logging in. For example, the login ID of the primary contractor (in this case, "S001") and the company name (in this case, "◇◇ Company") are displayed in the upper right corner.

[0248] Here, when a representative from the primary contractor enters an order ID in the order ID input field, the order date, confirmation date (date of primary order information transmission), prime contractor name, and order amount for the entered order ID will be displayed. The order ID is an ID assigned and notified by the early payment management system when the prime contractor completes confirmation and acceptance of the work for the previous month and sends primary order information containing data on the confirmed amount to the early payment management system.

[0249] Furthermore, on screen 410 for entering the early payment amount, the application period is displayed, and here it is automatically set from today (20240515) to the end of the month (20240531), when the early payment amount is specified. It is also possible to design the system so that the person in charge at the primary contractor enters this application period.

[0250] The primary contractor's representative identifies the order by entering the order ID in the order ID input field, and then specifies the amount of early payment available to the secondary contractor. In this example, three methods are provided for specifying the amount of early payment available.

[0251] The first method is "individual specification," where the amount available for early payment is specified individually for each subcontractor. The second method is "overall specification," where the amount available for early payment is specified as a general framework for each order. The third method is "percentage specification," where the amount available for early payment is set as a certain percentage of the order amount. In addition to these, various other variations can be considered for setting the amount available for early payment, such as the unit, range, and amount set.

[0252] Here, the amount available for early payment is specified individually, and the checkbox to the left of "Individual Specification" is checked. When this check is performed, each order display row representing the secondary orders for the order corresponding to the order ID is displayed. For example, in this example, for each secondary subcontractor, the secondary subcontracting ID (C1, C2, C3, C4), company name, and order amount are displayed, and an input field for the amount available for early payment for each secondary subcontractor is also displayed.

[0253] Here, the primary contractor's representative enters the amount of the secondary contractor willing to pay early in the early payment amount input field. The early payment amount is an amount less than or equal to the order amount. In this case, the early payment amount for each secondary contractor is set according to the setting pattern shown in Figure 16(A). After that, the early payment amount is registered by touching the "Add" button or similar.

[0254] Furthermore, in the early payment management system 101 according to the second embodiment, by entering the early payment amount via the early payment amount input screen 410, the upper limit amount for the extra-early payment application (extra-early payment amount) can also be set at the same time. In addition, the early payment management system 101 can also be configured to allow the setting of the extra-early payment amount to be entered in an extra-early payment amount input field different from the early payment amount input field, or to be entered on a separate screen (for example, an extra-early payment amount input screen).

[0255] The early payment request screen 420 shown in Figure 19 is a screen displayed for secondary subcontractors to specify the amount they wish to receive as an early payment (i.e., the desired early payment amount). For example, after logging in to the early payment management system application (including a web application) running on the secondary subcontractor's terminal, the screen is displayed on the secondary subcontractor's terminal's display by selecting (touching or clicking with a mouse) the "Early Payment Request" button on the menu screen (not shown).

[0256] On the early payment application screen 420, as described above, since this is an operation performed after logging in, for example, the login ID of the secondary subcontractor (in this case, "M001") and the company name (in this case, "○○ Company") are displayed in the upper right corner.

[0257] Here, when a representative from a secondary subcontractor enters the order ID of the order for which they wish to receive early payment into the order ID input field, the order date, confirmation date (date of primary order information transmission), and the name of the primary subcontractor for the entered order ID will be displayed. The order ID is assigned by the early payment management system when the prime contractor completes confirmation and acceptance of the work for the previous month and sends primary order information, including data on the confirmed amount, to the early payment management system. This ID is then notified to the secondary subcontractor when the primary subcontractor enters secondary order information, etc.

[0258] Furthermore, on the early payment application screen 420, when an order ID is entered, the application period during which early payment can be requested, the order amount for the currently logged-in secondary subcontractor, and the amount available for early payment (set by the primary subcontractor) are displayed. Additionally, input fields for the desired early payment amount and the desired transfer date are displayed.

[0259] Here, the representative of the secondary subcontractor enters the amount they wish to receive as an early payment in the "Desired Early Payment Amount" field, and then enters the desired date for the transfer of that amount to the secondary subcontractor's bank account in the "Desired Transfer Date" field. The requested early payment amount must be less than or equal to the amount available for early payment. Furthermore, if the early payment management system is configured to transfer the requested early payment amount at a specific time, such as immediately, on the same day, or on the next business day, the "Desired Transfer Date" field is unnecessary.

[0260] When a representative from a secondary subcontracting company enters the desired early payment amount in the input field and the desired transfer date in the input field, and then touches the "OK" button, the early payment request is confirmed, and the requested early payment amount is transferred to their bank account, for example, on the desired transfer date.

[0261] Furthermore, on the early payment application screen 420, the application period is controlled to vary depending on the order ID. For example, for orders related to work for which the main contractor's confirmation and acceptance were completed in April, the application period will be from May 15th to 29th.

[0262] Furthermore, on the early payment application screen 420, if the person in charge at the primary contractor specifies the amount eligible for early payment using the "overall limit specification" on the early payment amount input screen 410, the amount eligible for early payment will fluctuate depending on the timing. For example, as shown in Figure 19, even if the initial amount eligible for early payment is 650,000 yen, if another secondary contractor receives an early payment first, the overall limit for the amount eligible for early payment will decrease, and the amount eligible for early payment will fall below 650,000 yen.

[0263] The ultra-early payment application screen 430 shown in Figure 20 is a screen displayed in the early payment management system 101 according to the second embodiment. Similar to the early payment application screen 420, this screen is displayed for secondary contractors to specify the amount they wish to receive as ultra-early payment (i.e., the desired ultra-early payment amount). For example, after logging in to the application (including a web application) of the early payment management system 101 running on the secondary contractor terminal 120, the screen is displayed on the secondary contractor terminal 120's display by selecting (touching or clicking with a mouse) the "Ultra-Early Payment Application" button on the menu screen (not shown).

[0264] On the super early payment application screen 430, as described above, since this is an operation performed after logging in, for example, the login ID of the secondary subcontractor (in this case, "M001") and the company name (in this case, "○○ Company") are displayed in the upper right corner.

[0265] Here, when a representative from the secondary subcontractor enters the order ID of the order for which they wish to receive early payment into the order ID input field, the order date and the name of the primary subcontractor for the entered order ID are displayed. The order ID is an ID assigned by the early payment management system 101 when secondary order information is entered by the primary subcontractor and notified to the secondary subcontractor. This order relates to work from the previous month, and although the main contractor has completed confirmation and acceptance, the primary order information, including data on the finalized amount, has not yet been sent to the early payment management system 101.

[0266] Furthermore, on the early payment application screen 430, when a purchase order ID is entered, the applicable application period for early payment applications, the amount of the order received by the secondary contractor logged in for that purchase order, and the early payment available amount (set by the primary contractor) are displayed. Also, an early payment desired amount input field for entering the desired amount of early payment and a transfer desired date input field for entering the desired date of transfer are displayed.

[0267] Here, the person in charge of the secondary contractor enters the amount they wish to receive as early payment in the early payment desired amount input field, and further enters the desired date they want the amount of the early payment desired amount to be transferred to the financial institution account etc. of the secondary contractor in the transfer desired date input field. The early payment desired amount must be less than or equal to the early payment available amount. Also, if the early payment management system 101 is configured to transfer the early payment desired amount at a specific timing such as immediately, within the day, or the next business day, the transfer desired date input field is not necessary.

[0268] After the person in charge of the secondary contractor enters the early payment desired amount in the early payment desired amount input field and enters the transfer desired date in the transfer desired date input field, and then touches the "OK" button etc., the early payment application is confirmed, and the early payment desired amount is transferred to, for example, their own financial institution account on the transfer desired date.

[0269] Note that on the early payment application screen 430, the applicable application period is controlled to be different according to the purchase order ID. For example, for a purchase order related to work where the confirmation and inspection etc. of the prime contractor are completed in April but the primary purchase order information has not been sent, it is from May 1st to 14th. As described regarding FIG. 12, it may be possible to apply for early payment before May 1st.

[0270] Also, on the early payment application screen 430, similar to the early payment application screen 420, when the person in charge of the primary contractor designates the early payment available amount by "overall frame designation" on the early payment available amount input screen 410, the early payment available amount fluctuates depending on the timing.

[0271] Also, both the early payment application screen 420 and the ultra-early payment application screen 430 may be displayed on a common screen and be made operable by the person in charge of the secondary contracting company. Also, at this time, on the date when the common screen is displayed, early payment applications and ultra-early payment applications for multiple orders may be possible. In that case, before displaying the common screen, it is possible to control to display an order selection screen for selecting the target order.

[0272] The early payment available amount input screen 440 shown in FIG. 21 is a screen displayed in the early payment management system 201 according to the third embodiment. This screen is a screen displayed for the prime contractor company to set the conditions for the amount to be paid early to the secondary contractor company, similar to the early payment available amount input screen 410. For example, after logging in with an application (including a WEB application) of the early payment management system 201 executed on the prime contractor company terminal 210, select the "Early payment available amount input" button on the menu screen (not shown) (by touching or clicking with a mouse), etc., and it is displayed on the display of the prime contractor company terminal 210.

[0273] Also, on the early payment available amount input screen 440, not only the early payment available amount for the secondary contractor company but also the early payment available amount of itself (i.e., the prime contractor company) can be set so that the prime contractor company itself can receive the payment early.

[0274] On the early payment available amount input screen 440, as described above, since it is an operation after logging in, for example, in the upper right, the login ID of the prime contractor company (here, "S001") and the company name (here, "◇◇ Company") are displayed.

[0275] Here, when the person in charge of the prime contractor company inputs the order ID in the order ID input field, the order date, confirmation date (primary order information transmission date), prime contractor company name, and order amount of the input order ID are displayed. The order ID is an ID numbered and notified by the early payment management system when the primary contractor company transmits primary order information including data on the amount that has been confirmed and finalized for the previous month's work, etc., to the early payment management system.

[0276] First, the primary contractor's representative identifies the order by entering the order ID in the order ID input field, and then enters the amount they (the primary contractor) are eligible for early payment in the primary contractor's early payment amount input field. The amount entered here is less than or equal to the order amount. This amount can be immediately transferred to the primary contractor's financial institution account, etc., when the "Register" button is clicked, etc. In this sense, entering an amount in the primary contractor's early payment amount input field is equivalent to an early payment application by the primary contractor.

[0277] Furthermore, on screen 440 for entering the early payment amount, the application period is displayed, and here it is automatically set from today (20240515) to the end of the month (20240529), when the early payment amount is specified. It is also possible to design the system so that the person in charge at the primary contractor enters this application period.

[0278] Next, the primary contractor's representative specifies the amount of early payment available to the secondary contractor for the order with the specified order ID. In this example, three methods are provided for specifying the amount of early payment available.

[0279] The first method is "individual specification," where the amount available for early payment is specified individually for each subcontractor. The second method is "overall specification," where the amount available for early payment is specified as a general framework for each order. The third method is "percentage specification," where the amount available for early payment is set as a certain percentage of the order amount. In addition to these, various other variations can be considered for setting the amount available for early payment, such as the unit, range, and amount set.

[0280] Here, the amount available for early payment is specified individually, and the checkbox to the left of "Individual Specification" is checked. When this check is performed, each order display row representing the secondary orders for the order corresponding to the order ID is displayed. For example, in this example, for each secondary subcontractor, the secondary subcontracting ID (C1, C2, C3, C4), company name, and order amount are displayed, and an input field for the amount available for early payment for each secondary subcontractor is also displayed.

[0281] Here, the person in charge at the primary contractor enters the amount that the secondary contractor can pay early into the input field for the amount that can pay early. The amount that can pay early is an amount less than or equal to the order amount. Here, as in the example in Figure 18(B), the amount that can pay early for each secondary contractor is to be set according to the setting pattern for the amount that can pay early shown in Figure 16(A). However, because 7.6 million yen is specified in the input field for the amount that can pay early for the primary contractor in order to receive early payment for itself, the secondary contractor can only set the remaining amount of the order amount, 2.4 million yen, as the amount that can pay early. As a result, the amount that can pay early for secondary contractor C3 is 0 yen (although it would be 2 million yen according to the setting pattern in Figure 16(A)).

[0282] The early payment performance display screen 450 shown in Figure 22 is a screen that displays the results of early payment requests by secondary subcontractors. For example, after logging in to the early payment management system application (including a web application) executed on the primary subcontractor's terminal, the screen is displayed on the primary subcontractor's terminal by selecting (touching or clicking with a mouse) the "Display Early Payment Performance" button on the menu screen (not shown).

[0283] On the early payment history display screen 450, as described above, since this is an operation performed after logging in, for example, the login ID of the primary contractor (in this case, "S001") and the company name (in this case, "◇◇ Company") are displayed in the upper right corner.

[0284] Here, the primary contractor's representative specifies one order ID from the list of order IDs related to them in the order ID specification field. The order date, confirmation date (date of primary order information transmission), prime contractor name, and order amount for the specified order ID are then displayed. The order ID is for orders that have been handled previously, where the prime contractor has completed confirmation and acceptance of the work, and primary order information containing data regarding the confirmed amount has been sent to the early payment management system.

[0285] When an order ID is specified in the order ID field, information about the secondary subcontractor related to that order is displayed. For example, as shown in Figure 22, the application period for that order is displayed, and furthermore, information about the secondary subcontractor related to the order is displayed in each display row. Each display row contains the secondary subcontractor ID, which is an ID used to identify the secondary subcontractor, the name of the secondary subcontractor, the order amount, the amount that can be paid early, the amount that was actually transferred as an early payment request, and the early payment date, which indicates the date the early payment was made.

[0286] In this example, the early payment amount for each subcontractor is set according to the early payment amount setting pattern shown in Figure 16(A). Subcontractor C1 has an early payment amount of 800,000 yen, and a transfer of 650,000 yen was made on May 15th. Subcontractor C2 has an early payment amount of 1,600,000 yen, and a transfer of 1,000,000 yen was made on May 20th. Subsequently, due to the above transfer, the early payment amount became 600,000 yen, and a transfer of 600,000 yen was made on May 29th. Subcontractor C2 can also apply for early payment multiple times during the period, and the early payment amount will be reduced by the amount of the previous early payment. Also, as described above, if the early payment amount is set using "overall limit designation," the overall limit for early payment amounts will decrease due to early payments by other subcontractors, and in that case, the early payment amount will also be reduced.

[0287] Secondary subcontractor C3 has an early payment option of 2 million yen, but has not made an early payment. Also, secondary subcontractor C4 is not permitted to make an early payment (early payment option is 0 yen).

[0288] Touching the "Back" button will return you to the original menu screen. If the order ID is changed in the order ID specification field, the above information regarding early payment for the order corresponding to that order ID will be displayed.

[0289] Furthermore, it is also possible to display information related to ultra-early payment applications in the early payment management system 101 according to the second embodiment, and information related to early payment applications from primary contractors in the early payment management system 201 according to the third embodiment, but these will be omitted here.

[0290] In addition, payment agency companies and the like that operate and manage the early payment management server of the early payment management system can use the terminal connected to the early payment management server to check the items displayed on the above early payment performance display screen 450, and can also input various setting values including handling fees and the like.

[0291] [6. Fourth Embodiment] The early payment management system 301 according to the fourth embodiment of the present application partially expands the functions of the above-mentioned early payment management system 1 according to the first embodiment. In the early payment management system 301, as shown in FIG. 23, the period during which a secondary contractor can apply for early payment is set from May 15th to June 10th, enabling early payment applications for a longer period than in the first embodiment. Here, the dates are just examples, and the fact that April to June is shown in FIG. 23 is also for illustration purposes.

[0292] Also, in the early payment management system 301, as described above, for secondary contractors, in order to enable early payment applications even in June, the amount of the first contractor transfer data on May 31st only includes the payment to the first contractor, and does not include the payment to the secondary contractor as in the case of the early payment management system 1 of the first embodiment.

[0293] Then, the early payment management system 301 generates secondary contractor transfer data on June 30th, which is the conventional payment timing to the secondary contractor, and according to this data, an amount is transferred from the financial institution account of the payment agency company to the financial institution account of the secondary contractor (amount transfer (due date payment)). Also, the amount at this time is the amount obtained by subtracting the amount transferred by early payment from the order amount.

[0294] Such a configuration of the early payment management system 301 according to the fourth embodiment can be applied to the early payment management systems (1, 101, 201) of the first to third embodiments respectively.

[0295] Furthermore, in the above example, the primary contractor sets an early payment amount for the secondary contractor, and the secondary contractor applies for early payment. However, the early payment management system can also be used to allow the secondary contractor to set an early payment amount for the tertiary contractor, and the tertiary contractor applies for early payment. In this way, early payments can be similarly implemented for the client's subcontractors thereafter.

[0296] [7. Fees] In the descriptions of the first to fourth embodiments of the early payment management system (1, 101, 201, 301) described above, the explanation of fees was omitted, but in these early payment management systems, for example, the secondary subcontractor bears the fee.

[0297] Specifically, the primary contractor indicates the amount that can be paid early, and when a secondary contractor enters the desired early payment amount on the secondary contractor's terminal 20 within that range and submits an early payment application, for example, an amount less than the amount actually indicated as the desired early payment amount will be transferred to the secondary contractor's financial institution account. With this configuration of the present invention, the early payment management system collects the difference between the desired early payment amount and the amount transferred as a fee.

[0298] For example, in the early payment application screen 420 shown in Figure 19, the requested early payment amount is 650,000 yen, but the actual amount transferred will be, for example, 630,500 yen (assuming a 3% fee). Note that the early payment application screen 420 in Figure 19 does not display the fee or the actual amount transferred, but it may be made to display the fee and calculate and display the transfer amount when the requested early payment amount is entered. Similarly, the extra-early payment application screen 430 shown in Figure 20 may also be made to display the fee and the transfer amount.

[0299] Furthermore, this application enables early payment for primary contractors, ultra-early payment for secondary contractors, and early payment. Primary and secondary contractors can choose the date to apply within the application period, and the fees can be varied depending on the application date or the transfer date on which at least a portion of the remuneration is transferred as a result of the application. The fees can also be varied depending on the amount requested for ultra-early payment or early payment.

[0300] Furthermore, in this application, as described above, only secondary subcontractors who are able to receive at least a portion of their remuneration early will have a fee deducted from the actual amount transferred when they apply for extra-early payment or early payment. However, it is also possible to collect some kind of fee from other businesses, such as prime contractors and primary subcontractors. In addition, while the method of collecting the fee here is deduction, other methods of collecting the fee are also permitted.

[0301] Furthermore, the fees collected by the early payment management system are received by the payment processing company that operates and manages the system. Additionally, if a usage fee for the early payment management system is required, the payment processing company may, for example, pay that fee from a portion of the collected fees.

[0302] [8. Period during which early payment can be applied] In the early payment management system 1 according to the first embodiment, the period during which a secondary contractor can apply for early payment is set to May 15th to May 29th in Figure 10. If the primary order information from the prime contractor is sent on May 1st, it is also possible to set the period to May 1st to May 29th, depending on the schedule for the primary contractor to input secondary order information and the amount of early payment available.

[0303] The period during which early payment applications can be submitted can be set in advance. Furthermore, the start date of this application period is conditional on, for example, the primary contractor sending the initial order information, the primary contractor entering the secondary order information, and the amount eligible for early payment being entered. Therefore, it is possible to set a fixed start date on a day when these conditions are definitely met, or to flexibly set the start date by determining the day on which the conditions are met.

[0304] On the other hand, the end date of this application period can be fixed, for example, May 29th, but it can also be set flexibly, for example, to the day after the prime contractor makes the final payment. In either case, the primary contractor's payment data and the secondary contractor's payment data are created after the application period has ended.

[0305] Furthermore, the period for applying for early payment can be set as a fixed date until June 10th, even after the prime contractor has made the final payment, as in the early payment management system 301 according to the fourth embodiment, and it is also possible to effectively extend it until June 29th.

[0306] As mentioned above, there are several possible ways to set the end date for the period during which early payment can be applied for, but in any case, the subcontractor has the opportunity to receive at least a portion of the remuneration before the prime contractor makes the final payment.

[0307] In the early payment management system 101 according to the second embodiment, the period during which applications for extra-early payment can be submitted can be set in advance. Furthermore, the start date of this application period is conditional on the primary contractor entering secondary order information and the amount eligible for early payment, so it can be fixed as a start date on a day when these conditions are definitely met, or it can be flexibly set as the start date after determining the day on which the conditions are met.

[0308] On the other hand, while the end date of this application period can be fixed as shown in Figure 12, it can also be set to a more flexible date, such as the day the prime contractor sends the initial order information.

[0309] The period during which early payment can be requested can be set in advance. Furthermore, the start date of this request period can be fixed as the date on which the condition that the prime contractor sends the initial order information is guaranteed to be met, or it can be set flexibly as the start date after determining the date on which the condition is met.

[0310] On the other hand, while the end date of this application period can be fixed as May 29th, it can also be set to a more flexible date, such as the day after the prime contractor makes the final payment. In either case, the primary and secondary contractor payment data will be created after the application period has ended.

[0311] In the early payment management system 201 according to the third embodiment, the period during which the primary contractor can apply for early payment can be set in advance. Furthermore, the start date of this application period is conditional on, for example, the primary order information being sent from the prime contractor, the secondary order information being entered by the primary contractor, and the amount of the early payment being entered. Therefore, it is possible to set a fixed start date on a day when these conditions are definitely met, or to determine the day on which the conditions are met and set that day as the start date.

[0312] On the other hand, while the end date of this application period can be fixed, for example, set as May 29th, it can also be set flexibly, for example, until the date the main contractor makes the final payment.

[0313] The setting of the period during which secondary subcontractors can apply for early payment is the same as in the early payment management system 1 of the first embodiment.

[0314] [9. Variations on setting the amount eligible for early payment requests related to extra-early payment requests] As explained in Figures 12 and 13, the early payment management system 101 according to the second embodiment of the present application allows a secondary contractor to submit an ultra-early payment application before submitting an early payment application, and the primary contractor pre-enters the amount available for early payment for that ultra-early payment application. The amount available for early payment thus entered is set as a common upper limit for both the early payment application and the ultra-early payment application.

[0315] Furthermore, if a secondary subcontractor receives the specified amount through an early payment application, that amount will be deducted from the amount eligible for early payment in the early payment application.

[0316] In the modified version described here, the amount available for early payment in the super early payment application and the amount available for early payment in the regular early payment application are managed separately. Furthermore, in this modified version, the primary contractor inputs the secondary order information only once after the prime contractor transmits the primary order information, similar to the early payment management system 1 of the first embodiment, and the super early payment application to the secondary contractor is made before receiving the secondary order information.

[0317] Therefore, the amount available for early payment in an early payment application is set by the early payment management system 101 to a certain percentage (e.g., 50%) of the performance (remuneration amount) of the secondary subcontractor in the month before last (March, which is outside the display range in the example in Figure 12). This percentage can be anything. With this setting, if the secondary subcontractor does not have performance in the month before last for work related to the same prime contractor or primary subcontractor, it will not be able to receive payment through the early payment application. In addition, the amount available for early payment in an early payment application may be determined based on the average amount over a specified period prior to the previous month (e.g., several months prior to the month before last), or set by the primary subcontractor, or by various other methods.

[0318] The ultra-early payment application allows for payment to the secondary subcontractor before the prime contractor has received the initial order information, i.e., before the secondary subcontractor's work performance is finalized. By determining the upper limit based on the aforementioned performance, appropriate risk management can be implemented. Furthermore, the primary subcontractor is relieved of the burden by not having to input secondary order information at an early stage.

[0319] Furthermore, in this modified example, the amount available for early payment in an early payment request is set by the primary contractor, similar to the early payment management system 1 in the first embodiment, so that the amount available for early payment in an ultra-early payment request and the amount available for early payment in an early payment request are set in different ways.

[0320] Furthermore, in the example shown in Figure 13, if this modified example (determining the upper limit based on the performance of the month before last) is applied, for example, the upper limit for the super early payment (May) will be 250,000 yen, which is 50% of the performance in April (500,000 yen) (the amount that can be paid early in the super early payment application); the upper limit for the super early payment (June) will be 375,000 yen, which is 50% of the performance in May (750,000 yen) (the amount that can be paid early in the super early payment application); and the upper limit for the super early payment (July) will be 75,000 yen, which is 50% of the performance in June (150,000 yen) (the amount that can be paid early in the super early payment application).

[0321] The early payment management system of this application has been described above with reference to the drawings, but the system configuration and processing timing (date) are merely illustrative examples, and the present invention is not limited to such illustrative configurations. The early payment management system according to the present invention can be configured with various other configurations and timings. [Explanation of symbols]

[0322] 1,101,201,301...Early Payment Management System 10... Primary contractor terminal 20...Secondary company terminal 30. Early Payment Management Server 50. Transaction management server

Claims

1. A management system comprising a management server for managing the payment of compensation to a third user when a second user who has received a job order from a first user places an order with a third user for the work related to the job ordered, The aforementioned management server A primary order information receiving means that receives primary order information from the first user, including the amount of compensation for work ordered by the first user to the second user, A secondary order information receiving means for receiving secondary order information regarding work ordered by the second user to the third user, A first payment request receiving means that receives a first payment request specifying at least a portion of the amount of remuneration for work ordered by the second user from the third user in response to operations performed on the computer used by the third user, The system includes a first value provision means that, upon receiving the first payment request, controls the provision of a value corresponding to the amount specified in the first payment request to the third user in a predetermined manner, under predetermined conditions, A management system characterized in that it can provide the third user with value corresponding to the amount specified in the first payment request before the value corresponding to the remuneration amount included in the primary order information is paid in a predetermined manner.

2. The management system according to claim 1, characterized in that, after the value corresponding to the reward amount included in the primary order information has been paid, the system provides the second user with a value corresponding to the amount obtained by subtracting the value provided to the third user by the first payment request from the reward amount included in the primary order information.

3. The system includes a third user information providing means that provides third user information to the second user after the value corresponding to the reward amount included in the primary order information has been paid, The aforementioned third user information is, Information on the value corresponding to the amount obtained by subtracting the value provided to the third user by the first payment request from the amount of compensation for the work ordered by the second user to the third user, The management system according to claim 1, characterized in that the information includes information relating to the value provided by the corresponding third user.

4. The management system according to claim 1, characterized in that the value provided to the third user, corresponding to the amount specified in the first payment request, may be the value after a predetermined fee has been deducted.

5. The management system according to claim 1, characterized in that the predetermined conditions for providing value corresponding to the amount specified in the first payment request include not exceeding a pre-set payable amount.

6. The management system according to claim 5, characterized in that the second user can set the payable amount using the computer used by the second user.

7. The management system according to claim 5, characterized in that the payable amount is set as an individual or common upper limit for each of the third users, or as a single upper limit for all the third users included in one secondary order information.

8. A second payment request receiving means that receives a second payment request specifying at least a portion of the amount of remuneration for work ordered by the first user to the second user, The system includes a second value provision means that, upon receiving the second payment request, controls the provision of value corresponding to the amount specified in the second payment request to the second user in a predetermined manner, under predetermined conditions, The management system according to claim 1, wherein the second value provision means enables the provision of value corresponding to the amount specified in the second payment request to the second user before the value corresponding to the remuneration amount included in the primary order information is paid in a predetermined manner.

9. The management system according to claim 8, characterized in that, after the value corresponding to the reward amount included in the primary order information has been paid, the system controls the provision of a value to the second user corresponding to the amount obtained by subtracting the value provided to the third user by the first payment request and the value provided to the second user by the second payment request from the reward amount included in the primary order information.

10. The management system according to claim 1, characterized in that, after the value corresponding to the reward amount included in the primary order information has been paid, the system controls the provision of a value corresponding to the amount obtained by subtracting the value provided to the third user by the first payment request from the reward amount included in the primary order information to the corresponding third user.

Images