KR20230013440A - Payment method and system for perfoming the same - Google Patents

Abstract

Disclosed are a payment method and a system performing the same. According to an embodiment, a payment method of a payment system related to an ordering project of an ordering agency comprises: a step of generating a virtual account to manage a payment of the ordering project; a step of generating a plurality of virtual codes which manage each payment of a plurality of payment objects receiving the payment related to the ordering project in the virtual account, and a plurality of virtual accounts managed by the plurality of virtual codes; a step of distributing and depositing the payment deposited in a first virtual account in at least one second virtual account based on at least one payment object and a payment amount for the payment object included in first billing information of the ordering project when the payment is deposited from the outside in the first virtual account of the plurality of virtual accounts; and a step of directly transferring the payment deposited in the at least second virtual account to each bank account of the at least one payment object. The plurality of payment objects can include at least one worker. The present invention facilitates safe payment.

Description

Payment method and system for performing it {PAYMENT METHOD AND SYSTEM FOR PERFOMING THE SAME}

The present disclosure relates to a payment method and a system for performing the same.

Recently, in order to solve chronic problems in the construction industry, such as overdue wages, it has become mandatory for public construction projects to be paid through an electronic payment system. The electronic payment system is a system to prevent the payment of workers' wages in arrears by restricting construction companies from arbitrarily withdrawing wages paid by the ordering organization.

On the other hand, even with the introduction of such an electronic payment system, there is a limit to solving chronic problems in the construction industry, such as account seizure of sub-businesses, opaque advance payment management, and fraudulent payment practices.

Embodiments are to provide a payment method and a system that can smoothly and transparently manage a money flow for safe payment.

According to an embodiment, a payment method of a system for paying a price related to a project ordered by an ordering organization includes generating a virtual account for managing the price of the ordered project, and related to the ordered project within the virtual account. Generating a plurality of virtual codes for managing the payment of each of a plurality of payment targets to receive payment and a plurality of virtual accounts managed by the plurality of virtual codes, a first virtual account among the plurality of virtual accounts When the money is deposited into the account from the outside, based on the at least one payment subject included in the first billing information of the ordered business and the payment amount for the payment subject, the money deposited into the first virtual account is transferred to at least one first billing information. It may include dispersively depositing in two virtual accounts, and directly transferring the money deposited in the at least one second virtual account to the bank account of each of the at least one payment target. The plurality of payment targets may include at least one worker.

The payment method may further include generating, in the virtual account, a fixed account for managing the price for which a payment target is specified, and an unconfirmed account for managing the payment for which the payment target is not specified. The plurality of virtual accounts and the plurality of virtual codes may be managed within the fixed account.

The distributed depositing may include, if the deposited amount is an advance payment including an unconfirmed amount to be paid, depositing the amount of the unconfirmed payment object among the advance payment into the unconfirmed account.

The payment method may include, when second billing information specifying a payment target for the payment deposited in the unconfirmed account is received, at least a part of the payment deposited in the unconfirmed account is transferred to the fixed account based on the second billing information. The method may further include transferring money to at least one third virtual account managed by .

The plurality of virtual accounts may be electronic accounts without bankbooks in which financial transactions by objects other than the system are restricted.

According to another embodiment, the system for processing payment in relation to the ordering business of the ordering organization includes a communication device that communicates with a claim registration system that manages claim information registered in relation to the ordering business by a plurality of payment targets; And a virtual account for managing the price of the ordered project, a plurality of virtual codes for managing the payment of each of the plurality of payment targets within the virtual account, and a plurality of virtual accounts managed by the plurality of virtual codes. and, when a payment is deposited into a first virtual account of the plurality of virtual accounts from the outside, the first virtual account based on at least one payment object and payment amount of the first claim information registered in the claim registration system. and a control device for distributing and depositing the money deposited in at least one second virtual account, and directly transferring the money deposited in the at least one second virtual account to the bank account of each of the at least one payment target. there is. The plurality of payment targets may include at least one worker.

The control device generates a fixed account for managing the price for which a payment subject is specified and an unconfirmed account for managing the price for which the payment subject is not specified in the virtual account, and the plurality of virtual accounts and the plurality of The virtual code can be managed within the fixed account.

If the deposited amount is an advance payment including an amount of unconfirmed payment subject, the control device may deposit the amount of unconfirmed payment object among the advance payment into the unconfirmed account.

The control device may, when second billing information specifying a payment target for the amount deposited in the unconfirmed account is registered in the claim registration system, at least some of the amount deposited in the unconfirmed account based on the second billing information. may be transferred to at least one third virtual account managed by the fixed account.

The plurality of virtual accounts may be electronic accounts without bankbooks in which financial transactions by objects other than the system are restricted.

According to another embodiment, the system for processing the payment in relation to the ordered project of the ordering organization manages the contract ledger of the ordered project, and collects information about the claim information input in relation to the ordered project by a plurality of payment targets. A claim registration system for managing adequacy verification and approval, and a virtual account for managing the price of the ordered project, a plurality of virtual codes for managing the payment of each of the plurality of payment targets within the virtual account, and the plurality of When a plurality of virtual accounts managed by a virtual code are created, and a payment is deposited into a first virtual account among the plurality of virtual accounts, the first billing information registered in the claim registration system in relation to the deposited payment Distributively deposits the amount deposited in the first virtual account into at least one second virtual account based on at least one payment target and payment amount of, and transfers the amount deposited into the at least one second virtual account to the at least one virtual account It can include a fund management system that transfers directly to each bank account of the payment target. The plurality of payment targets may include at least one worker.

The claim registration system, when the claim information of the first payment object is input, requests the at least one upper business operator of the first payment object to verify claim adequacy for the claim information of the first payment object, and the first payment object. Only when the adequacy of the claim for the claim information of the object is verified, the claim information of the first payment object may be registered and managed.

In the claim registration system, when claim information for claiming an advance payment is registered with a third payment object that is a parent operator of the second payment object, the payment for the advance payment is made by the fund management system. Until completion, the third payment object may not be charged for payment.

The fund management system may create a fixed account for managing the price for which a payment subject is specified and an unconfirmed account for managing the price for which the payment subject is not specified in the virtual account. The plurality of virtual accounts and the plurality of virtual codes may be managed within the fixed account.

If the deposited amount is an advance payment including an amount of unconfirmed payment subject, the money management system may deposit the amount of the unconfirmed payment subject among the advance payment into the unconfirmed account.

The fund management system, when second billing information specifying a payment target for the amount deposited in the unconfirmed account is registered in the claim registration system, at least among the amount deposited in the unconfirmed account based on the second claim information. A portion may be transferred to at least one third virtual account managed by the fixed account.

The plurality of virtual accounts may be electronic accounts without bankbooks in which financial transactions by objects other than the system are restricted.

According to the embodiments, there is an effect of solving problems such as account seizure of sub-businesses, opaque advance payment management, and fraudulent payment practices occurring in the current payment system, and enabling safe payment.

1 is an exemplary diagram for explaining a financial service system including a financial service providing server according to an embodiment.
Figure 2 schematically illustrates a payment method in the arrears prevention system according to an embodiment.
3 illustrates an example of managing billing details for payment in the arrears prevention system according to an embodiment.
4 illustrates an example of managing payment in arrears management system according to an embodiment.
5 illustrates another example of managing payment in arrears management system according to an embodiment.
6 illustrates another example of managing payment in arrears management system according to an embodiment.
7 illustrates another example of managing payment in arrears management system according to an embodiment.

Hereinafter, the embodiments disclosed in this specification will be described in detail with reference to the accompanying drawings, but the same or similar reference numerals are given to the same or similar components, and overlapping descriptions thereof will be omitted. The suffixes "module" and "unit" for components used in the following description are given or used together in consideration of ease of writing the specification, and do not have meanings or roles that are distinct from each other by themselves. In addition, in describing the embodiments disclosed in this specification, if it is determined that a detailed description of a related known technology may obscure the gist of the embodiment disclosed in this specification, the detailed description thereof will be omitted. In addition, the accompanying drawings are only for easy understanding of the embodiments disclosed in this specification, the technical idea disclosed in this specification is not limited by the accompanying drawings, and all changes included in the spirit and technical scope of the present invention , it should be understood to include equivalents or substitutes.

Terms including ordinal numbers, such as first and second, may be used to describe various components, but the components are not limited by the terms. Terms are only used to distinguish one component from another.

It is understood that when an element is referred to as being "connected" or "connected" to another element, it may be directly connected or connected to the other element, but other elements may exist in the middle. It should be. On the other hand, when an element is referred to as “directly connected” or “directly connected” to another element, it should be understood that no other element exists in the middle.

Singular expressions include plural expressions unless the context clearly dictates otherwise.

In this document, the terms "comprise" or "have" are intended to indicate that there is a feature, number, step, operation, component, part, or combination thereof described in the specification, but one or more other features It should be understood that the presence or addition of numbers, steps, operations, components, parts, or combinations thereof is not precluded.

In this document, the client means the business operator, organization, etc. that initially entrusted the necessary manufacturing, repair, construction, or service to another business. In addition, the original subcontractor (or principal contractor) is an enterprise that first receives (or contracts for) manufacturing, repair, construction, or service from the ordering party, and entrusts at least a part of the work entrusted from the ordering party to other entrepreneurs. it means. In addition, subcontractor refers to a subcontractor who has been entrusted (or contracted) with at least a part of the work entrusted by the original subcontractor from the original subcontractor. do. In the case of construction work, for example, the Railway Facilities Corporation entrusts the entire specific construction work to the first operator, the first operator entrusts part of the construction work to the second operator, and the second operator If part of the service is entrusted to a third operator, the Korea Rail Network Authority may be the orderer, the first operator may be the original supplier, the second operator may be the primary subcontractor, and the third operator may be the secondary subcontractor. In addition, in this document, depending on the supply-demand relationship, subcontractors (primary suppliers and subcontractors) may be named and used as 'upper business operators' and 'lower business operators'. For example, in the above supply and demand example of the Railway Facilities Corporation, the first operator is the upper operator of the second and third operators, the second and third operators are lower operators of the first operator, and the third operator is the second operator. can be a sub-business of

1 schematically illustrates a system for preventing late payments according to an embodiment.

Referring to FIG. 1 , a late payment prevention system 10 according to an embodiment may include a claim registration system 11 , an information relay system 12 , and a money management system 13 .

The claim registration system 11 is a system (or server) operated by an ordering organization, and can create and manage a contract ledger for each business (hereinafter referred to as 'ordering business') ordered by the ordering organization. The contract ledger is the contract information, claim information, and payment information between the ordering organization and the original supplier of the project, between the original supplier and the subcontractor, between the subcontractors having a contract relationship, or between the subcontractor and the worker/equipment contractor/material supplier. etc. may be included.

The claim registration system 11 may receive input of claim information from each payment subject receiving payment in relation to the ordering project of the ordering organization. In this document, 'subject of payment' refers to all creditors contracted to receive payment in relation to the project ordered by the ordering organization, and includes not only the original supplier and subcontractors, but also workers, equipment suppliers, and material suppliers. can

The claim registration system 11 can manage adequacy verification of claim information entered by each payment subject, claim approval, and registration in a contract ledger. The claim information entered by each payment ambassador is transmitted to the upper operator through the claim registration system 11, and can be finally registered in the contract ledger managed by the claim registration system 11 after the adequacy verification and claim approval of the upper operator. there is. Claim information finally registered in the claim registration system 11 may be transferred to the fund management system 13 to be described later and referred to for payment.

The fund management system 13 may manage the payment of the ordering organization. The fund management system 13 may issue a virtual account (hereinafter referred to as 'e-account') for managing the flow of funds related to the ordered project at the request of the ordering institution when the contract of the ordered project is finalized. In addition, the fund management system 13 can distinguish and manage a fixed account for managing the amount of money for which the payment target and payment amount is determined and an unconfirmed account for managing the payment for which the payment target and payment amount are not confirmed within the e account. there is.

The fund management system 13 issues a virtual code (hereinafter referred to as 'e-code') and a virtual account (hereinafter referred to as 'e-account') to payment targets receiving payment in relation to the ordered project, respectively. can The e account is an electronic account without a bankbook that has not gone through a new deposit subscription procedure. Transaction details and balances can be inquired by the corresponding payment target, but financial transactions such as withdrawal by other targets other than the fund management system 13 may be restricted. can The e code is a computer code for the fund management system 13 to classify and manage the amount to be paid for each payment subject. Each e code may be mapped to an e account of a corresponding payment target. The e account is used as a means to receive payment to the e code to which it is mapped, and the e code can be used to manage ledger data of the e account mapped to it.

The money management system 13 may include a communication device 131 , a control device 132 , and a database management system (DBMS) 133 .

The communication device 131 may perform a function of transmitting/receiving information between an external device and the money management system 13 . For example, the communication device 131 may communicate with the claim registration system 11 .

The DBMS 133 is a storage device for storing and managing ledger data managed in an e account. Within the e-account, it can be managed by dividing it into a confirmed account and an unconfirmed account according to whether the payment target and payment amount are confirmed. The DBMS 133 may include a fixed account ledger DB 133-1 that stores ledger data related to fixed accounts and an unconfirmed account ledger DB 133-2 that stores ledger data related to unconfirmed accounts. In the fixed account ledger DB 133-1, ledger data may be stored and managed for each e code. The ledger data managed by each e-code may include deposit and withdrawal details such as deposit and withdrawal dates, depositors, deposit amounts, recipients, and withdrawal amounts for the corresponding e-accounts, and additional information related to payment targets. As the additional information related to the payment object, the payment object may include account information (bank name, account number) of the actual receiving account to which the payment is finally paid. The recipient account to which the payment object is finally paid is a bank account issued by the bank to the payment object, and is a general bank account where financial transactions such as deposit and withdrawal are not restricted. The unconfirmed account ledger DB 133-2 may store and manage ledger data for an e account issued for an unconfirmed account. Payments for which the target of payment is not specified can be deposited and managed in the e-account of the unconfirmed account.

The control device 132 may perform a function of managing the money deposited from the ordering organization so that it can be directly paid to the receiving account of each payment target.

To this end, the control device 132 receives an e account for managing the cost of the ordering organization, e codes for managing payment for each payment subject within the corresponding e account, and deposits the payment for each e code on the e account, Alternatively, e-accounts may be issued to receive payments from unconfirmed accounts. Issuance of an e-code and an e-account corresponding thereto may be made based on a contract ledger registered in the claim registration system 11 . That is, the control device 132 may issue an e-code and an e-account corresponding thereto to all payment targets, including workers registered to receive payment in the contract ledger.

When the payment is deposited into the e account managed by the e account (eg, the original supplier's e account), the control device 132 determines the deposited amount based on the claim information received from the claim registration system 11. It can be distributed and deposited by e code of That is, the control device 132 may check the payment target and the payment amount for each payment target from the billing information, and based on this, distribute and transfer the amount deposited from the ordering institution to the e-account of each payment target. Then, the control device 132 may pay the amount by transferring the distributed deposited amount for each e-code of the fixed account to the receiving account of the corresponding payment target.

When the amount deposited in the e account managed by the e account includes the amount for which the payment target is undetermined, the control device 132 may separate the undetermined amount from the deposited amount and transfer the amount to the e account of the unconfirmed account. The control device 132 may check the amount of undetermined payment target among the deposited money based on the claim information registered in the claim registration system 11 .

When the payment target is confirmed for the amount deposited in the undetermined account through the claim registration system 11 later, the control device 132 can transfer the determined amount to the e account of the payment target managed by the fixed account. there is.

A method of managing payment by the control device 132 will be described in detail with reference to FIGS. 4 to 7 to be described later.

The information relay system 12 is connected to the claim registration system 11 and the asset management system 13 through a network, and can perform an information relay function between the claim registration system 11 and the asset management system 13 . The fund management system 13 manages payment based on e-code, not information that can directly identify the payment target, in order to prevent the payment to be paid to the lower business operator from being seized due to seizure of the upper business. can do. Therefore, when the information relay system 12 receives claim information, payment instructions, etc. from the claim registration system 11, the money management system 13 converts the received information so that it can be processed based on the e-code and delivers it. can In addition, when payment details and the like are received from the fund management system 13, the received information can be converted and transmitted so that the claim registration system 11 can process it based on the contract ledger.

2 schematically illustrates a payment method in the arrears prevention system 10 according to an embodiment. The payment method of FIG. 2 may be performed by the money management system 13 described with reference to FIG. 1 .

Referring to FIG. 2 , the fund management system 13 may create an e-account for managing the bill of the ordering organization (S10). In step S10, the fund management system 13 may additionally create a fixed account for managing funds for which a payment target is specified and an unconfirmed account for managing funds for which a payment target is not specified within the e account.

As the e-account is created, the fund management system 13 receives the e-codes for managing the payment for each payment object within the corresponding e-account, receives the payment for each e-code within the e-account, or pays for the unconfirmed account. e accounts for receiving deposits may be created (S11). In step S11, issuance of the e-code and the corresponding e-account may be made based on the contract ledger registered in the claim registration system 11. That is, the fund management system 13 may issue an e-code and an e-account corresponding thereto to all payment subjects registered to receive payment in the contract ledger.

If the ordering organization wants to pay the advance payment or advance payment, or if the original supplier or subcontractor wants to make an advance payment to its subordinate business operator, the ordering agency, the original supplier or subcontractor, manages the e-account of the fund management system 13 A payment to be paid may be deposited into an e account (eg, an e account of a primary supplier or a subcontractor). For this reason, the money management system 13 confirms that the money has been deposited from the outside (ordering agency, original supplier, or subcontractor) into the e account managed by the e account (S12), and the details of the deposit (depositor, date of deposit, amount of deposit) Etc.) together with information for notifying the payment of payment may be transmitted to the claim registration system 11 (S13). Upon receiving the deposit notification from the funds management system 13, the claim registration system 11 checks the claim information corresponding to the received deposit notification among the registered claims information, and sends a payment instruction together with the confirmed claim information to the funds management system. (13) can be sent.

When the money management system 13 receives a payment instruction from the claim registration system 11, based on the claim information received from the claim registration system 11, among the money deposited in the e account, the amount of undetermined payment target is included. It can be confirmed whether or not it has been done (S15). In addition, if the amount deposited in the e account includes an amount of undetermined payment target, the money management system 13 separates and deposits in the e account of the undetermined account as much as the amount of the undetermined payment target out of the amount deposited in the e account It can (S16).

The money management system 13 may distribute and deposit the money for which the payment subject is determined among the money deposited into the e account for each e code of the payment subject managed by the fixed account based on the billing information (S17). That is, the fund management system 13 may distribute and deposit the payment amount of each payment object to the e account of each payment object managed by the fixed account.

The amount of money distributed and deposited for each e code can then be transferred to the receiving account of the corresponding payment target by the asset management system 13 (S18). In step S18, the fund management system 13 checks the ledger data for each e-code from the fixed account ledger DB 133-1, confirms the receiving account of the payment target corresponding to each e-code, and transfers it to the confirmed receiving account. You can transfer the amount that is being distributed to each e-code. When payment is completed to the receiving account of the payment target, the fund management system 13 provides information on payment details (payment target, payment date, payment amount, etc.) ) may be transmitted to the claim registration system 11.

Meanwhile, the fund management system 13 continuously stores the ledger data stored in the fixed account ledger DB 133-1 or the unconfirmed account ledger DB 133-2 based on the deposit and withdrawal details of each e account generated during the payment process. can be updated with

Hereinafter, the payment method of the arrears prevention system 10 will be described in more detail with reference to FIGS. 3 to 7 .

3 illustrates an example of managing billing details for payment in the arrears prevention system 10 according to an embodiment. 3 illustrates a case in which the payment target and the payment amount are determined and the billing details for the payment are managed while the ordering project is in progress.

Referring to FIG. 3, workers/equipment makers/material makers access the claim registration system 11 through their terminals (not shown), and pay costs (labor costs, equipment charges, materials) for the work entrusted from the subcontractor. Billing information (3-1) for claiming a price, etc.) can be input to the claim registration system 11 (S21). Here, claim information (3-1) includes information on the subject of claim (subcontractor), subject of payment (worker, equipment supplier, or material supplier), receiving account information (bank name, account number, etc.), billing amount, etc. , can be created for each payment target. For example, in the case of claim information for claiming workers' labor costs, claim information may be separately created for each worker.

The claim registration system 11 may store the claim information 3-1 received through step S21 in a database (not shown) of the claim registration system 11. Thereafter, when the claim registration system 11 accesses the claim registration system 11 through the subcontractor's own system (hereinafter referred to as 'subcontractor system') (not shown), the registered claim information (3-1) Information on can be transmitted to the sewage service system (S22). The subcontractor who has confirmed the claim information (3-1) through the subcontractor system can verify the adequacy of the claim for the corresponding claim information (3-1). And, when the adequacy verification of the claim information (3-1) is completed, the subcontractor can transfer the claim approval for the corresponding claim information (3-1) to the claim registration system 11 through the subcontractor service system. The subcontractor can also enter the claim information (3-2) in the claim registration system (11) to claim his/her share of the cost for the work he/she has been entrusted to his/her upper business operator (original supplier) through the subcontractor system. Yes (S23). Here, the billing information 3-2 may include information about the subject of claim (primary supplier), subject of payment (subcontractor), receiving account information, billing amount, and the like.

The claim registration system 11 may store the claim information 3-2 received through step S23 in the database of the claim registration system 11. Then, when the claim registration system 11 accesses the claim registration system 11 through the original supplier's own system (hereinafter referred to as 'primary supplier system') (not shown), the subcontractor claims for the original supplier. Information on claim information may be transmitted to the original supplier system (S24). Here, the claim information requested to the original supplier includes both the claim information (3-2) of the subcontractor and the claim information (3-1) of the worker/equipment supplier/material supplier to the subcontractor. can

The original supplier who has confirmed the claim information (3-1, 3-2) charged to him or her through the original supplier system can verify the adequacy of the claim for the corresponding claim information (3-1, 3-2). And, when the adequacy verification of the claim information (3-1, 3-2) is completed, the original supplier can deliver the claim approval for the corresponding claim information (3-2) to the claim registration system 11 through the original supplier system. there is. The original supplier can also input claim information (3-3) for claiming the owner's share of expenses to the ordering organization into the claim registration system 11 through the original supplier system (S25). Here, the billing information (3-3) may include information on a payment target (original supplier), receiving account information, billing amount, and the like.

The claim registration system 11 may store the claim information 3-3 received through step S25 in the database of the claim registration system 11. The claim information (3-1, 3-2, 3-3) registered in the claim registration system 11 is the system of the ordering organization that placed the corresponding project (hereinafter referred to as the 'ordering agency system') (not shown) ) (S26), the claim adequacy can be finally verified by the ordering agency system. When the propriety verification for the claim information (3-1, 3-2, 3-3) is completed, the ordering agency system can transfer the claim approval to the claim registration system 11 to finally determine the claim information ( S27).

The claim information finally determined by the claim registration system 11 is registered in the contract ledger managed by the claim registration system 11 and transmitted to the fund management system 13 through the information relay system 12 (S28), It can be referenced to pay the price paid by the ordering organization to each payment target.

As described with reference to FIG. 3, the claim registration system 11 allows the party receiving the cost in relation to the project to be paid (the subject of payment) to directly register claim information, so that the claim is omitted or the payment is transferred to another person's account. Receipt may be prevented. In addition, the claim information entered at each stage is managed by the claim registration system 11, and the adequacy verification is performed by the upper operator for the claim information registered by the lower level operator, so that contract inquiry by payment target is possible and payment is made. adequacy can be monitored.

4 illustrates an example of managing payment in the arrears management system 10 according to an embodiment. The payment management method of FIG. 4 illustrates a case in which an advance payment is paid to payment targets based on billing information finally determined by the method described with reference to FIG. 3 .

Referring to FIG. 4, when the claim information on the completed payment is finally confirmed by the claim registration system 11 (see FIG. 3), the ordering organization manages the fund management system 13 in the representative e account (or the original supplier's e account). Account) can be deposited with the determined ready-made money (S31). At this time, the amount deposited by the ordering organization may correspond to the total payment amount of the claim information 3-1, 3-2, and 3-3 finally determined by the claim registration system 11. That is, the ordering organization can deposit the sum of all amounts to be paid to the original supplier, the subcontractor, and the worker/equipment supplier/material supplier to the representative e-account.

When ready-made money is deposited from the ordering organization, the fund management system 13 may notify the claim registration system 11 that the payment has been received, and receive a payment instruction together with claim information from the claim registration system 11 . Accordingly, the fund management system 13 may distribute and deposit the ready-made money deposited by the ordering organization by e-code of each payment target based on the claim information received from the claim registration system 11 (S32). That is, the fund management system 13 distributes the amount deposited by the ordering organization into payment amounts for each payment target (primary supplier, subcontractor, worker, material supplier, and equipment supplier), and pays the distributed amount to each It can be transferred to an e account managed by the target's e code.

Thereafter, the fund management system 13 may directly pay the payment to the corresponding payment target by transferring the deposited amount for each e code to the receiving account of each payment target (S33, S34, S35). When the money transfer is completed to the receiving account of each payment target, the fund management system 13 may map and store the details of the transfer for each e-code in the fixed account ledger DB 133-1. In addition, information on transfer details (payment information) may be transmitted to the claim registration system 11 to renew the contract ledger in the claim registration system 11 .

According to the description with reference to FIG. 4, instead of using a method in which the upper operator receives the payment and delivers it to the lower operator when the payment is made, the asset management system 13 automatically distributes the payment for each payment target and pays each payment A method of direct payment to the target is used. Therefore, the payment of the payment to the sub-businesses can be guaranteed because the completion money paid by the ordering organization can be safely delivered to each payment target. In addition, the e account used in the process of distributing the amount for each payment target is an account managed inside the asset management system 13, and the payment target does not require a complicated account issuance process and registration process to obtain the corresponding account. , the convenience of payment targets can be increased.

5 illustrates another example of managing payment in the arrears management system 10 according to an embodiment. The method for managing the price of FIG. 5 shows a case of managing the execution advance payment paid by the ordering organization. The execution advance payment is the first advance payment made by the ordering organization to the original supplier for the project to be ordered.

Referring to FIG. 5 , the original supplier registers claim information 4-1 through the claim registration system 11 and applies for approval to the ordering organization in order to claim the execution advance payment from the ordering organization (S41). Since the claim information (4-1) is the claim details for the execution advance payment, the payment target may not be determined for the remaining amount other than the original supplier's own share.

When the claim aptitude for the claim information 4-1 is verified, the ordering organization can finally determine the claim information 4-1 through the claim registration system 11. In addition, the ordering organization may deposit the execution advance payment corresponding to the finally confirmed claim information (4-1) into a representative e account (eg, the original supplier's e account) managed by the fund management system 10 ( S42).

When the execution advance payment is deposited from the ordering organization, the fund management system 13 notifies the claim registration system 11 that the payment has been received, and receives a payment instruction together with the claim information 4-1 from the claim registration system 11. can do. Accordingly, the fund management system 13 may distribute and deposit the deposited execution advance money into fixed accounts and unconfirmed accounts based on the claim information 4-1 transmitted from the claim registration system 11 (S43). That is, the fund management system 13 divides the execution advance deposited from the ordering institution into the amount for which the payment target is confirmed as the original supplier and the amount for which the payment target is not determined, and then the amount for which the payment target is confirmed as the original supplier is stored in the fixed account. deposited in the e-account managed by the original supplier, and the amount of undetermined payment target can be deposited in the e-account managed by the unconfirmed account.

After that, the amount deposited in the e-code of the primary supplier can be transferred directly to the receiving account of the primary supplier through the fund management system 13, and the amount deposited in the unconfirmed account is deposited in the unconfirmed account until the payment target is specified. status can be maintained.

6 shows another example of managing payment in the arrears management system 10 according to an embodiment. The payment management method of FIG. 6 illustrates a case in which a prepayment for use is paid after subcontracting between the original supplier and the subcontractor. The use advance payment is an advance payment that the original supplier requests and uses when necessary.

Referring to FIG. 6 , the subcontractor registers claim information 5-1 in the claim registration system 11 and requests approval of the claim from the original supplier through the claim registration system 11 (S51). Here, for the claim information (5-1), the subject of payment may not be determined for the remaining price other than the subcontractor's own share.

Upon receiving the claim information 5-1 of the subcontractor through the claim registration system 11, the original supplier can verify the adequacy of the claim for the claim information 5-1. If the adequacy of the claim for the claim information (5-1) is verified, the original supplier may transmit claim approval for the claim information (5-1) to the claim registration system (11). In addition, the original supplier may transmit the claim information (5-2) requesting the use advance payment to the ordering organization through the claim registration system 11 to request approval of the claim in order to pay the amount claimed by the subcontractor (S52). ). The ordering organization that has received the request for approval of the claim verifies the claim aptitude for the claim information (5-2), and when the claim appropriateness for the claim information (5-2) is verified, the claim information (5) through the claim registration system (11). -2) can be finalized. As the claim information 5-2 is finalized, the claim registration system 11 may transmit a payment instruction including the claim information 5-2 to the fund management system 13.

The fund management system 13 may transfer some of the amount of the execution down payment deposited in the unconfirmed account to the confirmed account based on the claim information 5-2 transmitted from the claim registration system 11 ( S53). That is, among the execution down payment deposited in the unconfirmed account, an amount determined to be paid to the subcontractor in the billing information (5-2) can be transferred to the e account of the subcontractor managed in the confirmed account. Among the billing details included in the billing information (5-2), the use advance payment to be paid to the original supplier is already transferred to the original supplier's e account when the ordering agency deposits the execution advance payment (see Fig. 5). A transfer may not be necessary.

When the transfer of money from the unconfirmed account to the confirmed account is completed, the fund management system 13 may transfer the amount deposited in the e accounts of the original supplier and the subcontractor in the confirmed account to the receiving accounts of the original supplier and the subcontractor, respectively (S54, S55). Even after that, the amount remaining in the unconfirmed account may remain deposited in the unconfirmed account until the target of payment is specified. When the money transfer is completed to the receiving account of the original supplier and the subcontractor, the fund management system 13 may map and store the details of the transfer in the fixed account ledger DB 133-1 with the e-code of the original supplier and the sewer. In addition, information on transfer details (payment information) may be transmitted to the claim registration system 11 to renew the contract ledger in the claim registration system 11 .

As described with reference to FIGS. 5 and 6, the fund management system 13 deposits and manages advance payments for which payment targets have not been determined in a separate undetermined account, and the payment recipient registers claim details for the advance payment to be paid Only after this is specified, the corresponding amount can be transferred to the fixed account and paid to the specified payment target. Therefore, it is possible to transparently and smoothly manage the advance payment paid in advance without specifying the payment target, and it is possible to avoid a situation in which the amount to be paid to the lower operator is seized due to the seizure of the upper operator.

7 illustrates another example of managing payment in the arrears management system 10 according to an embodiment. The payment management method of FIG. 7 shows a case of managing the advance payment when an advance payment is required before receiving the payment from the ordering organization.

Referring to FIG. 7, workers/equipment makers/material makers use claim information (6-1) to claim costs (labor costs, equipment charges, material charges, etc.) ) can be registered (S61).

The subcontractor who has confirmed the claim information 6-1 through the claim registration system 11 can verify the adequacy of the claim for the claim information 6-1. When the adequacy of the claim for the claim information 6-1 is verified, the subcontractor may transfer the claim approval for the claim information 6-1 to the claim registration system 11. In addition, in order to pay the amount claimed by the worker/equipment supplier/material supplier, the subcontractor delivers the claim information (6-2) requesting advance payment through the claim registration system (11) to the original supplier and makes an advance payment to the original supplier. can be requested (S62). In addition to the claim information 6-1, the claim information 6-2 may further include claim details of the subcontractor's share.

Upon receiving the claim information 6-2 for the advance payment from the subcontractor through the claim registration system 11, the original supplier can verify the adequacy of the claim information 6-2. When the claim adequacy of the claim information 6-2 is verified, the original supplier may transmit claim approval to the claim registration system 11. In addition, the primary supplier may deposit the advance payment requested by the subcontractor into the e account of the primary supplier managed by the e account of the fund management system 13 (S63). When paying the advance payment, the primary supplier may directly deposit his/her own funds into his/her e-account or apply for financial support so that the corresponding amount is deposited into his or her e-account.

When the deposit of the advance payment of the original supplier is confirmed, the fund management system 13 may notify the claim registration system 11 that the deposit of the advance payment has been confirmed. Thereafter, when the subcontractor who has confirmed the deposit of the advance payment through the claim registration system 11 requests a payment instruction from the claim registration system 11, the fund management system 13 receives a response from the claim registration system 11. It is possible to receive the claim information (6-2) together with the subcontractor's payment instruction (S64).

As the payment instruction is received, the fund management system 13 may distribute and deposit the deposited advance payment for each e-code of the payees managed by the fixed account based on the claim information (6-2) (S65). That is, the fund management system 13 identifies payment targets (workers, equipment manufacturers, material suppliers, and subcontractors) who have applied for advance payment from the claim information (6-2), and among the e accounts managed by the fixed account. The amount to be paid to each payment object can be transferred to the e account corresponding to the e code of the payment objects.

Thereafter, the fund management system 13 transfers the advance payments deposited in the e account of the subcontractor subcontractor (worker, equipment supplier, or material supplier) among the advance payments managed in the fixed account, to each payment target (worker, equipment supplier, or material supplier). The advance payment may be paid by direct transfer to the receiving account of the equipment manufacturer or material supplier) (S66). If the upper business operator does not prepay the advance payment requested by the lower business operator through the fund management system 13, later billing through the claim registration system 11 may not be allowed.

When the money transfer is completed to the receiving account of each payment target, the fund management system 13 may map and store the details of the transfer for each e-code in the fixed account ledger DB 133-1. In addition, information on transfer details (payment information) may be transmitted to the claim registration system 11 to renew the contract ledger in the claim registration system 11 .

According to the description with reference to FIG. 7, since the entire process from the deposit of the advance payment by the upper operator to the transfer to each payment target is managed and recorded by the fund management system 13, transparent management of the advance payment may be possible. there is. In addition, if the upper operator does not complete the payment for the advance payment claimed by the lower operator through the fund management system 13, the upper operator is not allowed to claim a new price through the claim registration system 11, You can avoid missing billing.

The foregoing embodiments can be implemented as computer readable codes on a recording medium on which programs are recorded. A computer-readable recording medium includes all types of recording devices in which data that can be read by a computer system is stored. Examples of computer-readable recording media include Hard Disk Drive (HDD), Solid State Disk (SSD), Silicon Disk Drive (SDD), ROM, RAM, CD-ROM, magnetic tape, floppy disk, and optical data storage devices. and the like, and also includes those implemented in the form of a carrier wave (eg, transmission over the Internet). Also, the computer may include a control device of the terminal. Accordingly, the above detailed description should not be construed as limiting in all respects and should be considered illustrative. The scope of the present invention should be determined by reasonable interpretation of the appended claims, and all changes within the equivalent scope of the present invention are included in the scope of the present invention.

Claims (17)

As a payment method for the system that pays for the project ordered by the ordering organization,
Creating a virtual account for managing the price of the ordered project;
Generating a plurality of virtual codes for managing the payment of each of a plurality of payment targets receiving payment in relation to the ordered business within the virtual account, and a plurality of virtual accounts managed by the plurality of virtual codes. ,
When a payment is deposited into a first virtual account of the plurality of virtual accounts from the outside, based on at least one payment target included in the first billing information of the order business and the payment amount for the payment target, the first virtual account Distributively depositing the money deposited in at least one second virtual account, and
Directly transferring the money deposited in the at least one second virtual account to the bank account of each of the at least one payment target,
The plurality of payment targets include at least one worker, payment method. According to claim 1,
Further comprising creating a fixed account for managing the payment for which the payment target is specified in the virtual account and an unconfirmed account for managing the payment for which the payment target is not specified,
Wherein the plurality of virtual accounts and the plurality of virtual codes are managed within the fixed account. According to claim 2,
The step of depositing the distributed,
If the deposited amount is an advance payment including an unconfirmed amount to be paid, depositing the amount of the unconfirmed amount among the advance payment in the unconfirmed account, the payment method. According to claim 3,
When second billing information specifying a payment target for the amount deposited in the unconfirmed account is received, at least one of the amounts deposited in the unconfirmed account is managed by the fixed account based on the second billing information. A payment method further comprising the step of transferring money to a third virtual account. According to claim 1,
The plurality of virtual accounts are bankbookless electronic accounts in which financial transactions by objects other than the system are restricted. As a system for processing payment in relation to the ordering project of the ordering organization,
A communication device that communicates with a claim registration system that manages claim information registered in relation to the ordered project by a plurality of payment targets, and
A virtual account for managing the price of the ordered project, a plurality of virtual codes for managing the payment of each of the plurality of payment targets within the virtual account, and a plurality of virtual accounts managed by the plurality of virtual codes and when payment is received from the outside in a first virtual account among the plurality of virtual accounts, the first virtual account is transferred to the first virtual account based on at least one payment object and payment amount of the first claim information registered in the claim registration system. A control device that distributes and deposits the deposited amount in at least one second virtual account and directly transfers the amount deposited in the at least one second virtual account to the at least one payment target bank account,
The plurality of payment targets include at least one worker, the system. According to claim 6,
The control device generates a fixed account for managing the price for which a payment subject is specified and an unconfirmed account for managing the price for which the payment subject is not specified in the virtual account,
The plurality of virtual accounts and the plurality of virtual codes are managed within the fixed account. According to claim 7,
Wherein the control device, if the deposited amount is an advance payment including an unconfirmed amount to be paid, deposits the amount of the unconfirmed payment object among the advance payments into the unconfirmed account. According to claim 8,
The control device may, when second billing information specifying a payment target for the amount deposited in the unconfirmed account is registered in the claim registration system, at least some of the amount deposited in the unconfirmed account based on the second billing information. to at least one third virtual account managed by the fixed account. According to claim 6,
The plurality of virtual accounts are bankbookless electronic accounts in which financial transactions by objects other than the system are restricted. As a system for processing payment in relation to the ordering project of the ordering organization,
A claim registration system that manages the contract ledger of the ordered project and manages the adequacy verification and approval of claim information input in relation to the ordered project by a plurality of payment targets, and
A virtual account for managing the price of the ordered project, a plurality of virtual codes for managing the payment of each of the plurality of payment targets within the virtual account, and a plurality of virtual accounts managed by the plurality of virtual codes and when the payment is deposited from the outside into the first virtual account of the plurality of virtual accounts, based on at least one payment target and payment amount of the first claim information registered in the claim registration system in relation to the deposited payment Money deposited in the first virtual account is distributed and deposited in at least one second virtual account, and funds deposited in the at least one second virtual account are directly transferred to the bank account of each of the at least one payment target. including the management system;
The plurality of payment targets include at least one worker, the system. According to claim 11,
The claim registration system, when the claim information of the first payment object is input, requests the at least one upper business operator of the first payment object to verify claim adequacy for the claim information of the first payment object, and the first payment object. A system that registers and manages the claim information of the first payment target only when the adequacy of claim for the claim information of the target is verified. According to claim 11,
In the claim registration system, when claim information for claiming an advance payment is registered with a third payment object that is a parent operator of the second payment object, the payment for the advance payment is made by the fund management system. A system that disallows billing of the third payment subject until complete. According to claim 11,
The fund management system creates a fixed account for managing the payment for which the payment target is specified in the virtual account and an unconfirmed account for managing the payment for which the payment target is not specified,
The plurality of virtual accounts and the plurality of virtual codes are managed within the fixed account. According to claim 14,
The money management system, if the deposited amount is an advance payment including an unconfirmed amount to be paid, depositing the amount of the unconfirmed payment object among the advance payments to the unconfirmed account. According to claim 15,
The fund management system, when second billing information specifying a payment target for the amount deposited in the unconfirmed account is registered in the claim registration system, at least among the amount deposited in the unconfirmed account based on the second claim information. and transfers a portion to at least one third virtual account managed by the fixed account. According to claim 16,
The plurality of virtual accounts are bankbookless electronic accounts in which financial transactions by objects other than the system are restricted.

Images