Project matching and contract brokerage method according to cash flow prediction based on artificial intelligence

Abstract

According to one embodiment of the present disclosure, the present invention relates to a method of operation of a server that performs project matching and contract brokerage. The method of operation comprises the steps of: selecting a first contractor that matches at least one task constituting a project registered by a terminal of a first client; and generating contract information for a first contract between a first client and a first contractor. The step of generating contract information includes the steps of: setting a payment option for the first client regarding the task according to user input received through the terminal of the first client; and setting a payment receipt option for the first contractor regarding the task according to user input received through the terminal of the first contractor.

Description

Technology Field

[0001] The present disclosure relates to a method of operation for a server that performs project matching and contract brokerage between a client and a service provider, and more specifically, to a method of operation for a server that sets contract conditions related to payment between a client and a service provider and is capable of predicting cash flow based on multiple contracts. Background Technology

[0002] Recently, there has been an increasing trend of project execution utilizing various types of freelancers and contract workers in platform-based digital environments. Amid this trend, there is a rising demand for services that efficiently connect clients and contractors and support automated contract and payment processes. In particular, technology that enables clients to register projects consisting of multiple tasks and individually match suitable contractors for each task is gaining attention.

[0003] Traditionally, matching was conducted on general brokerage platforms by bulk matching service providers on an entire project basis or by simply listing job openings. This approach had limitations in accurately assigning personnel suitable for specific tasks and failed to support flexible settings for contract execution, commission processing, and payment settlement and receipt conditions. In particular, there was a lack of functionality to automatically generate or adjust contracts that reflected differing payment methods or settlement terms between the client and the service provider.

[0004] Furthermore, cash flow forecasting for platforms based on multiple contracts often relies on manual methods or simple statistical approaches, which has limited the ability to establish real-time operational strategies or manage risks. Consequently, there is a growing need for a precise cash flow forecasting function that considers payment and receipt options based on contract information. Prior art literature

[0005] Published Patent Application No. 10-2024-0170754 The problem to be solved

[0006] The present invention relates to a technology for performing project matching and contract brokerage, and more specifically, to a method of operation of a server capable of setting contract conditions related to payment between a client and a service provider and predicting cash flow based on multiple contracts.

[0007] The purposes of the present disclosure are not limited to those mentioned above, and other purposes and advantages of the present disclosure not mentioned may be understood from the following description and will be more clearly understood from the embodiments of the present disclosure. Furthermore, it will be readily apparent that the purposes and advantages of the present disclosure can be realized by the means and combinations thereof set forth in the claims. means of solving the problem

[0008] According to one embodiment of the present disclosure, a method of operation of a server performing project matching and contract brokerage comprises the steps of: selecting a first contractor that matches to at least one task constituting a project registered by a terminal of a first client; and generating contract information for a first contract between the first client and the first contractor. The step of generating contract information includes the steps of: setting a payment option of the first client for the task according to user input received through the terminal of the first client; and setting a payment receipt option of the first contractor for the task according to user input received through the terminal of the first contractor.

[0009] Here, the step of selecting a first service provider that matches at least one task may include: identifying the task suitability of each of the service providers based on task information for at least one task constituting a project registered by the terminal of the first client and service provider information for each of the service providers; transmitting information about a candidate service provider whose identified task suitability exceeds a threshold to the terminal of the first client; and selecting the first service provider among the candidate service providers based on user input received through the terminal of the first client.

[0010] Meanwhile, the step of generating the above contract information may generate contract information including the payment option of the first client and the payment receipt option of the first service provider.

[0011] At this time, the step of generating the contract information may include the step of calculating a first fee imposed on the first client for the first contract based on the payment option of the first client, and the step of calculating a second fee imposed on the first service provider for the first contract based on the payment receipt option of the first service provider.

[0012] Meanwhile, the method of operation of the above server may include the step of selecting a second service provider that matches at least one task constituting a project registered by the terminal of the second client, and the step of predicting cash flow based on payment options and payment receipt options included in contract information generated for each of the plurality of clients and the plurality of service providers.

[0013] At this time, the step of predicting cash flow can predict cash flow based on cash inflows and cash outflows for at least one future point in time by inputting contract information generated for each of the plurality of clients and the plurality of service providers into at least one artificial intelligence model that predicts cash flow.

[0014] Additionally, the method of operation of the server may include the steps of: deactivating at least one of a plurality of payment options based on the predicted cash flow; providing information regarding payment options excluding the deactivated payment option among the plurality of payment options to the terminal of the second client; and setting one of the payment options provided to the terminal of the second client as the payment option of the second client according to user input received through the terminal of the second client.

[0015] At this time, the method of operation of the server may include the steps of: deactivating at least one of a plurality of payment receiving options based on the predicted cash flow; providing information regarding payment receiving options excluding the deactivated payment receiving option among the plurality of payment receiving options to the terminal of the second service provider; and setting one of the payment receiving options provided to the terminal of the second service provider as the payment receiving option of the second service provider according to user input received through the terminal of the second service provider.

[0016] According to one embodiment of the present disclosure, a method of operation of a server performing project matching and contract brokerage comprises: a step of selecting a first contractor that matches to at least one task constituting a project registered by a terminal of a first client; and a step of generating contract information for a first contract between the first client and the first contractor. The step of generating contract information comprises: a step of predicting cash flow based on contract information generated for each of a plurality of clients and a plurality of contractors; a step of deactivating at least one of a plurality of payment options based on the predicted cash flow; a step of providing information on payment options among the plurality of payment options, excluding the deactivated payment option, to the terminal of the first client; and a step of setting one of the payment options provided to the terminal of the first client as the payment option of the first client according to user input received through the terminal of the first client.

[0017] According to one embodiment of the present disclosure, a method of operation of a server performing project matching and contract brokerage comprises: a step of selecting a first contractor that matches to at least one task constituting a project registered by a terminal of a first client; and a step of generating contract information for a first contract between the first client and the first contractor. The step of generating contract information comprises: a step of predicting cash flow based on contract information generated for each of a plurality of clients and a plurality of contractors; a step of deactivating at least one of a plurality of payment receiving options based on the predicted cash flow; a step of providing information on payment receiving options excluding the deactivated payment receiving option among the plurality of payment receiving options to the terminal of the first contractor; and a step of setting one of the payment receiving options provided to the terminal of the first contractor as the payment receiving option of the first contractor according to user input received through the terminal of the first contractor. Effects of the invention

[0018] According to the present invention, a server performing project matching and contract brokerage can flexibly respond to various transaction methods by setting payment and receipt options for each contract based on the input of the client and the service provider.

[0019] In addition, according to the present invention, financial risks can be identified and managed in advance by predicting the inflow and outflow of cash at a future point in time based on multiple contract information, and the financial soundness of the platform and the overall stability and sustainability of the system can be improved by disabling some payment / receipt options based on the predicted cash flow and providing only appropriate options to the user. Brief explanation of the drawing

[0020] FIG. 1 is a diagram illustrating the operation of a server communicating with a terminal according to one embodiment of the present disclosure. FIG. 2 is a flowchart illustrating the operation of a server generating contract information between a client and a service provider according to one embodiment of the present disclosure. FIG. 3 is a flowchart illustrating the operation of a server predicting cash flow and setting a client's payment option based thereon according to one embodiment of the present disclosure. FIG. 4 is a flowchart illustrating the operation of a server predicting cash flow and setting a service provider's payment receipt option based thereon, according to one embodiment of the present disclosure. FIG. 5 is a diagram illustrating the operation of a server communicating with an external server according to one embodiment of the present disclosure. FIG. 6 is a block diagram illustrating the configuration of a server according to one embodiment of the present disclosure. Specific details for implementing the invention

[0021] Before specifically describing the present disclosure, the method of description in the specification and drawings is described.

[0022] First, the terms used in this specification and claims have been selected based on general terms considering their functions in the various embodiments of this disclosure. However, these terms may vary depending on the intent of those skilled in the art, legal or technical interpretations, and the emergence of new technologies. Additionally, some terms have been arbitrarily selected by the applicant. Such terms may be interpreted according to the meanings defined in this specification; in the absence of specific definitions, they may be interpreted based on the overall content of this specification and common technical knowledge in the relevant field.

[0023] In addition, the same reference numbers or symbols described in each drawing attached to this specification represent parts or components that perform substantially the same function. For convenience of explanation and understanding, the same reference numbers or symbols are used to describe different embodiments. That is, even if components having the same reference number are all depicted in multiple drawings, the multiple drawings do not imply a single embodiment.

[0024] Additionally, in this specification and claims, terms including ordinal numbers, such as "first," "second," etc., may be used to distinguish between components. These ordinal numbers are used to distinguish identical or similar components from one another, and the meaning of the terms should not be limited by the use of such ordinal numbers. For example, the order of use or arrangement of components combined with such ordinal numbers should not be restricted by the number. If necessary, each ordinal number may be used interchangeably.

[0025] In this specification, singular expressions include plural expressions unless the context clearly indicates otherwise. In this application, terms such as "comprising" or "consisting of" are intended to specify the existence of the features, numbers, steps, actions, components, parts, or combinations thereof described in the specification, and should be understood as not precluding the existence or addition of one or more other features, numbers, steps, actions, components, parts, or combinations thereof.

[0026] In the embodiments of the present disclosure, terms such as "module," "unit," "part," etc. are used to refer to a component that performs at least one function or operation, and such component may be implemented in hardware or software, or in a combination of hardware and software. Additionally, a plurality of "modules," "units," "parts," etc. may be integrated into at least one module or chip and implemented as at least one processor, except where each needs to be implemented in specific individual hardware.

[0027] Furthermore, in the embodiments of the present disclosure, when a part is described as being connected to another part, this includes not only a direct connection but also an indirect connection through another medium. Additionally, the meaning that a part includes a certain component implies that, unless specifically stated otherwise, it does not exclude other components but may include additional components.

[0028] In the present disclosure, the expression “at least one of a, b, or c” may refer to “a”, “b”, “c”, “a and b”, “a and c”, “b and c”, “a, b, and c all”, or variations thereof.

[0029] The terms used in this disclosure have been selected to be as widely used and general as possible, taking into account their functions within this disclosure; however, these terms may vary depending on the intent of those skilled in the art, case law, the emergence of new technologies, etc. Additionally, in specific cases, terms have been selected at the applicant's discretion, and in such cases, their meanings will be described in detail in the relevant explanatory sections. Therefore, terms used in this disclosure should be defined not merely by their names, but based on their meanings and the overall content of this disclosure.

[0030] Singular expressions may include plural expressions unless the context clearly indicates otherwise. Terms used herein, including technical or scientific terms, may have the same meaning as generally understood by those skilled in the art as described in this specification. Additionally, terms including ordinal numbers, such as "first" or "second," used in this specification may be used to describe various components, but said components should not be limited by said terms. Such terms are used solely for the purpose of distinguishing one component from another.

[0031] When a part of a specification is described as "comprising" a certain component, this means that, unless specifically stated otherwise, it does not exclude other components but may include additional components. Furthermore, terms such as "part" or "module" as used in the specification refer to a unit that processes at least one function or operation, and this may be implemented in hardware or software, or as a combination of hardware and software.

[0032] Embodiments of the present disclosure are described below with reference to the attached drawings so that those skilled in the art can easily implement the invention. However, the present disclosure may be embodied in various different forms and is not limited to the embodiments described herein. Furthermore, in order to clearly explain the present disclosure in the drawings, parts unrelated to the explanation have been omitted, and similar parts throughout the specification are denoted by similar reference numerals.

[0033] FIG. 1 is a diagram illustrating the operation of a server communicating with a terminal according to one embodiment of the present disclosure.

[0034] The server (100) may be an entity that operates a platform providing project matching and contract brokerage services.

[0035] At this time, the server (100) can communicate with multiple terminals through at least one web page and / or application constituting the platform, and can provide at least one UI (User Interface) that includes data related to project matching and contract brokerage services (e.g., project information, portfolio, matching details, etc.) linked with each of the multiple terminals through at least one web page and / or application.

[0036] Meanwhile, the server (100) may be an FTP server (File Transfer Protocol Server), a web server, a database server, or a cloud server, but is not limited thereto. The server may perform one or more functions and operations, and may be implemented as a single device or distributed across multiple devices so that each function and operation is implemented.

[0037] Referring to FIG. 1, the server (100) can communicate with at least one client's terminal (200) and at least one service provider's terminal (300).

[0038] The client's terminal (200) may correspond to the terminal of the user entrusting the work.

[0039] For example, the client's terminal (200) can register information about a project consisting of at least one task to the server (100).

[0040] For example, the server (100) can obtain project information including task-specific types (e.g., video production, filming, planning, data editing, etc.), requests, deadlines, and contract prices, based on user input received through the client's terminal (200).

[0041] The service provider's terminal (300) may correspond to a user's terminal that performs work and receives payment for the work.

[0042] For example, the service provider's terminal (300) can register the service provider's portfolio information to the server (100).

[0043] For example, the server (100) can obtain portfolio information including result data of a task performed by a service provider, types of tasks that the service provider can perform, and evaluation data for the task performed by the service provider (e.g., whether the task client is satisfied), based on user input received through the service provider's terminal (300).

[0044] Meanwhile, the client's terminal (200) and the service provider's terminal (300) may each be a smartphone, tablet PC, laptop PC, desktop PC, etc., but are not limited thereto.

[0045] Accordingly, the server (100) can mediate a contract between a client and a service provider by matching a client who has registered project information and a service provider who has registered portfolio information with the server (100) to generate and register contract information.

[0046] As an additional embodiment, the server (100) may provide at least one first UI for monitoring the progress of each task constituting the project on the client's terminal.

[0047] For example, the server (100) may provide a first UI including service fees per task constituting the project, a payment schedule for service fees, whether the service fees have been paid, and details of the service provider's task performance. Additionally, the first UI may include UI items for inputting messages delivered to the service provider, such as requests for modification based on the service provider's task performance details, and UI items for modifying the service fees or the payment schedule for service fees.

[0048] In addition, the server (100) can provide a notification requesting payment of the service fee to the client's terminal according to the payment schedule of the service fee.

[0049] In addition, the server (100) may provide at least one second UI for inputting the progress status of each task matched with the service provider to the service provider's terminal.

[0050] For example, the server (100) may provide a second UI including a schedule for receiving service fees for each task matched with a service provider, whether the service fees have been received, details of the task's execution, and a request for modification from the client. At this time, the second UI may include UI items for inputting messages to be delivered to the client.

[0051] Accordingly, the client's terminal and the service provider's terminal can perform chatting by sending and receiving messages in real time through the first UI and the second UI, respectively.

[0052] As an additional example of implementation, the server (100) can predict the success probability of a project registered by the client's terminal.

[0053] For example, the server (100) can predict the probability of success of the project based on messages transmitted and received by the client's terminal and the service provider's terminal.

[0054] Specifically, the server (100) can identify the context for each message that is continuously transmitted and received for each task through natural language processing, calculate a performance ability score of a service provider according to the identified context, and identify the probability of success of the project based on the calculated performance ability score.

[0055] To this end, the server (100) may use a large language model capable of natural language understanding. For example, the server (100) may use a large language model stored in an external server connected to the server (100), or may use a large language model that has been acquired in advance and stored in the server (100).

[0056] Accordingly, the server (100) can input the messages continuously transmitted and received for each task into a large language model and, based on the output data, calculate the performance ability score of the service provider for the task according to the context of each continuously transmitted and received message.

[0057] For example, the server (100) can calculate a low performance capability score for a message transmitted from the service provider's terminal to the client's terminal if it is identified that the service provider did not understand the task.

[0058] Additionally, regarding the message transmitted from the client's terminal to the service provider's terminal, if the server (100) identifies that the client has repeatedly mentioned the occurrence of a problem regarding the same matter, it may calculate a low performance capability score.

[0059] Accordingly, the server (100) can calculate the average score of the service provider's performance ability score calculated for each task and identify the probability of success of the project based on the calculated average score. For example, the server (100) can identify the probability of success of the project as higher the average score.

[0060] Additionally, the server (100) may select a subcontractor that matches the unit task constituting the task (of the client) that is matched with the service provider's terminal.

[0061] For example, tasks constituting a content production project may include video production, image production, text production, etc., and unit tasks constituting the video production tasks may include filming, lighting, planning, editing, makeup, etc.

[0062] That is, the client-service relationship described below may correspond to a user who has registered a project and a user matched with at least one task constituting the project, or it may correspond to a user matched with a task and a user matched with at least one unit task constituting the task. If the client-service relationship corresponds to the latter, the project may be a term corresponding to the task, and the task may be a term corresponding to the unit task.

[0063] FIG. 2 is a flowchart illustrating the operation of a server generating contract information between a client and a service provider according to one embodiment of the present disclosure.

[0064] Referring to FIG. 2, the server (100) can select a first service provider that matches at least one task constituting a project registered by the terminal of the first client (S110).

[0065] In one embodiment, the server (100) can identify the task suitability of each service provider based on task information for at least one task constituting a project registered by the terminal of the first client and service provider information for each service provider.

[0066] Here, service providers include users who have registered portfolio information on the server (100) through each service provider's terminal, and service provider information may include portfolio information.

[0067] Specifically, the server (100) can identify the task suitability of each service provider in proportion to the similarity of the task information to the service provider information of each service provider.

[0068] To this end, the server (100) converts each of the task information and the service provider information into a vector value in a latent space through text embedding, and can identify the similarity of the task information to the service provider information based on the vector value in the latent space.

[0069] Specifically, the server (100) can identify the similarity of task information to service information based on the angle between the vector of task information and the vector of service information. In this case, the server (100) can identify a high similarity by determining that the smaller the angle between the vectors, the more similar the meaning of the text constituting each of the task information and service information is or the more frequently they appear together.

[0070] Additionally, the server (100) may identify the degree of relevance based on the distance between the vector of task information and the vector of service provider information. Here, the server (100) can calculate the distance between vectors based on the difference in vector values ​​by dimension, and can identify a high degree of similarity by determining that the closer the distance between vectors, the more similar the meaning of the text constituting each of the task information and service provider information is or the more frequently they appear together.

[0071] In this case, the server (100) can identify a service provider whose task suitability exceeds a threshold as a candidate service provider and transmit information about the candidate service provider to the terminal of the first client.

[0072] In addition, the server (100) may identify the task suitability of each of the service providers using at least one second artificial intelligence model that identifies the task suitability of the service providers.

[0073] The second artificial intelligence model may correspond to a model trained based on training data that includes the execution history of tasks according to contract information generated for each of the multiple clients and multiple service providers. The execution history of tasks may include whether the task was completed according to the contract information generated for each of the multiple clients and multiple service providers, and whether the client was satisfied with each task. In this case, the higher the probability that the task will be completed by the service provider and the higher the probability that the client will be satisfied, the higher the task fit may be identified.

[0074] Meanwhile, the second artificial intelligence model may be a model based on various learning algorithms such as linear regression, random forest, GBM (Gradient Boosting Machines), Siamese Neural Network, and Feedforward Neural Network, but is not limited thereto.

[0075] Accordingly, task information for at least one task constituting a project registered by the terminal of the first client and service provider information for each of the service providers are input into the second artificial intelligence model, and based on the output data, the task suitability of each of the service providers can be identified.

[0076] Here, the server (100) can select a first service provider among candidate service providers based on user input received through the terminal of the first client.

[0077] The server (100) can generate information about the first contract between the first client and the first service provider (S120).

[0078] In one embodiment, the server (100) provides information on a plurality of payment options to the terminal of the first client and can set the payment options of the first client for a task according to user input through the terminal of the first client.

[0079] A payment option refers to an option regarding the timing of payment by the First Client for the service fees paid by the First Client to the First Service Provider as the First Service Provider performs the task. For example, payment options may include immediate payment of contract information, short-term installment payments, long-term deferred payments, etc.

[0080] For example, based on the time when contract information is generated and registered on the terminal of the first client, immediate payment may be an option to pay the service fee within 30 days, short-term installment payment may be an option to pay the service fee between 1 month and 3 months, and long-term deferred payment may be an option to pay the service fee after 3 months, but is not limited thereto.

[0081] At this time, the server (100) can calculate a first fee to be charged to the first client's terminal based on the first client's payment option.

[0082] For example, the server (100) may waive the first fee if the payment option of the first client is immediate payment, calculate 2% of the service fee as the first fee if it is short-term installment payment, and calculate 5% of the service fee as the first fee if it is long-term deferred payment, and the ratio of the first fee applied to the service fee (e.g., 2%, 5%) is not limited thereto.

[0083] In addition, the server (100) may charge the brokerage fee for contract brokerage to the terminal of the first client.

[0084] Additionally, the server (100) provides information on multiple payment receipt options to the terminal of the first service provider and can set the payment receipt options of the first service provider for the task according to user input received through the terminal of the first service provider.

[0085] The payment receipt option refers to an option regarding the timing of the first service provider's receipt of the service fee paid by the first client to the first service provider as the first service provider performs the task. For example, the payment receipt option may include immediate receipt (advance receipt), installment receipt, deferred payment receipt, etc.

[0086] For example, based on the time when contract information is generated and registered on the terminal of the first service provider, immediate receipt may correspond to an option to receive the service fee immediately, installment receipt to an option to receive the service fee between one month and three months, and deferred receipt to an option to receive the service fee after three months, but is not limited thereto.

[0087] At this time, the server (100) can calculate a second fee to be charged to the terminal of the first service provider based on the payment receipt option of the first service provider.

[0088] For example, the server (100) may calculate 10% of the service fee as a second fee if the first service provider's payment receipt option is immediate receipt, 5% as a second fee if payment is received in installments, and waive the second fee if payment is received later, and the ratio of the second fee applied to the service fee (e.g., 5%, 10%) is not limited thereto.

[0089] In addition, the server (100) may charge the brokerage fee resulting from the contract brokerage to the terminal of the first service provider.

[0090] Accordingly, the server (100) can generate contract information for a first contract including at least one of the first client's payment receipt option and the first service provider's payment option, and register it for each of the first client's terminal and the first service provider's terminal.

[0091] In addition, the contract information regarding the first contract may include information regarding the type of task, the first client's requests for the task, the service fee for the task, the performance period of the task, the scheduled start date of the task, the scheduled end date of the task, the scheduled payment date of the first client, the scheduled payment date of the first service provider, etc.

[0092] Here, the first client's scheduled payment date is identified based on the first client's payment option and the scheduled start date of the task, and the first service provider's scheduled payment receipt date can be identified based on the first service provider's payment receipt option and the scheduled end date of the task.

[0093] In addition, when payment for the first contract is made by the terminal of the first client, the server (100) can add information about the time when payment was made to the contract information for the first contract.

[0094] Additionally, the server (100) may add the completion date of the task to the contract information for the first contract if it is identified that the task for the first contract has been completed based on user input received through the terminal of the first client or user input received through the terminal of the first service provider.

[0095] FIG. 3 is a flowchart illustrating the operation of a server predicting cash flow and setting a client's payment option based thereon according to one embodiment of the present disclosure.

[0096] In one embodiment, the server (100) may select a second service provider that matches at least one task constituting a project registered with the terminal of the second client.

[0097] Specifically, the server (100) can select a second service provider among the service providers based on information regarding a task according to project information registered by the terminal of the second client, by going through the same process as step S110.

[0098] Here, the server (100) can predict cash flow based on payment options and payment receipt options included in contract information generated for each of the multiple clients and multiple service providers (S210).

[0099] In one embodiment, the server (100) can predict cash flow based on cash inflows and cash outflows at least one future point in time by inputting contract information generated for each of a plurality of clients and a plurality of service providers into at least one first artificial intelligence model that predicts cash flow.

[0100] Here, the cash inflow may include at least one of the service fee and the first commission obtained from the client's terminal and the second commission obtained from the service provider's terminal, and the cash outflow may include, but is not limited to, the service fee distributed to the service provider's terminal.

[0101] The first artificial intelligence model may be a model trained based on training data including service fees for each of a plurality of contracts, the client's payment options and the service provider's payment receipt options, the actual time of payment of service fees by the client, and the actual time of receipt of service fees by the service provider, so as to identify cash flows according to cash inflows and cash outflows for at least one future point in time.

[0102] At this time, the first artificial intelligence model may be a model trained by the server (100) and used for predicting cash flow, or it may be a model that is pre-trained to predict cash flow and is acquired and used by the server (100).

[0103] Meanwhile, the first artificial intelligence model may correspond to a model trained based on learning algorithms such as GBM (Gradient Boosting Machines), RNN (Recurrent Neural Network), LSTM (Long Short-Term Memory), GRU (Gated Recurrent Unit), and Transformer, but is not limited thereto.

[0104] Here, the server (100) can send a risk alert to the terminal of the administrator managing the server (100) indicating that a deficit is predicted, based on the predicted cash flow, when the cash inflow is predicted to be less than the cash outflow for a future point in time that arrives within a certain period (e.g., 24 hours, one week, etc.).

[0105] The server (100) can disable at least one of the multiple payment options based on the predicted cash flow (S220).

[0106] In one embodiment, the server (100) may disable payment options related to long-term deferred payment if, based on predicted cash flow, a deficit is predicted for a future point in time that will arrive within a certain period (e.g., 24 hours, one week, etc.).

[0107] The server (100) can provide information on payment options to the terminal of the second client, excluding the payment options that are disabled among the multiple payment options (S230).

[0108] In one embodiment, the server (100) may provide a first UI item for each of the payment options, excluding the payment option that is disabled among the payment options, to the terminal of the second client.

[0109] The server (100) can set one of the payment options provided to the second client's terminal as the second client's payment option according to user input received through the second client's terminal (S240).

[0110] In one embodiment, the server (100) provides a first UI item for each payment option, excluding the payment option that is disabled, to the terminal of the second client, and can store the payment option corresponding to the first UI item selected by the second client as the payment option of the second client according to user input received through the terminal of the second client.

[0111] Meanwhile, the server (100) may disable the entire payment option to stop the contract mediation between the second client and the second service provider if a deficit is predicted for a future point in time to arrive within a certain period based on the predicted cash flow. In this case, since the payment option is not provided to the terminal of the second client, the payment option of the second client is not set, and thus contract information for the second contract may not be generated.

[0112] In an additional embodiment, the server (100) provides information on payment options, excluding deactivated payment options based on cash flow predicted by the first artificial intelligence model among a plurality of payment options, to the terminal of the first client, and can set the payment options of the first client among the payment options provided to the terminal of the first client according to user input received through the terminal of the first client.

[0113] FIG. 4 is a flowchart illustrating the operation of a server predicting cash flow and setting a service provider's payment receipt option based thereon, according to one embodiment of the present disclosure.

[0114] Referring to FIG. 4, the server (100) can disable at least one of a plurality of payment receiving options based on the cash flow predicted through the first artificial intelligence model (S310).

[0115] In one embodiment, the server (100) may disable payment options related to immediate receipt if a deficit is predicted for a future point in time to come within a certain period based on the predicted cash flow.

[0116] The server (100) can provide information on payment receiving options to the terminal of the second service provider, excluding the payment receiving option that is disabled among the multiple payment receiving options (S320).

[0117] In one embodiment, the server (100) may provide a second UI item for each of the payment receiving options, excluding the disabled payment receiving option among the multiple payment receiving options, to the terminal of the second service provider.

[0118] The server (100) can set one of the payment receiving options provided to the second service provider's terminal as the second service provider's payment receiving option according to user input received through the second service provider's terminal (S330).

[0119] In one embodiment, the server (100) provides a second UI item for each payment receiving option, excluding the payment receiving option that is disabled, to the terminal of the second service provider, and can store the payment receiving option corresponding to the second UI item selected by the second service provider as the payment receiving option of the second service provider according to user input received through the terminal of the second service provider.

[0120] Meanwhile, the server (100) may disable the entire payment receipt option to stop the contract mediation between the second client and the second service provider if a deficit is predicted for a future point in time to arrive within a certain period based on the predicted cash flow. In this case, since the payment receipt option is not provided to the terminal of the second service provider, the payment receipt option of the second service provider is not set, and thus contract information for the second contract may not be generated.

[0121] Additionally, the server (100) may disable the entire payment option to stop the contract mediation between the second client and the second service provider if a deficit is predicted for a future point in time to arrive within a certain period based on the predicted cash flow. In this case, since the payment option is not provided to the terminal of the second client, the payment option of the second client is not set, and thus contract information for the second contract may not be generated.

[0122] As an additional embodiment, the server (100) provides information on payment receiving options, excluding deactivated payment receiving options based on cash flow predicted by the first artificial intelligence model among a plurality of payment receiving options, to the terminal of the first service provider, and can set the payment receiving option of the first service provider among the payment receiving options provided to the terminal of the first service provider according to user input received through the terminal of the first service provider.

[0123] Meanwhile, the server (100) can identify the financial risk of the platform based on the predicted cash flow for each of the multiple future points in time through the first artificial intelligence model.

[0124] In one embodiment, the server (100) identifies a time interval between the current time and a time after a preset period (e.g., 7 days, 10 days, 30 days, etc.) as a target interval, and inputs contract information generated for each of the multiple clients and multiple service providers into the first artificial intelligence model and can predict cash flow for the target interval based on the output data.

[0125] At this time, the server (100) can identify, based on the cash flow predicted by the first artificial intelligence model, a first deficit section in which a deficit is continuously predicted (as the cash inflow is predicted to be less than the cash outflow) and a second deficit section in which the cumulative value of the cash inflow (calculated starting from the current point in time) is continuously predicted to be less than the cumulative value of the cash outflow.

[0126] For example, the cumulative value of cash inflows for a specific point in time within the target interval may correspond to the sum of predicted cash inflows between the current point in time and a specific point in time, and the cumulative value of cash outflows for a specific point in time may correspond to the sum of predicted cash outflows between the current point in time and a specific point in time.

[0127] Accordingly, the server (100) can identify financial risk based on the first ratio of the first deficit section in the target section and the second ratio of the second deficit section in the target section.

[0128] For example, the server (100) identifies the financial risk as higher as the first ratio and the second ratio are larger, and can set the degree to which each of the first ratio and the second ratio is reflected in the financial risk according to the amount of deficit change within each deficit interval. Here, the amount of deficit change refers to the degree to which the value of the cash inflow minus the cash outflow changes over time, and if the amount of deficit change increases, it may correspond to a state where the deficit increases, and if the amount of deficit change decreases, it may correspond to a state where the deficit decreases.

[0129] Specifically, the server (100) can identify the average value of the deficit change amount per unit time of the first deficit section as the first deficit change amount, and the average value of the deficit change amount per unit time of the second deficit section as the second deficit change amount.

[0130] At this time, when setting the first weight for determining the extent to which the first ratio is reflected in the financial risk and the second weight for determining the extent to which the second ratio is reflected in the financial risk, the server (100) may set the weight applied to the ratio corresponding to the deficit change amount having the larger value between the first deficit change amount and the second deficit change amount to have a larger value within the range where the sum of the first weight and the second weight maintains a constant value (e.g. 1), and may set the difference between the first weight and the second weight to increase as the difference between the first deficit change amount and the second deficit change amount increases.

[0131] For example, if the first deficit change amount is greater than the second deficit change amount, the server (100) sets the first weight to have a value greater than the second weight, and the greater the difference between the first deficit change amount and the second deficit change amount, the higher the first weight can be adjusted and the lower the second weight can be adjusted.

[0132] That is, the server (100) determines that the greater the change in deficit, the greater the cash outflow occurs than the cash inflow, and thus the shortage of funds intensifies; thus, it can set weights to identify the financial risk as higher the longer the period of large change in deficit.

[0133] Accordingly, the server (100) can identify financial risk by summing the value calculated by applying the first weight to the first ratio (e.g., multiplying) and the value calculated by applying the second weight to the second ratio.

[0134] At this time, if the financial risk level exceeds a preset threshold risk level (e.g., if the financial risk level has a value between 0 and 10, the threshold risk level may be preset to 7), the server (100) identifies that the financial status of the platform is unstable and disables at least one of the multiple payment options or disables at least one of the payment receiving options, and may disable at least one of the multiple payment options or disable at least one of the payment receiving options based on the reliability of each of the terminal of the second client and the terminal of the second service provider.

[0135] To this end, the server (100) can identify the reliability of each of the terminal of the second client and the terminal of the second service provider.

[0136] In one embodiment, the server (100) can identify the reliability of the request for the terminal of the second client based on the payment history of the terminal of the second client, and identify the reliability of the service for the terminal of the second service provider based on the service history of the terminal of the second service provider.

[0137] Specifically, the server (100) can identify the payment due date included in the contract information previously generated for the second client's terminal and the time when the second client's terminal made the payment (payment due date), and can identify the payment history in which the payment due date and payment due date related to the same contract are matched and recorded.

[0138] Accordingly, the server (100) can identify the reliability of the request as low as the number of times the second requester's terminal has paid the payment later than the scheduled payment date, based on the payment history.

[0139] Additionally, the server (100) can identify the scheduled end date and completion date of a task included in the contract information created in the past for the terminal of the second service provider, and can identify the service history in which the scheduled end date and completion date related to the same contract are matched and recorded.

[0140] Accordingly, the server (100) can identify the service reliability as low as the number of times the terminal of the second service provider completes a task later than the scheduled end date based on the service history.

[0141] At this time, the server (100) can disable at least one of the multiple payment receiving options if the request reliability is higher than the service reliability, and disable at least one of the multiple payment settlement options if the service reliability is higher than the request reliability.

[0142] Specifically, when the request reliability is higher than the service reliability, the server (100) can disable a payment receiving option having a lower rank than the first threshold rank among the multiple payment receiving options according to a preset priority for each of the multiple payment receiving options.

[0143] For example, if there are payment options such as immediate receipt, installment receipt, and deferred receipt, deferred receipt may be set as the first priority, installment receipt as the second priority, and immediate receipt as the third priority, and according to the first threshold priority set based on service reliability, the server (100) may disable the payment option for immediate receipt set as the third priority, and may also disable the payment option for installment receipt set as the second priority and the payment option for immediate receipt set as the third priority.

[0144] Here, the first threshold ranking can be set according to the service reliability, and the server (100) can set the first threshold ranking higher as the service reliability decreases, thereby limiting the range of payment receipt options selectable by the terminal of the second service provider.

[0145] Specifically, the server (100) can set a first threshold rank based on a threshold rank that matches each of a plurality of service reliability ranges, and the number of service reliability ranges can be set according to the number of payment receipt options.

[0146] For example, if there are three payment receipt options and the service reliability is identified within a range of 0 to 10, multiple service reliability ranges may be formed by dividing the range of 0 to 10 into three equal parts (e.g., a first range of less than 3.3, a second range of 3.3 or more and less than 6.6, and a third range of 6.6 or more), and the threshold rank that matches the low reliability range may correspond to a high rank (e.g., the threshold rank matched with the first range is rank 1, the threshold rank matched with the second range is rank 2, and the threshold rank matched with the third range is rank 3).

[0147] Accordingly, the server (100) can identify the threshold rank matched with the range in which service reliability is included as the first threshold rank.

[0148] For example, if the service reliability is identified as 5, the server (100) can identify the second rank, which is matched with the second range, as the first threshold rank, and accordingly, can disable the immediate receipt of the third rank corresponding to a priority lower than the second rank.

[0149] In this case, the server (100) may provide information on multiple payment options to the terminal of the second client and provide information on payment receiving options to the terminal of the second service provider, excluding the deactivated payment receiving option among the multiple payment receiving options.

[0150] Additionally, if the service reliability is higher than the request reliability, the server (100) may disable a payment option having a lower rank than the second threshold rank among the payment options, according to a preset priority for each of the payment options.

[0151] For example, if there are payment options such as immediate payment, short-term installment payment, and long-term deferred payment, immediate payment may be set as the first priority, short-term installment payment as the second priority, and long-term deferred payment as the third priority, and according to the second threshold priority set based on the reliability of the request, the server (100) may disable the payment option for long-term deferred payment set as the third priority, and may also disable the payment options for short-term installment payment set as the second priority and long-term deferred payment set as the third priority.

[0152] Here, the second threshold ranking can be set according to the request reliability, and the server (100) can set the second threshold ranking higher as the request reliability decreases, thereby limiting the range of payment options selectable by the terminal of the second requester.

[0153] Specifically, the server (100) can set a second threshold ranking based on a threshold ranking that matches each of the multiple request reliability ranges, and the number of request reliability ranges can be set according to the number of payment options.

[0154] For example, if there are three payment options and the request reliability is identified within the range of 0 to 10, the multiple request reliability ranges may be formed by dividing the range of 0 to 10 into three equal parts (e.g., a first range of less than 3.3, a second range of 3.3 or more and less than 6.6, and a third range of 6.6 or more), and the threshold rank that matches the low reliability range may correspond to a high rank (e.g., the threshold rank matched with the first range is rank 1, the threshold rank matched with the second range is rank 2, and the threshold rank matched with the third range is rank 3).

[0155] Accordingly, the server (100) can identify the threshold rank matched with the range in which the request reliability is included as the second threshold rank.

[0156] For example, if the request reliability is identified as 5, the server (100) can identify the second rank that has been matched with the second range as the second threshold rank, and accordingly, can disable the third rank long-term post-payment corresponding to a priority lower than the second rank.

[0157] In this case, the server (100) may provide information on payment options excluding deactivated payment options among multiple payment options to the terminal of the second client, and may provide information on multiple payment receiving options to the terminal of the second service provider.

[0158] Through this, the server (100) can reduce the possibility of contract brokerage failure due to deterioration in liquidity by managing cash flow from payment settlement and receipt in advance according to financial risk. In addition, the server (100) can evaluate the reliability of each based on the past history of the client and the service provider, and by imposing restrictions on the payment settlement or receipt method of the party with relatively lower reliability, it can prevent potential risks such as the client's payment delay or the service provider's dishonest performance of services in advance.

[0159] As an additional example, if the financial risk level exceeds a preset threshold risk level (e.g., if the financial risk level has a value between 0 and 10, the threshold risk level may be preset to 7), the server (100) may disable the full payment receipt option or the full payment receipt option to stop the contract mediation between the second client and the second service provider.

[0160] Meanwhile, if the financial risk level exceeds a preset threshold risk level (e.g., if the financial risk level has a value between 0 and 10, the threshold risk level may be preset to 7), the server (100) may disable the full payment receipt option and the full payment receipt option to stop the contract mediation between the second client and the second service provider.

[0161] FIG. 5 is a diagram illustrating the operation of a server communicating with an external server according to one embodiment of the present disclosure.

[0162] Referring to FIG. 5, the server (100) can communicate with an external server.

[0163] In one embodiment, the external server may correspond to a payment intermediary server for mediating the payment of costs.

[0164] In one embodiment, the payment intermediary server requests payment approval by transmitting payment information included in the payment request signal to the card company server, and when it receives a signal of payment approval for the request from the card company server, it can transmit a payment completion signal to the server (100) indicating that the payment according to the payment request signal has been completed.

[0165] In this case, when the time for payment of service fees according to the client's payment option arrives, the server (100) may request payment of service fees to the client's terminal.

[0166] At this time, the server (100) can receive a payment request signal including payment information (e.g., card information, payment amount, installment information, deposit details, etc.) from the client's terminal and transmit it to a payment intermediary server, and can receive a payment completion signal from an external server in accordance with the payment request signal transmitted to the payment intermediary server.

[0167] As an additional example of implementation, the external server may be a server managed by an agency performing tax-related duties (e.g., the National Tax Service).

[0168] In this case, if the server (100) identifies cash payment of the service fee or the first fee by the client's terminal, cash payment of the second fee by the service provider's terminal, etc., it can transmit payment information (e.g., information about the client, information about the service provider, payment (deposit) amount, payment (deposit) time, etc.) to an external server and obtain a tax invoice from the external server.

[0169] FIG. 6 is a block diagram illustrating the configuration of a server according to one embodiment of the present disclosure.

[0170] Referring to FIG. 6, the server (100) may include memory (110), a processor (120), and a communication interface (130).

[0171] The memory (110) stores various programs or data temporarily or non-temporarily and transmits the stored information to the processor upon the call of the processor (120). Additionally, the memory (110) can store various information required for the operation, processing, or control operation of the processor (120) in an electronic format.

[0172] The memory (110) may include, for example, at least one of a main memory and an auxiliary memory. The main memory may be implemented using a semiconductor storage medium such as ROM and / or RAM.

[0173] The processor (120) controls the overall operation of the electronic device. Specifically, the processor (120) is connected to the configuration of the electronic device including memory as described above, and can control the overall operation of the electronic device by executing at least one instruction stored in the memory as described above. In particular, the processor (120) can be implemented as a single processor as well as as a plurality of processors.

[0174] The processor (120) may be implemented in various ways. For example, one or more processors (120) may include one or more of a CPU (Central Processing Unit), GPU (Graphics Processing Unit), APU (Accelerated Processing Unit), MIC (Many Integrated Core), DSP (Digital Signal Processor), NPU (Neural Processing Unit), hardware accelerator, or machine learning accelerator. One or more processors (120) may control one or any combination of other components of an electronic device and may perform operations or data processing related to communication. One or more processors (120) may execute one or more programs or instructions stored in memory. For example, one or more processors (120) may perform a method according to one embodiment of the present disclosure by executing one or more instructions stored in memory.

[0175] In embodiments of the present disclosure, the processor (120) may mean a system-on-chip (SoC) in which one or more processors (120) and other electronic components are integrated, a single-core processor, a multi-core processor, or a core included in a single-core processor or a multi-core processor, wherein the core may be implemented as a CPU, GPU, APU, MIC, DSP, NPU, hardware accelerator, or machine learning accelerator, but the embodiments of the present disclosure are not limited thereto.

[0176] The communication interface (130) may include a wireless communication interface, a wired communication interface, or an input interface. The wireless communication interface may communicate with various external devices using wireless communication technology or mobile communication technology. Such wireless communication technologies may include, for example, Bluetooth, Bluetooth Low Energy, CAN communication, Wi-Fi, Wi-Fi Direct, ultrawide band (UWB), Zigbee, infrared data association (IrDA), or near field communication (NFC), and mobile communication technologies may include 3GPP, Wi-Max, LTE (Long Term Evolution), 5G, etc.

[0177] A wireless communication interface can be implemented using an antenna, a communication chip, a substrate, etc., capable of transmitting electromagnetic waves to the outside or receiving electromagnetic waves transmitted from the outside.

[0178] A wired communication interface can communicate with various devices based on a wired communication network. Here, the wired communication network can be implemented using physical cables, such as, for example, pair cables, coaxial cables, fiber optic cables, or Ethernet cables.

[0179] Depending on the embodiment, either the wireless communication interface or the wired communication interface may be omitted. Accordingly, the server (100) may include only the wireless communication interface or only the wired communication interface. In addition, the server (100) may be equipped with an integrated communication interface (130) that supports both wireless connection via the wireless communication interface and wired connection via the wired communication interface.

[0180] The server (100) is not limited to having one communication interface (130) that performs a communication connection in one manner, but may include multiple communication interfaces (130) that perform communication connections in multiple manners.

[0181] Meanwhile, the various embodiments described above may be implemented by combining two or more embodiments, provided that they do not conflict or contradict each other.

[0182] Specifically, each of the multiple operations, steps, and configurations for implementing one embodiment may be embodied in another embodiment, or the operations and steps of another embodiment may be followed by the last operation or step of one embodiment, but are not limited thereto.

[0183] Meanwhile, computer instructions or computer programs for performing processing operations in the various embodiments of the present disclosure described above may be stored in a non-transitory computer-readable medium. When such computer instructions or computer programs stored in the non-transitory computer-readable medium are executed by a processor of a specific device, the specific device described above performs processing operations according to the various embodiments described above.

[0184] A non-transient computer-readable medium refers to a medium that stores data semi-permanently and can be read by a device, unlike media that store data for a short period of time such as registers, caches, and memory. Specific examples of non-transient computer-readable media include CDs, DVDs, hard disks, Blu-ray discs, USBs, memory cards, and ROMs.

[0185] According to one embodiment, the method according to the various embodiments disclosed herein may be provided by being included in a computer program product. The computer program product may be traded between a seller and a buyer as a product. The computer program product may be distributed in the form of a device-readable storage medium (e.g., compact disc read-only memory (CD-ROM)), or distributed online (e.g., download or upload) through an application store (e.g., Play Store™) or directly between two user devices (e.g., smartphones). In the case of online distribution, at least a portion of the computer program product (e.g., downloadable app) may be temporarily stored or temporarily created on a device-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or a relay server.

[0186] Although preferred embodiments of the present disclosure have been illustrated and described above, the present disclosure is not limited to the specific embodiments described above. It is understood that various modifications can be made by those skilled in the art without departing from the essence of the present disclosure as claimed in the claims, and such modifications should not be understood individually from the technical spirit or perspective of the present disclosure. Explanation of the symbols

[0187] 100: Server 110: Memory 120: Processor 130: Communication Interface 200: Client's terminal 300: Service provider's terminal

Claims

Claim 1 A method of operation of a server performing project matching and contract brokerage comprises: a step of selecting a first contractor that matches at least one task constituting a project registered by a terminal of a first client; and a step of generating contract information for a first contract between the first client and the first contractor; wherein the step of generating contract information includes a step of setting the first client's payment option for the task according to user input received through the terminal of the first client; The method of operation of the server includes: a step of setting a payment receipt option of the first service provider for the task according to user input received through the terminal of the first service provider; and the method of operation of the server includes: a step of selecting a second service provider that matches at least one task constituting a project registered by the terminal of the second client; a step of predicting a cash flow according to a cash inflow and a cash outflow for at least one future point in time based on payment options and payment receipt options included in contract information generated for each of the plurality of clients and the plurality of service providers; a step of deactivating at least one of the plurality of payment options and the plurality of payment receipt options based on the predicted cash flow; a step of providing information on the plurality of payment options to the terminal of the second client, wherein if at least one of the plurality of payment options is deactivated, providing information on payment options excluding the deactivated payment option among the plurality of payment options; and a step of setting one of the payment options provided to the terminal of the second client as the payment option of the second client according to user input received through the terminal of the second client.A method of operation comprising: providing information on a plurality of payment receiving options to a terminal of the second service provider, wherein if at least one of the plurality of payment receiving options is deactivated, providing information on a payment receiving option excluding the deactivated payment receiving option among the plurality of payment receiving options; and setting one of the payment receiving options provided to the terminal of the second service provider as the payment receiving option of the second service provider according to user input received through the terminal of the second service provider. Claim 2 A method of operation according to claim 1, wherein the step of selecting a first service provider that matches at least one task comprises: identifying the task suitability of each of the service providers based on task information for at least one task constituting a project registered by the terminal of the first client and service provider information for each of the service providers; transmitting information about a candidate service provider whose identified task suitability exceeds a threshold to the terminal of the first client; and selecting the first service provider among the candidate service providers based on user input received through the terminal of the first client. Claim 3 In claim 1, the step of generating the contract information comprises generating contract information including the payment option of the first client and the payment receipt option of the first service provider. Claim 4 A method of operation according to claim 3, wherein the step of generating the contract information comprises: a step of calculating a first fee imposed on the first client for the first contract based on the payment option of the first client; and a step of calculating a second fee imposed on the first service provider for the first contract based on the payment receipt option of the first service provider. Claim 5 delete Claim 6 In claim 1, the step of predicting cash flow is a method of operation in which contract information generated for each of the plurality of clients and the plurality of service providers is input into at least one artificial intelligence model that predicts cash flow based on cash inflows and cash outflows for at least one future point in time. Claim 7 delete Claim 8 delete Claim 9 A method of operation of a server for performing project matching and contract brokerage, comprising the step of selecting a first contractor that matches at least one task constituting a project registered by a terminal of a first client; The method includes the step of generating contract information for a first contract between the first client and the first service provider; wherein the step of generating contract information comprises: predicting cash flow based on cash inflows and cash outflows for at least one future point in time, based on payment options and payment receipt options included in the contract information generated for each of the multiple clients and multiple service providers; deactivating at least one of the multiple payment options and multiple payment receipt options based on the predicted cash flow; providing information regarding the multiple payment options to the terminal of the first client, wherein if at least one of the multiple payment options is deactivated, providing information regarding payment options excluding the deactivated payment option among the multiple payment options; setting one of the payment options provided to the terminal of the first client as the payment option of the first client according to user input received through the terminal of the first client; providing information regarding the multiple payment receipt options to the terminal of the first service provider, wherein if at least one of the multiple payment receipt options is deactivated, the multiple payment receipt options A method of operation comprising: a step of providing information on payment receiving options excluding the above-mentioned deactivated payment receiving options; and a step of setting one of the payment receiving options provided to the terminal of the first service provider as the payment receiving option of the first service provider according to user input received through the terminal of the first service provider. Claim 10 delete

Images