WO2001061532A1 - A system for managing inter-company settlement and the method therefor - Google Patents
A system for managing inter-company settlement and the method therefor Download PDFInfo
- Publication number
- WO2001061532A1 WO2001061532A1 PCT/KR2001/000219 KR0100219W WO0161532A1 WO 2001061532 A1 WO2001061532 A1 WO 2001061532A1 KR 0100219 W KR0100219 W KR 0100219W WO 0161532 A1 WO0161532 A1 WO 0161532A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- company
- purchaser
- information
- prepayment
- event
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/02—Banking, e.g. interest calculation or account maintenance
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
- G06Q20/102—Bill distribution or payments
Definitions
- the present invention relates to a system for managing inter-company settlement.
- the present invention relates to an inter-company settlement management system which enables seller companies and purchaser companies to conduct the sales amount collection procedure and the purchase price payment procedure more reliably by systematically implementing the overall settlement procedures conducted in between purchaser companies and seller companies on the bank on-line networks. Furthermore, the present invention relates to a method for managing inter-company settlement using the said inter-company settlement management system.
- the reason that the settlement relation between the seller company and the purchaser company is an important social issue is as follows. If an unreliable settlement system between the seller company and the purchaser company causes individual companies to go bankrupt, the basic economic order of the nation may be destroyed and the entire social order may be adversely affected, rendering a serious problem in the society.
- a seller company which has provided goods or services, conducts a series of procedures to claim the payment of sales amount against a purchaser company.
- most of the purchaser companies have preferred payment by bills to payment in cash because a purchaser company may manage the fund more flexibly if the payment is made through bills, compared with the payment in cash.
- the issuance date and the payment date are different in the bill payment method.
- a seller company who receives a bill from the purchaser company bears the risk of the purchaser company's failure to actually pay the purchase price. If such risk becomes a reality and the purchaser company which issued bills goes bankrupt without paying the purchase price, the seller company may incur a significant amount of damages.
- the purpose of the present invention is to enable a purchaser company to establish a settlement system against seller companies without incurring special financial strains, by making on-line prepayments of the purchase price on behalf of the purchaser company based upon the rights to the accounts receivable that the seller company had obtained from the purchaser company and provided as a collateral.
- Another purpose of the present invention is to preclude purchaser companies from using the conventional payment method by bills and, thus, to improve the reliability of the settlement system formed between the purchaser companies and seller companies. Consequently, unexpected damage or loss to seller companies may be minimized.
- Another purpose of the present invention is to implement the overall settlement procedures conducted between seller companies and purchaser companies systematically on the on-line networks. Through such implementation of the system on the on-line networks, it is intended that the seller companies and the purchaser company may conveniently conduct the sales amount collection procedure and the purchase price payment procedure without bearing unnecessary risks of theft or loss.
- Another purpose of the present invention is to improve the reliability of the settlement system between the purchaser company and the relevant seller companies, minimizing the economic loss caused by various companies' chain bankruptcy.
- Other purposes of the present invention will become apparent from the following detailed description and the attached drawings.
- the present invention implements an inter-company settlement management system comprising a D/B block, a D/B management server and a payment management server.
- the said D/B block comprises an authentication information database ("D/B") with a series of authentication information, a purchase price payment statement information D/B with the purchase price payment statement information, a loan prepayment information D/B with a series of loan prepayment information, a credit card purchase price prepayment information D/B with a series of information on the purchase price prepayment by credit card, and a registration information D/B with a series of registration information.
- D/B authentication information database
- the said D/B block comprises an authentication information database ("D/B") with a series of authentication information, a purchase price payment statement information D/B with the purchase price payment statement information, a loan prepayment information D/B with a series of loan prepayment information, a credit card purchase price prepayment information D/B with a series of information on the purchase price prepayment by credit card, and a registration information D/B with a series of
- the D/B block stores the said authentication information, purchase price payment statement information, loan prepayment information, credit card purchase price prepayment information or registration information, etc. selectively in the relevant field ofthe said D/B block, or extracts the said information from the D/B block.
- the said payment management server determines whether to store or extract the said authentication information, purchase price payment statement information, loan prepayment information, credit card purchase price prepayment information, etc. Additionally, if an event for management of the purchase price payment statement and an event of requesting the sales amount prepayment arises in telecommunication clients of a purchaser company and a seller company, the payment management server, in a state interfaced with the said telecommunication clients of the purchaser company and the seller company through the bank on-line network, analyzes the said various information, prepays the purchase price that a relevant purchaser company must pay to the seller company, and collects, on line, the amount equivalent to such pre-paid amount from the purchaser company after a predetermined period of time passes.
- Fig. 1 is a diagram illustrating the settlement relations between companies adopting the present invention.
- Fig. 2 is a diagram illustrating the inter-company settlement management system according to the present invention.
- Fig. 3 is a flow chart illustrating the sequence of the inter-company settlement method according to a preferred embodiment ofthe present invention.
- Fig. 4 and Fig. 5 are diagrams showing the initially displayed pages ofthe seller company's telecommunication client and the purchaser company's telecommunication client, according to a preferred embodiment ofthe present invention.
- Fig. 6 is a flow chart illustrating the sequence of the inter-company settlement method according to another preferred embodiment ofthe present invention.
- Fig. 7 and Fig. 8 are diagrams showing the messages displayed for the purchaser company's telecommunication client according to another preferred embodiment of the present invention.
- Fig. 9 is a flow chart illustrating the sequence of the inter-company settlement method according to still another preferred embodiment ofthe present invention.
- Fig. 10 and Fig. 11 are diagrams showing the messages displayed for the seller company's telecommunication client according to still another preferred embodiment of the present invention.
- Fig. 12 is a flow chart illustrating the sequence of the inter-company settlement method according to still another preferred embodiment ofthe present invention.
- Fig. 13a to Fig. 13d are diagrams illustrating the settlement states of the designated accounts of the purchaser company according to still another embodiment of the present invention.
- the inter-company settlement management system (100) is a part of the computer on-line network of a financial institution, for example, a bank (300), which may reliably manage the settlement relations between a purchaser company (400) and multiple seller companies (500).
- the present invention's inter-company settlement management system (100) which belongs to the computer on-line network of the bank (300) is composed largely of the D/B block (80), D/B management server (70), and the payment management server (10).
- the said D/B management server (70) stores the said authentication information, purchase price payment statement information, loan prepayment information, credit card purchase price prepayment information, operational information or registration information selectively in the relevant field of the D/B block (80), or extracts various data from the said authentication information D/B (81), the purchase price payment statement information D/B (82), the loan prepayment information D/B (83), the credit card purchase price prepayment information D/B (84), the operational information D/B (85), or the registration information D/B (86).
- the said D/B management server (70) not only stores or extracts various data but also conducts an intelligent function of effectively managing the various data without redundancy within the shortest period of time possible.
- the said payment management server (10) is interfaced with the telecommunication client (1) ofthe purchaser company (400) and the telecommunication client (2) ofthe seller company through a device such as an interface module (20).
- the telecommunication client (1) of the purchaser company (400), such as the purchaser company's computer (la) and the purchaser company's wired/wireless telephone (lb), and the telecommunication client (2) of the seller company (500), such as the seller company's computer (2a) and the seller company's wired wireless telephone (2b), are connected to the present invention's inter-company settlement management system (100) through the bank on-line network such as the wired/wireless Internet, automatic response system communication network, value added network, or public switched telephone network, etc.
- the bank on-line network such as the wired/wireless Internet, automatic response system communication network, value added network, or public switched telephone network, etc.
- the payment management server (10) systematically controls the D/B management server through the authentication module (30), the purchase price payment statement management module (40), the prepayment collection management module (50) and the operational information management module (60). In this way, the payment management server (10) determines whether to store or extract certain authentication information, purchase price payment statement information, loan prepayment information, credit card purchase price prepayment information, operational information or registration information.
- the payment management server (10) systematically analyzes the said authentication information, purchase price payment statement information, loan prepayment information, credit card purchase price prepayment information, operational information and registration information, and prepays on-line the purchase price that the purchaser company (400) must pay to the seller company (500). After a predetermined period of time passes, the said payment management system (10) collects, on line, the amount equivalent to the relevant prepayment from the purchaser company (400).
- the said authentication module (30) authenticates the purchaser company (400) or the seller company (500) which accesses the present invention's inter-company settlement management system (100) through the telecommunication client (1) of the purchaser company (400) or the telecommunication client (2) of the seller company (500).
- the authentication module (30) conducts said authentication function by checking the registration using the said authentication information D/B (81).
- the prepayment collection management module (50) manages the prepayment made to the seller company, by utilizing the said loan prepayment information D/B (83) and the credit card purchase price prepayment D/B (84).
- the account management module (90) is closely connected to the payment management server (10) as the said authentication module (30), the purchase price payment statement management module (40), the prepayment collection management module (50), and operational information management module (60) are similarly connected to the payment management server (10).
- the account management server (90) manages the designated account (92) of the system (100), the designated account (91) of the purchaser company (400), and the designated account (93) ofthe seller company (500).
- the purchaser company (400) which purchased certain goods or services and the seller company (500) which sold such goods or services access the present invention's inter-company settlement management system (100) through the said telecommunication client (1) ofthe purchaser company (400), for example, the computer (la) of the purchaser company, and through the telecommunication client (2) of the seller company (500), for example, the computer (2a) ofthe seller company.
- the purchaser company (400) and the seller company (500) may also use various telecommunication clients other than the computers (la or 2a).
- the wired/wireless communication device (lb) on the purchaser company or the wired/wireless communication device (2b) on the seller company may be selected for access to the inter-company settlement management system (100).
- the telecommunication relay station (200) transmits data from the purchaser company's wired/wireless communication device (lb) or the seller company's wired/wireless communication device (2b) to the interface module (20), and vice versa.
- the payment management server (10) determines whether there is a system access event from the purchaser company's computer (la) or the seller company's computer (2a) (Step SI).
- the payment management server (10) proceeds to conduct Step SI 1 as described below.
- the payment management server (10) extracts the relevant operational information from the operational information D/B (80) by using the operational information management module (60). Thereafter, using such operational information, the payment management server (10) generates an authentication request message and transmits the generated authentication request message to the relevant computer that has issued the system access event (Step S2).
- the payment management server (10) continuously checks with the interface module (20) to determine whether the purchaser company's computer (la) or the seller company's computer (2a) has transmitted the requested authentication information (Step S3). If it is determined that the purchaser company's computer (la) or the seller company's computer (2a) has not transmitted authentication information, the payment management server (10) considers that the relevant computer has not yet completed the input ofthe authentication information and goes to Step S4 to wait for the authentication information.
- the payment management server (10) immediately contacts the authentication module (30) to determine whether the purchaser company (400) or the seller company (500) which is presently connected to the system (100) through the relevant purchaser company's computer (la) or the seller company's computer (2a) has been registered with the system (Step S5).
- the purchaser company (400) in order to be authenticated as a registered company, the purchaser company (400) must have executed a separate purchaser company agreement with the bank (300). Such agreement may be, for example, a specific agreement or a credit card issuance agreement. Furthermore, the information regarding such agreement must have been recorded in the authentication information D/B (81). In order for the seller company (500) to be authenticated as a registered company, such seller company (500) must have executed a separate seller company agreement with the bank (300), which agreement being, for example, a loan agreement or an agreement for a credit card member company. The relevant information also must have been recorded in the authentication information D/B (81).
- the payment management server (10) using the operational information management module (60), collects the relevant registration information regarding the company from the registration information D/B (86) and then determines whether the connected company is the purchaser company (400) or the seller company (500) (Step S7).
- the payment management server (10) If the company is determined to be a purchaser company (400), the payment management server (10) generates an initial page for a purchaser company reflecting the relevant purchaser company's registration information. When such initial page is completed, the payment management server (10) transmits the initial page to the purchaser company's computer (Step S8). The purchaser company's computer (la) then immediately interprets the transmitted initial page (601) and displays the page as illustrated in Fig. 4, enabling the purchaser company to conveniently conduct the management of the purchase price payment statement. If the company accessing the system (100) is determined to be a seller company
- the payment management server (10) generates an initial page for a seller company reflecting the relevant seller company's registration information.
- the payment management server (10) transmits the initial page to the seller company's computer (2a) (Step S6a).
- the seller company's computer (2a) immediately interprets the said initial page designed for a seller company and displays the page as illustrated in Fig. 5.
- the seller company (500) may conveniently conduct the steps of requesting the prepayment ofthe sales amount.
- the purchase price payment statement means the statement setting forth the payments that the purchaser company (400) made to the seller company (500) for the purchased goods or services. If the purchaser company (400) transmits an "accounts receivable statement" as a purchase price payment statement, this means that the purchase price has been paid through the accounts receivable. If the purchaser company (400) transmits a "credit card statement" as a purchase price payment statement, this means that the purchase price has been paid by the company credit card.
- the said company credit card is a special card that the bank (300) using the present invention's settlement management system (100) issues to the purchaser company (400) which has entered into a "credit card issuance agreement.”
- the initial page (601) of the purchaser company's computer (la) contains the following items: "send the credit card statement" (602a); “view the sent credit card statements” (603a); “send the account receivable statement” (602b); “view the sent account receivable statements” (603b); “view the details of payment” (604); “view the details of delayed payment” (605); and “view the result ofthe process” (606).
- the purchaser company (400) may confirm or set any ofthe said items real time by clicking the relevant item on the page. The said items may be modified in accordance with the changing circumstances.
- the initial page (607) of the seller company's computer (2a) contains the following items: "view the requests for sales amount prepayment” (608); “view the details of sales” (609); “request for loan” (610a); and “request for credit card purchase” (610b).
- the seller company (500) may confirm or set any of the said items real time by clicking the relevant item on the page.
- the said items may also be modified in accordance with the changing circumstances.
- the seller company (500) may generate information regarding the request of loan by selecting the item, request for loan (610a).
- the information regarding the request of loan here means the information to request the sales amount prepayment, that the seller company (500), which has sold certain goods or provided certain services, sends to the bank (300) associated with the purchaser company (400) which "pays the purchase price for the goods or services through the accounts receivable.”
- the present invention's system (100) prepays the requested loan amount on behalf of the purchaser company (400) based upon the said "information regarding the request of loan.” Consequently, the seller company (500) may collect, in advance, the sales amount for the goods and services provided by the seller company.
- the seller company (500) may select the item, request for credit card purchase (610b), and generates the information on the request for purchase by the credit card.
- the information on the request for credit card purchase means the information to request the sales amount prepayment, that the seller company (500), which has sold certain goods or provided certain services, sent to the bank (300) associated with the purchaser company (400) which "pays the purchase price for the goods or services using the company's credit card.”
- the present invention's system (100) prepays the credit card purchase price on behalf of the purchaser company (400) based upon the said "information on the request for the credit card purchase.” Consequently, the seller company (500) may collect, in advance, the sales amount for the goods and services provided by the seller company.
- the payment management server (10) determines whether any event for managing the purchase price payment statement has occurred in the said purchaser company's computer (la) (Step S9).
- the payment management server (10) moves to Step S9a and maintains the "Wait" state.
- the payment management server (10) refers to the purchase price payment statement information transmitted from the purchaser company's computer (la) and proceeds quickly to conduct the purchase price payment statement management (Step SI 00).
- the payment management server determines whether there has been an event for requesting the sales amount prepayment from the said seller company's computer (2a) (Step S10).
- the payment management server (10) moves the flow to Step SlOa and maintains the "Wait” state.
- the seller company (500) clicks the item, "request for loan"
- the payment management server (10) refers to the sales amount prepayment information transmitted from the seller company's computer (2a) and proceeds quickly to conduct the sales amount prepayment (Step 200).
- Step SI 00 the said step for managing the purchase price payment statements
- the payment management server (10) determines whether there has been any event for sending the account receivable statement from the purchaser company's computer (la) (Step S101).
- the payment management server (10) uses the operational information management module (60) to generate the message for inputting the details regarding the credit card purchase.
- the payment management server sends the completed page for inputting the details regarding the credit card purchase to the purchaser company's computer (la) through the interface module (20) (Step SI 02).
- the purchaser company's computer (la) then quickly interprets the message for inputting the details regarding the credit card purchase (611) and displays it as illustrated in Fig. 7, providing the stable environment in which the purchaser company (400) may create the information regarding the credit card purchase.
- the payment management server (10) continually checks with the interface module (20) and determines whether the purchaser company's computer (la) has transmitted the information on the credit card purchase (Step SI 03).
- the payment management server (10) moves to Step SI 04 and maintains the waiting state.
- the payment management server (10) determines whether the said information on the credit card purchase is acceptable. For instance, it is determined whether the amount recorded in the said information as the amount to be paid is within the limit of the credit amount and whether the seller company recorded in the said information as the company to be paid is a registered seller company, etc. (Step SI 05).
- the payment management server (10) proceeds to conduct a step to send an error message to the purchaser company's computer (la) (Step SI 06).
- the payment management server (10) uses the operational information management module (60) to extract certain operational information which has been stored in the operational information D/B (85). Then, the payment management server (10), using such operational information, generates an error message such as "The amount inputted exceeds the limit of your credit amount. Please try again.” The generated error message is transmitted to the purchaser company's computer (la).
- the payment management server (10) proceeds to collect and store the said information on the credit card purchase (Step SI 07).
- the payment management server (10) transmits the information on the credit card purchase, which has been transmitted from the purchaser company's computer (la), to the purchase price payment statement management module (40).
- the purchase price payment statement management module (40) immediately upon receiving the information on the credit card purchase, transmits the said information to the D/B management server (70). In this manner, the information on the credit card purchase is collected and stored in the purchase price payment statement information D/B (82).
- Step S 101 if the purchaser company (400) clicks the item "send the account receivable statement" (602b) on the initial page (601) and if it is accordingly determined that an event for sending the account receivable statement has occurred, the payment management server (10) uses the operational information management module (60) to generate the message for inputting the details of the relevant accounts receivable. The payment management server (10) then transmits the completed message for inputting the details of accounts receivable to the purchaser company's computer (la) through the interface module (20) (Step S108).
- the purchaser company's computer (la) quickly interprets the message for inputting the details of accounts receivable (613), which has been sent by the payment management server (10), and then displays the message as illustrated in Fig. 8, providing the stable environment in which the purchaser company (400) may create the information on the account receivable statement.
- the payment management server (10) continually checks with the interface module (20) and determines whether the purchaser company's computer (la) has transmitted the information on the account receivable statement (Step SI 09). If the purchaser company (400) has not yet inputted the details regarding the accounts receivable and thus if the information on the account receivable statement has not yet been transmitted from the purchaser company's computer (la), the payment management server (10) moves to Step SI 10 and maintains the waiting state.
- the payment management server (10) determines whether the said information on the account receivable statement is acceptable. For instance, it is determined whether the amount recorded in the said information as the amount to be paid is within the pre-determined limit of the account receivable amount and whether the seller company recorded in the said information as the company to be paid is a registered seller company, etc. (Step S 111).
- the payment management server (10) proceeds to conduct a step to send an error message to the purchaser company's computer (la) (Step SI 12).
- the payment management server (10) uses the operational information management module (60) to extract certain operational information which has been stored in the operational information D/B (85). Then, the payment management server (10), using such operational information, generates an error message such as "The amount inputted exceeds the limit of account receivable amount. Please try again.” The generated error message is transmitted to the purchaser company's computer (la). In contrast, if the amount recorded in the information on the account receivable statement does not exceed the pre-designated limit ofthe account receivable amount and if the seller company recorded as the company to be paid is determined to be a registered seller company, the said information on the account receivable statement is deemed acceptable. Accordingly, the payment management server (10) proceeds to collect and store the said information on the account receivable statement (Step S 113).
- the payment management server (10) transmits the information on the account receivable statement, which has been transmitted from the purchaser company's computer (la), to the purchase price payment statement management module (40).
- the purchase price payment statement management module (40) immediately upon receiving the information on the account receivable statement, transmits the said information to the D/B management server (70). In this manner, the information on the account receivable statement is collected and stored in the purchase price payment
- Step S200 the payment management server (10), by continually checking with the interface module (20), determines whether there has occurred an event for requesting a loan based upon the account receivable statement from the seller company's computer (2a) (Step S201).
- the payment management server (10) uses the operational information management module (60) to generate the message for inputting the details regarding the credit card sales.
- the payment management server sends the completed page for inputting the details regarding the credit card sales to the seller company's computer (2a) through the interface module (20) (Step S202).
- the seller company's computer (2a) then quickly interprets the message for inputting the details regarding the credit card sales (615) and displays it as illustrated in Fig. 10, providing the stable environment in which the seller company (400) may create the information regarding the credit card sales.
- the payment management server (10) continually checks with the interface module (20) and determines whether the seller company's computer (2a) has transmitted the information on the credit card sales (Step S203).
- Step S204 If the seller company (500) has not yet inputted the details regarding the credit card sales and thus if the information on the credit card sales has not yet been transmitted from the seller company's computer (2a), the payment management server (10) moves to Step S204 and maintains the waiting state. In contrast, if the seller company (500) completed the input of the details regarding the credit card sales and clicked the item "send" (616) and, thus, it is determined that the seller company's computer (2a) has transmitted the information on the credit card sales, the payment management server (10) determines whether the amount recorded in the said information on the credit card sales as the amount to be paid does not exceed the balance ofthe pre-determined credit limit amount. (Step S205).
- the payment management server (10) proceeds to conduct a step to send an error message to the seller company's computer (2a) (Step S206).
- the payment management server (10) uses the operational information management module (60) to extract certain operational information which has been stored in the operational information D/B (85). Then, the payment management server (10), using such operational information, generates an error message such as "The amount inputted exceeds the balance of the credit limit amount. Please try again.” The generated error message is transmitted to the seller company's computer (2a).
- the payment management server (10) proceeds to make the prepayment of the "credit card sales amount" to the seller company (500) on behalf of the purchaser company (400) (Step S207).
- the payment management server (10) instructs the account management module (90) to make the prepayment of the "credit card sales amount.”
- the account management module (90) immediately upon receiving such instruction, transfers the specified amount of cash from the designated account of the system (92) to the designated account of the seller company (93). Accordingly, the seller company (500) which has sold goods or provided services to the purchaser company (400) may receive, on line, the prepayment of the "credit card sales amount" for "the provided goods or services" conveniently.
- Step S201 if the seller company (500) clicks the item "request for a loan" (610a) on the initial page (607) and if it is accordingly determined that there has occurred an event for requesting a loan based upon the account receivable statement from the seller company's computer (2a), the payment management server (10) uses the operational information management module (60) to generate the message for inputting the details of the loan request. The payment management server (10) then transmits the completed message for inputting the details ofthe loan request to the seller company's computer (2a) through the interface module (20) (Step S208).
- the seller company's computer (2a) quickly interprets the message for inputting the details of the loan request (617) which has been transmitted from the payment management server (10) and displays the message as illustrated in Fig. 11, providing the stable environment in which the seller company (500) may expeditiously proceed with the loan request.
- the payment management server (10) continually checks with the interface module (20) and determines whether the seller company's computer (2a) has transmitted the information on the loan request (Step S209). If the seller company (500) has not yet inputted the details regarding the loan request and thus if the information on the loan request has not yet been transmitted from the seller company's computer (2a), the payment management server (10) moves to Step S210 and maintains the waiting state.
- the payment management server (10) determines whether the amount recorded in the said information as the amount to be loaned is within the pre-determined limit of the credit balance amount. (Step S211). Here, if the requested loan amount recorded in the said information exceeds the pre-determined limit of the credit balance amount, the payment management server (10) proceeds to conduct a step to send an error message to the seller company's computer (2a) (Step S212).
- the payment management server (10) uses the operational information management module (60) to extract certain operational information which has been stored in the operational information D/B (85). Then, the payment management server (10), using such operational information, generates an error message such as "The amount inputted exceeds the limit of the credit balance amount. Please try again.” The generated error message is transmitted to the seller company's computer (2a).
- the payment management server (10) proceeds to make the prepayment of the "loan amount" to the seller company (500) on behalf of the purchaser company (400) (Step S213). In such an event, the payment management server (10) instructs the account management module (90) to make the prepayment of the "loan amount.”
- the account management module (90) immediately upon receiving such instruction, transfers the specified amount of cash from the designated account of the system (92) to the designated account of the seller company (93). Accordingly, the seller company (500) which has sold goods or provided services to the purchaser company (400) may receive, on line, the prepayment of the "loan sales amount" for "the provided goods or services” conveniently.
- the payment management server (10) uses the purchase price payment statement management module (40) to extract the purchase price payment statement information which was stored in the purchase price payment statement information D/B (82). The payment management server (10) then reviews the said purchase price payment statement information to determine whether the purchase price payment statement contains any item that is due on the present day (Step 11).
- the payment management server (10) checks with the designated account (91) ofthe purchaser company (400) to quickly pay the relevant purchase price of the purchaser company (Step S300). First, as illustrated in Fig. 12, the payment management server (10) controls the account management module (90) and analyzes in detail the designated account (91) of the purchaser company (90) which has issued the purchase price payment statement that is due on the present day (Step S301).
- the payment management server (10) then proceeds to determine whether the item due on the present day is subject to the "collection for the prepayment," a process in which the prepayment, which was made in accordance with the said steps S207 and
- the payment management server (10) immediately proceeds to conduct the "ordinary process” (Step S301b).
- the relevant seller company (500) related to the item due on the present day is an ordinary seller company (500) which did not proceed to "request the sales amount prepayment” and thus it is determined that the item due on the present day is not subject to the “collection ofthe prepayment” but is subject to the "ordinary process”
- the payment management server (10) immediately proceeds to conduct the "ordinary process” (Step S301b).
- Persons skilled in the relevant art may easily understand the ordinary process for payment. Therefore, we omitted the detailed illustration of the ordinary process in Fig. 12.
- the payment management server (10) determines whether the said item subject to the ordinary process is the item under the account receivable statement.
- the payment management server (10) deems that the said item subject to the ordinary process is an item under the credit card purchase statement. Then, the payment management server (10) checks whether the amount deposited in the designated account (91) of the purchaser company is not less than the "credit card purchase amount.”
- the payment management server (10) holds the purchaser company (400) which is the credit card debtor of the bank (300) in default. At the same time, on behalf of the purchaser company, the payment management server (10) pays to the seller company (500) the "credit card purchase amount" to which the seller company (500) is entitled to. In contrast, if it is determined that the amount deposited in the designated account (91) of the purchaser company is equal to or greater than the "credit card purchase amount," the payment management server (10) transfer the relevant amount from the purchaser company's designated account (91) to the seller company (500)'s designated account (93). Consequently, the seller company (500) receives the sales amount for the goods or services it has provided.
- the payment management server (10) checks whether the amount deposited in the purchaser company's designated account (91) is not less than the "amount on the account receivable statement.” Here, if the amount deposited in the purchaser company's designated account
- the payment management server (10) terminates the flow of process.
- the payment management server (10) transfers the relevant amount from the purchaser company's designated account (91) to the seller company (500)'s designated account (93).
- the seller company (500) receives the sales amount for the goods or services it has provided.
- step S301a if the item that is due on the present day is determined to be an item subject to the collection of the prepayment, the payment management server
- the payment management server (10) determines whether the amount deposited in the purchaser company's designated account (91) is not less than the "amount of the credit card purchase prepayment" (Step S303).
- the payment management server (10) collects the amount 100 deposited in the purchaser company's designated account (91) and, at the same time, holds the relevant purchaser company (400) which is a debtor to the bank (300) in default for the difference ofthe said amounts, 100 (Step S304).
- the payment management server (10) transmits to the operational module (60) the message which reads "Hold the purchaser company (400) in default.”
- the operational module immediately upon receiving the said message, changes the registration information regarding the said purchaser company, which has been stored in the registration information D/B (86). Thereafter, the said purchaser company (400) is characterized and managed as a company in default.
- the payment management server (10) proceeds to conduct the collection of the "amount of the credit card purchase prepayment" which was made by the bank (300) (Step S305). In this case, the payment management server (10) instructs the account management module (90) to collect the relevant amount from the amount deposited in the purchaser company's designated account (91).
- the account management module (90) transfers the relevant amount (for example, 50 out of 120) from the purchaser company's designated account (91) to the system's designated account (92). Consequently, the bank (300) may conveniently collect the amount prepaid in the "step of the credit card purchase prepayment.”
- the payment management server (10) proceeds to conduct the step to transfer, from the purchaser company's fund to the seller company's designated account (93), the balance of the sales amount to be paid to the seller company after subtracting the said "amount of the credit card purchase prepayment” (Step S309).
- the payment management server (10) instructs the account management module (90) to transfer the said relevant balance amount from the purchaser company's designated account (91).
- the account management module (90) transfers the "balance ofthe seller company (500)'s sales amount," 50 in this case, from the purchaser company (400)'s designated account (91) with the remaining fund 70 to the seller company's designated account (93). Consequently, the seller company (500) receives the entire sales amount for the goods or services it has provided.
- the payment management server (10) extracts the loan prepayment information through the prepayment collection management module (50). Then, using the said loan prepayment information, the payment management server (10) determines whether the amount deposited in the purchaser company's designated account (91) is not less than the amount of the loan prepayment (Step S306).
- the payment management server (10) collects the amount 100 deposited in the purchaser company's designated account (91) and, at the same time, holds the relevant seller company (500) which is a debtor to the bank (300) in default for the difference of the said amounts, 100 (Step S307).
- the payment management server (10) transmits to the operational module (60) the message which reads "Hold the seller company (400) in default.”
- the operational module immediately upon receiving the said message, changes the registration information regarding the said seller company (500), which has been stored in the registration information D/B (86). Thereafter, the said seller company (500) is characterized and managed as a company in default.
- the said seller company (500) is characterized and managed as a company in default.
- the payment management server (10) proceeds to conduct the collection of the "amount of the loan prepayment" which was made by the bank (300) (Step S308).
- the payment management server (10) instructs the account management module (90) to collect the relevant amount from the amount deposited in the purchaser company's designated account (91).
- the account management module (90) transfers the relevant amount (for example, 50 out of 120) from the purchaser company's designated account (91) to the system's designated account (92). Consequently, the bank (300) may conveniently collect the amount prepaid in the "step ofthe loan prepayment.”
- the payment management server (10) proceeds to conduct the step to transfer, from the purchaser company's fund to the seller company's designated account (93), the balance ofthe sales amount to be paid to the seller company after subtracting the said "amount ofthe loan prepayment” (Step S309).
- the payment management server (10) instructs the account management module (90) to transfer the said relevant balance amount from the purchaser company's designated account (91).
- the account management module (90) transfers the "balance ofthe seller company (500)'s sales amount," 50 in this case, from the purchaser company (400)'s designated account (91) with the remaining fund 70 to the seller company's designated account (93). Consequently, the seller company (500) receives the entire sales amount for the goods or services it has provided.
- the payment management server 10 coordinates the said authentication module (30), the purchase price payment statement management module (40), the prepayment collection management module (50), the operational information management module (60) and the account management module (90) so that the steps for the purchase price payment statement management or the steps for the sales amount prepayment management may be systematically conducted. Resultantly, the purchaser company and the seller companies may establish a reliable settlement relationship based upon the bank on-line network.
- the present invention enables a purchaser company to establish settlement relationships with seller companies without incurring special financial strains, by making on-line prepayments of the purchase price on behalf of the purchaser company based upon the rights to the accounts receivable that the seller company had obtained from the purchaser company and provided as a collateral.
- the present invention also precludes the purchaser company from using the conventional payment method by bills and, thus, may improve the reliability of the settlement system formed between the purchaser company and the seller companies. Consequently, unexpected damage or loss to the seller companies may be minimized.
- the present invention may implement the overall settlement procedures conducted between seller companies and purchaser companies systematically on the on-line networks.
- the seller companies and the purchaser company may conveniently conduct the sales amount collection procedure and the purchase price payment procedure without bearing unnecessary risks of theft or loss.
- the present invention improves the reliability of the settlement system between the purchaser company and the seller companies, minimizing the economic loss caused by various companies' chain bankruptcy.
- Preferred embodiments of the present invention have been specifically explained and illustrated in the above. However, it is apparent to persons skilled in the relevant art that the present invention may be modified in various manners and implemented accordingly.
Abstract
Description
Claims
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AU36134/01A AU3613401A (en) | 2000-02-15 | 2001-02-14 | A system for managing inter-company settlement and the method therefor |
EP01908390A EP1257932A1 (en) | 2000-02-15 | 2001-02-14 | A system for managing inter-company settlement and the method therefor |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR2000/7057 | 2000-02-15 | ||
KR20000007057 | 2000-02-15 | ||
KR2001/6687 | 2001-02-12 | ||
KR1020010006687A KR100542386B1 (en) | 2000-02-15 | 2001-02-12 | System and method for managing a payment relation between the enterprises |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2001061532A1 true WO2001061532A1 (en) | 2001-08-23 |
Family
ID=26637104
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2001/000219 WO2001061532A1 (en) | 2000-02-15 | 2001-02-14 | A system for managing inter-company settlement and the method therefor |
Country Status (7)
Country | Link |
---|---|
US (1) | US20030014362A1 (en) |
EP (1) | EP1257932A1 (en) |
JP (1) | JP2001283115A (en) |
KR (1) | KR100542386B1 (en) |
CN (1) | CN1423783A (en) |
AU (1) | AU3613401A (en) |
WO (1) | WO2001061532A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8341043B2 (en) | 2009-04-16 | 2012-12-25 | Westpac Bank Corporation | Dynamic prepayment risk management |
Families Citing this family (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2000079452A2 (en) * | 1999-06-18 | 2000-12-28 | Echarge Corporation | Method and apparatus for ordering goods, services and content over an internetwork using a virtual payment account |
KR20010099419A (en) * | 2001-09-26 | 2001-11-09 | 김형태 | Account settlement system for relationship of companys |
KR20020030047A (en) * | 2002-02-27 | 2002-04-22 | 김기태 | Enterprise for loan settlement line urgent civil official |
KR20030077250A (en) * | 2002-03-25 | 2003-10-01 | 오스크엔터테인먼트(주) | The payment method for Internet shopping mall and Internet service company by using OPA(Online Payment-in-Advance) system and DBMS. |
US20040039609A1 (en) * | 2002-08-22 | 2004-02-26 | Sarah Burkitt | System and method for payment of insurance premiums for vessels |
KR20040026194A (en) * | 2002-09-23 | 2004-03-30 | 주식회사 신한은행 | Method for managing a payment relation between the enterprises based on the on-line banking network |
US7291497B2 (en) * | 2003-09-11 | 2007-11-06 | Theranos, Inc. | Medical device for analyte monitoring and drug delivery |
KR100684967B1 (en) * | 2004-08-04 | 2007-02-20 | 전달용 | Method and system for providing payment services for sales price |
US20060264779A1 (en) | 2005-05-09 | 2006-11-23 | Kemp Timothy M | Fluidic medical devices and uses thereof |
WO2007102632A1 (en) * | 2006-03-07 | 2007-09-13 | I-Bliss Co., Ltd | System and method for electronic financial payment using esp |
US11287421B2 (en) | 2006-03-24 | 2022-03-29 | Labrador Diagnostics Llc | Systems and methods of sample processing and fluid control in a fluidic system |
US8741230B2 (en) * | 2006-03-24 | 2014-06-03 | Theranos, Inc. | Systems and methods of sample processing and fluid control in a fluidic system |
US8007999B2 (en) | 2006-05-10 | 2011-08-30 | Theranos, Inc. | Real-time detection of influenza virus |
US20080113391A1 (en) | 2006-11-14 | 2008-05-15 | Ian Gibbons | Detection and quantification of analytes in bodily fluids |
US8158430B1 (en) | 2007-08-06 | 2012-04-17 | Theranos, Inc. | Systems and methods of fluidic sample processing |
US8862448B2 (en) | 2009-10-19 | 2014-10-14 | Theranos, Inc. | Integrated health data capture and analysis system |
KR101173651B1 (en) | 2011-10-11 | 2012-08-13 | 김경록 | Deposits and installment savings granted with the stock switch right and the bankinng system for polysynthetically managing the deposits and installment savings and controlling method therefore |
US9792451B2 (en) | 2011-12-09 | 2017-10-17 | Echarge2 Corporation | System and methods for using cipher objects to protect data |
KR101491469B1 (en) * | 2012-06-13 | 2015-02-10 | 엠앤서비스 주식회사 | Loan service system based on accounts receivable in open market |
KR101790985B1 (en) | 2015-03-18 | 2017-10-27 | 윤영배 | Financial service method of dealings for which buying of credit card credit of sales and provision ahead of the buying price were used based on danger avoidance guarantee as collateral |
WO2017152037A1 (en) | 2016-03-04 | 2017-09-08 | 1Usf, Inc. | Systems and methods for media codecs and containers |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5671280A (en) * | 1995-08-30 | 1997-09-23 | Citibank, N.A. | System and method for commercial payments using trusted agents |
US5677955A (en) * | 1995-04-07 | 1997-10-14 | Financial Services Technology Consortium | Electronic funds transfer instruments |
JPH10207956A (en) * | 1997-01-27 | 1998-08-07 | Hironori Wakayama | Electronic settlement system |
US5920629A (en) * | 1994-04-28 | 1999-07-06 | Citibank, N.A. | Electronic-monetary system |
US5983208A (en) * | 1996-06-17 | 1999-11-09 | Verifone, Inc. | System, method and article of manufacture for handling transaction results in a gateway payment architecture utilizing a multichannel, extensible, flexible architecture |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4994964A (en) * | 1987-04-16 | 1991-02-19 | L & C Family Partnership | Transaction tracking data processing system |
US5504677A (en) * | 1992-10-15 | 1996-04-02 | Pollin; Robert E. | Automated payment system |
US5465206B1 (en) * | 1993-11-01 | 1998-04-21 | Visa Int Service Ass | Electronic bill pay system |
US5732400A (en) * | 1995-01-04 | 1998-03-24 | Citibank N.A. | System and method for a risk-based purchase of goods |
US6085168A (en) * | 1997-02-06 | 2000-07-04 | Fujitsu Limited | Electronic commerce settlement system |
JPH1196262A (en) * | 1997-09-25 | 1999-04-09 | The Asahi Bank Ltd | Flotation processing system of accounts receivable |
US6006207A (en) * | 1998-04-17 | 1999-12-21 | Mumick; Ravneet Kaur | System and method for loan prepayment discounts |
KR100328577B1 (en) * | 1999-04-16 | 2002-03-14 | 김용훈 | Method for paying a charge of goods |
KR19990084123A (en) * | 1999-09-15 | 1999-12-06 | 손성배 | Operation of an integrated logistics company that provides finance, logistics and information by conducting and acquiring sales and purchasing activities of member companies through an Internet electronic store. |
-
2001
- 2001-02-12 KR KR1020010006687A patent/KR100542386B1/en active IP Right Grant
- 2001-02-14 WO PCT/KR2001/000219 patent/WO2001061532A1/en not_active Application Discontinuation
- 2001-02-14 US US10/203,824 patent/US20030014362A1/en not_active Abandoned
- 2001-02-14 CN CN01808075A patent/CN1423783A/en active Pending
- 2001-02-14 AU AU36134/01A patent/AU3613401A/en not_active Abandoned
- 2001-02-14 EP EP01908390A patent/EP1257932A1/en not_active Withdrawn
- 2001-02-15 JP JP2001038848A patent/JP2001283115A/en active Pending
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5920629A (en) * | 1994-04-28 | 1999-07-06 | Citibank, N.A. | Electronic-monetary system |
US5677955A (en) * | 1995-04-07 | 1997-10-14 | Financial Services Technology Consortium | Electronic funds transfer instruments |
US5671280A (en) * | 1995-08-30 | 1997-09-23 | Citibank, N.A. | System and method for commercial payments using trusted agents |
US5983208A (en) * | 1996-06-17 | 1999-11-09 | Verifone, Inc. | System, method and article of manufacture for handling transaction results in a gateway payment architecture utilizing a multichannel, extensible, flexible architecture |
JPH10207956A (en) * | 1997-01-27 | 1998-08-07 | Hironori Wakayama | Electronic settlement system |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8341043B2 (en) | 2009-04-16 | 2012-12-25 | Westpac Bank Corporation | Dynamic prepayment risk management |
Also Published As
Publication number | Publication date |
---|---|
EP1257932A1 (en) | 2002-11-20 |
AU3613401A (en) | 2001-08-27 |
KR100542386B1 (en) | 2006-01-10 |
JP2001283115A (en) | 2001-10-12 |
KR20010082133A (en) | 2001-08-29 |
CN1423783A (en) | 2003-06-11 |
US20030014362A1 (en) | 2003-01-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7783539B2 (en) | Derivative currency-exchange transactions | |
US20030014362A1 (en) | System for managing inter-company settlement and the method therefor | |
US8015085B2 (en) | System for distributing funds | |
US7797237B2 (en) | Electronic financial transaction system and method providing real-time authentication service through wire/wireless communication network | |
US20080270246A1 (en) | Global electronic payment system | |
WO2001055983A1 (en) | Banking system with enhanced utility | |
KR100855903B1 (en) | Service system and method for safely buying and selling immovable property by internet | |
JP2002245251A (en) | On-line securities exchange server, account management server, on-line securities exchange system, purchase order settlement of accounts method, purchase order settlement of accounts program, and recording medium | |
EP1325437A1 (en) | Method and device for bill account by on-line certified contract | |
US20030041024A1 (en) | System for managing inter-company settlement and the method therefor | |
JP2002074000A (en) | Funds account settlement processing support system through information communication network | |
KR20000036837A (en) | Method of internet giro service | |
KR20020009761A (en) | Mother account exchange system and method of exchanging an account using such system | |
KR100462699B1 (en) | Banking System Using a Cyber Bank | |
KR20020088740A (en) | Methods of remittance and request mediation service using a screen scraping program | |
JP2003044682A (en) | Remittance system, remittance method, account management device, wallet deposit and withdrawal and credit management system and computer software | |
KR20020078319A (en) | Method for providing Electronic Pocket Service using Instant Messenger | |
KR20070014726A (en) | System for guiding a encashment process of the trade receivables which contents provider possesses | |
KR20020021564A (en) | Real Estate System Using Escrow Service of Bank on Internet | |
GB2363646A (en) | Banking operation system | |
US20180039515A1 (en) | Systems and methods for identifying similarities in instructional data and creating consolidated records thereof | |
KR20000063898A (en) | Electronic settlement method through the computer network and apparatus therefor, and computer-readable medium recording the method | |
US20060100959A1 (en) | Methods and systems for implementing derivative transactions | |
KR20050030786A (en) | Real time payment method using virtual account | |
KR20070088843A (en) | Integrated settlement method using sms, escrow account and virtual account and recording medium thereof |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS KE KG KP KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2001908390 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 10203824 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 018080758 Country of ref document: CN |
|
WWP | Wipo information: published in national office |
Ref document number: 2001908390 Country of ref document: EP |
|
REG | Reference to national code |
Ref country code: DE Ref legal event code: 8642 Ref country code: DE Ref legal event code: 8642 |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: 2001908390 Country of ref document: EP |