JP2005092892A - Payment securing system and method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a payment securing system, its method and its program for eliminating the payment collection risk of each enterprise in chain transactions carried out by a plurality of enterprises. <P>SOLUTION: A payment securing server has: a distribution setting data table 16a created by storing distribution condition data including price rate data or price data, and payment term data including payment dates, direction data reception or credits above a certain amount; a first account data table 14a for storing received amounts from final payment enterprises; a means for determining whether credits correspond to the payment terms data stored in the data table 16a or not; a means for determining a distribution amount to each reception enterprise from a credit amount based on the distribution terms data; and a second account data table 14c with disbursement information data stored. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to a system for payment for transactions through a plurality of companies, and more particularly, to a system for preserving funds collected by each company involved in transactions.

FIG. 7 is a diagram schematically showing a conventional chain transaction involving a plurality of companies A, B, C, D, and E. Parts 1, 2, 3, and 4 are delivered from parts manufacturer A to B, B to C, C to D, and D to final product manufacturer E, respectively. For example, the parts manufacturers B to D are processing manufacturers and sales agents. Due to this delivery process, there is a receivable-liability relationship between each company that deals directly. Hereinafter, such a chain transaction is referred to as a “chain transaction”. In the payment process based on this debt and liability relationship, the price 100 (arbitrary unit) from the final product manufacturer E to the parts manufacturer D, the price 90 from D to C, the price 80 from C to B, and the price 70 from B to A Will be paid. If the payment process is carried out smoothly, the inter-company receivables and payables will be dissolved.
JP 2000-76369 A JP 2002-83249 A JP 2002-150159 A JP 2002-123635 A

  However, in chain transactions involving multiple companies, even if the ultimate buyer's creditworthiness is high, there is always a risk associated with collection of money if a company with low creditworthiness is present in the middle of the chain. To do. For example, in FIG. 7, when the part maker D cannot pay, the part makers C, B, and A may not be able to collect the price.

  In order to avoid such a risk, for example, component manufacturer C inserts a security deposit for credit enhancement in order to purchase from component manufacturer B. If there is no room, it will be difficult to purchase. On the other hand, B, which has received a deposit, has a large burden when interest payment on the deposit is required.

  In this way, manufacturers on the product supply side struggle with credit management of manufacturers and sales agents who are suppliers, but on the other hand, there are cases where they want to expand transactions with sales agents who have little work experience. . It goes without saying that manufacturers and sales agents on the product purchasing side also want to ensure a stable supply of products.

  In view of the current situation, the present invention provides a price maintenance system, method, and program capable of reducing the price recovery risk of each company in a chain transaction performed by a plurality of companies without taking other credit enhancement means. With the goal.

The object of the present invention is achieved by a price maintenance system, method and program having the following configuration.
(1) The invention according to claim 1 is a price maintenance server having a price maintenance server that executes processing for allocation and maintenance of prices related to chain transactions by a plurality of companies, wherein the price maintenance server includes:
Distribution condition data including percentage data or amount data for allocating the received money to each receiving company in the chain transaction, as well as payment date, instruction data reception or payment of a certain amount or more Distribution setting data table (16a) storing payment condition data including,
A first account data table (14a) for storing the deposit amount in accordance with the deposit to the maintenance account from the final paying company in the chain transaction;
Means for determining whether the payment condition data corresponds to the payment condition data stored in the distribution setting data table (16a);
When it corresponds to the payment condition data, it is stored in the first account data table (14a) based on the distribution condition data by obtaining the distribution condition data stored in the distribution setting data table (16a). Means for determining a distribution amount for each recipient company from the deposit amount;
And a second account data table (14c) storing withdrawal information data indicating payment to the designated account of each recipient company made according to the determined distribution amount.

(2) The invention according to claim 2 is characterized in that, in claim 1, the distribution condition data includes amount data with a priority order to be paid to each receiving company.

(3) The invention according to claim 3 is a method in which the price maintenance server executes a process for distribution and maintenance of a price related to a chain transaction by a plurality of companies, wherein the price maintenance server includes:
Distribution condition data including percentage data or amount data, and payment date, receipt of instruction data, or receipt of a certain amount or more for allocating the received money to each recipient company in the chain transaction Storing the payment condition data including the distribution setting data table (16a),
Storing the deposit amount in the first account data table (14a) according to the deposit to the maintenance account from the final paying company in the chain transaction;
Acquiring the payment condition data stored in the distribution setting data table (16a), and determining whether the acquired payment condition data is satisfied;
Obtaining the distribution condition data stored in the distribution setting data table (16a) in response to determining that the payment condition data is satisfied;
Determining a distribution amount from the deposit amount data according to the acquired distribution condition data;
Storing in the second account data table (14c) withdrawal information data indicating payment of the distribution amount to the designated account of each recipient company made according to the determined distribution amount. .

(4) The invention according to claim 4 is characterized in that, in claim 3, the distribution condition data includes amount data with a priority order to be paid to each receiving company.

  According to the price maintenance system according to the present invention, in a chain transaction involving a plurality of companies, the price paid by the final paying company to the maintenance account is temporarily stored, and then distributed and paid to each receiving company. In many cases, the final paying company is generally a company with high creditworthiness, and the money collection risk of each receiving company is eliminated by ensuring that the received amount of each receiving company is securely stored in the maintenance account. Each receiving company can carry out transactions without anxiety without burdening deposits etc. This system is also useful in that the burden is small compared to other credit enhancement means.

  Conventionally, even when the final paying company has successfully paid for the direct business partner, the credit / debt relationship between the final paying company and the business partner is canceled, but other than that The receivable-liability relationship between companies remains unaffected. On the other hand, in this system, when the final paying company deposits the money into the account, the financial institution sorts out the debts and debts, so that the debts and debts relationship between the companies is related to the financial institutions and each receiving company. It will replace the debt and debt relationship between the two. Therefore, when the normal payment is received from the final paying company, all the claims and debts between the receiving companies are cancelled. In addition, since the amount related to claims and liabilities between financial institutions and each receiving company is the difference between the amounts related to the claims and liabilities that occurred between the receiving companies at the time of the transaction, the risk that each receiving company bears has been It becomes much smaller than.

  This system is very useful in that the safety of transactions can be secured without being affected by differences in creditworthiness or fluctuations of companies involved in chain transactions.

Embodiments of the present invention will be described below with reference to the drawings.
FIG. 1 is a configuration diagram schematically and schematically showing an embodiment of a price maintenance system according to the present invention. The price maintenance server 10 is installed in a financial institution (for example, a bank) capable of organizing receivables and payables generated between companies. The price maintenance server 10 is an appropriate computer that executes the system, and the function of the system is executed by a program installed in the price maintenance server 10. The price maintenance server includes a central processing unit (CPU) for executing a program for realizing the functions of the system, a main storage device for storing various programs related to the system, and an auxiliary storage. By including the device and the keyboard and display device, which are other general input / output devices, necessary data input and data display can be performed. Data input / output includes data exchange performed by connecting to an appropriate communication network, and includes a general communication device for that purpose.

 1 exemplifies a chain transaction involving a plurality of companies A, B, C, D, and E, as in FIG. 7 described above. Parts manufacturers A to B, B to C, C to D Then, parts D, 1, 2, 3 and 4 are delivered from D to final product manufacturer E, respectively. Due to this delivery process, there is a receivable-liability relationship between each company that deals directly. In the payment process for this, first, the final product manufacturer E transfers, for example, a payment amount of 1 million yen, which is a debt amount, to the price maintenance account 14 installed and managed in the storage device by the price maintenance server 10. In the embodiment of FIG. 1, the transferred deposit amount is distributed according to a preset distribution condition and is stored in the price maintenance account 14. In this specification, “allocate” means to determine an allocation amount. In the embodiment of FIG. 1, “maintain in the price maintenance account” means that the allocated amount is separately managed in the price maintenance account and the withdrawal process is limited until payment is made ( The same applies to the embodiment of FIG. 2 described later). Thereafter, in accordance with the set payment conditions, a process of paying from the price maintenance account 14 to the designated accounts of the parts manufacturers A to D is executed. Note that “payment” in this specification means that payment processing is generally performed regardless of the type of processing, and includes, for example, transfer, transfer, or similar processing. Here, the amount transferred to the account of each of the component manufacturers A to D is only the amount of difference in credits and debts between the companies. For example, a deposit amount of 1 million yen from manufacturer E is distributed to 700,000 yen for A, 100,000 yen for B, 100,000 yen for C, and 100,000 yen for D. This result is the same as in the case of FIG. 4 described above when the price collection is performed without delay.

 In the price maintenance system according to the present invention, the companies involved in the chain transaction do not directly transfer funds to each other in the price collection, but the final payment company located at the end of the chain (in the illustrated example, the final product manufacturer E, hereinafter, Receiving companies (referred to as “final paying companies”) to the money conservation account, and each receiving company (in the example shown, each component manufacturer A to D) located in the middle of the chain and at the opposite end in accordance with the preset distribution conditions. ) Will be stored in the price maintenance account. And it pays to each receiving company on a predetermined date. As a result, each receiving company can surely collect the money regardless of the situation of other receiving companies. Hereinafter, the final payment company and the receiving company that participate to use this system may be referred to as “member companies”.

The price maintenance server 10 has a control unit 12 mainly composed of a CPU, and installs a price maintenance account 14 managed by the control unit 12. The price maintenance account 14 is a special account previously set up in a financial institution or the like for a specific group of companies composed of companies A to E related to a predetermined chain transaction. The payment to the price maintenance account 14 is performed by the final payment company. In the example of FIG. 1, the final payment company is only the manufacturer E, but in general, there may be a plurality of final payment companies, and in that case, the plurality of final payment companies deposit money in the payment maintenance account 14 respectively. It will be. The withdrawal from the price maintenance account 14 is performed according to preset distribution conditions (distribution rate of each receiving company, distribution amount, etc.) and payment conditions (predetermined date, etc.). The price maintenance server 10 creates an account data table 14a in order to manage payment information data related to the price maintenance account 14, and stores it in an appropriate storage device. The account data table 14a includes information items such as “Payment person”, “Payment date”, “Payment amount”, and the payment maintenance server 10 has made payment to the payment maintenance account 14 from the final paying company. Sometimes, data corresponding to these information items is stored. Further, the price maintenance server 10 creates an account data table 14b in order to manage distribution information data in which the deposit amount is distributed according to the set distribution condition, and stores it in an appropriate storage device. The account data table 14b includes information items such as “recipient” and “distributed amount”. Further, the price maintenance server 10 creates an account data table 14c for managing the withdrawal information data in which the price has been paid to each receiving company in accordance with a preset payment condition, and stores it in an appropriate storage device. The account data table 14c includes information items such as “date”, “withdrawal destination”, “withdrawal amount”, “balance”, and the like. The account data tables 14a, 14b, and 14c are for storing and managing these pieces of information, and the illustrated configuration is shown as an example.

 Furthermore, the price maintenance server 10 provides a distribution setting data storage unit 16 managed by the control unit 12 in an appropriate storage device, and creates and stores a distribution setting data table 16a therein. The distribution setting data table 16a stores data relating to distribution conditions and payment conditions set in advance for the price to be maintained. The distribution setting data table 16a in the example of FIG. 1 includes information items such as “recipient”, “distribution condition”, “payment condition”, and “payment account”. The “recipient” is each receiving company A to D, and the “allocation condition” stores data of the ratio (allocation rate) of the amount paid to each receiving company with respect to the total amount of money deposited in the price maintenance account 14. . In this case, even if the payment amount of the final paying company fluctuates in each transaction, the distribution ratio to each receiving company is always constant. In this example, the “payment condition” is a date when the maintenance fee is transferred to the account of each receiving company. The payment date for each receiving company is not necessarily the same date. The “payment account” is an account for which each receiving company designates a transfer. The payment account does not need to be provided in the same financial institution as the financial institution in which the price maintenance server 10 is installed. The maintenance server 10 refers to the distribution setting data table 16a when allocating the money transferred to the price maintenance account 14 and when paying the price that has been maintained to the designated account.

 FIG. 2 is a block diagram schematically and schematically showing another embodiment of the price maintenance system according to the present invention. In addition, the same code | symbol is used for the component which is common in the form of FIG. A difference from the embodiment of FIG. 1 is a distribution setting data table 16b. In the information item “distribution condition” of the distribution setting data table 16b, data of the amount actually paid to each receiving company is stored. In this case, for example, it is assumed that the amount of money received from the final paying company is constant in each transaction, and that the amount allocated and paid to each receiving company is also constant. Further, the distribution setting data table 16b is given a priority from the upper level to the lower level. That is, when 1 million yen, which is a normal price, is deposited, 300,000 yen is paid to manufacturer A first, then 100,000 yen to B, 100,000 yen to C, and 40 again to A. Ten thousand yen is paid, and finally D is paid 100,000 yen. Such prioritized distribution conditions are set in advance with the approval of each member company. The example of FIG. 2 shows the distribution and payment situation when the final paying company E has received only 500,000 yen, which is half of the normal price. The deposit amount of 500,000 yen is 300,000 yen for manufacturer A with the highest priority in distribution setting data table 16b, 100,000 yen for B, which is the next priority, and the next priority. It is distributed to 100,000 yen for a certain C, and each is paid. In this case, the remaining 400,000 yen for A and 100,000 yen for D are not paid. Such priorities are also set in consideration of minimizing risk.

 The distribution conditions in the embodiment shown in FIGS. 1 and 2 are examples, and other distribution conditions can be set. For example, regardless of the total amount of deposit, if there is a deposit of a certain amount or more, a certain amount (for example, 300,000 yen) is always allocated to A, and the remaining amount is allocated to BD in a predetermined ratio (for example, 50% each) , 25%, 25%).

 FIGS. 3A and 3B show distribution setting data tables 16c and 16d, respectively, for illustrating another example of payment conditions. In FIG. 3A, the distribution conditions are the same as in the example of FIG. 2, but the payment conditions are different. Payment to the manufacturer A at the first stage is executed by “instruction of manufacturer A”. For example, payment processing is executed in response to payment instruction data being transmitted from a suitable computer terminal installed at manufacturer A via the network and received by the price maintenance server. Subsequently, payment to the manufacturer B is executed “as soon as the first payment to the manufacturer A is completed”. Further, the payment to the manufacturer C is executed according to the “instruction of the manufacturer C”. In this case, the context of the manufacturer A instruction and the manufacturer C instruction may be arbitrary. For example, when a normal deposit of 1 million yen is made at a time, the price to any manufacturer is immediately allocated and maintained at the time of deposit, and can be paid at any time. In addition, for example, when payment is made gradually over several days from a plurality of final paying companies, payment to maker A will be made if the deposit amount exceeds 300,000 yen and maker A instructs, according to the priority of distribution conditions If the next 100,000 yen is deposited, payment to manufacturer B is immediately made. The instruction from the manufacturer C may be given at any time, but the payment is not executed unless the 100,000 yen paid to the manufacturer C is deposited. Also, as an example, manufacturers A and C that use “instruction” as a payment condition may be notified to each of them when there is a deposit that can be paid.

  The payment condition in FIG. 3 (B) is “when there is a deposit of 300,000 yen or more” for payment to manufacturer A in the first stage. Therefore, when a normal deposit of 1 million yen is made at a time, of course, payment is immediately made to all manufacturers. For example, when a gradual payment is made from a plurality of final payment companies, the deposit amount is 300,000. As soon as the yen is exceeded, payment to manufacturer A is executed. In addition, when a deposit of 500,000 yen or more is received at one time, payment to manufacturers A, B, and C is immediately executed. As illustrated in FIG. 3, various payment conditions can be set.

  In the embodiment of FIGS. 1 and 2, a simple example in which a chain transaction consists of only one transaction path is shown. However, there may be a plurality of end product manufacturers E. For example, the end product manufacturer E may deliver a part from parts manufacturers D1 and D2, and part manufacturer D1 may have a complicated transaction path such as parts delivered from part makers C1 and C2. Even in such a case, each member company of the final paying company group and the receiving company group is identified, and distribution conditions and payment conditions for each receiving company are set in advance based on the entire payment from the final paying company group. It is possible to implement the system.

  Note that the deposit processing to the price maintenance account and the transfer processing from the price maintenance account to each designated account are executed according to a normal business system of a financial institution or the like (for example, a bank).

  FIG. 4 is a configuration diagram schematically and schematically showing still another embodiment of the price maintenance system of the present invention. In FIG. 4, the final product manufacturer E transfers, for example, 1 million yen as a debt amount to the price maintenance account 14 installed and managed by the price maintenance server 10. Data related to the deposit information is stored in the same account data table 14a as in FIGS. In the embodiment shown in FIG. 4, the deposit amount is not allocated at the time of depositing, and is maintained in the price maintenance account 14 as it is. In the embodiment of FIG. 4, “maintain in the price maintenance account” means that the deposit amount is managed in the price maintenance account and the withdrawal process is limited until distribution and payment are performed. . After that, by referring to the distribution setting data table 16a similar to FIG. 1, at the time corresponding to the preset payment condition, the price maintained in the price maintenance account 14 is distributed according to the preset distribution condition. Then, the process of paying the account of each manufacturer A to D is executed. Data relating to the withdrawal information is stored in the same account data table 14c as in FIGS.

FIG. 5 is a flowchart schematically showing a processing flow executed by the price maintenance system of the embodiment shown in FIG. Reference numerals in FIG. 1 are referred to as necessary. The same processing flow is applied to the embodiment of FIG.
Step 101: The price maintenance server 10 installs the price maintenance account 14 based on the contract contents between the member company group (consisting of the final paying company and the receiving company) and the financial institution, and the account data tables 14a and 14b. , 14c are created and stored in the storage device.
Step 102: The price maintenance server 10 creates a distribution setting data table 16a that sets distribution conditions and payment conditions for the maintenance price to each receiving company based on the contract contents between the member company group and the financial institution. Store in the setting data storage unit 16.
Step 103: The price maintenance server 10 checks at any time (every predetermined period or on a predetermined date) whether there is any payment to the price maintenance account 14. If there is a deposit (transfer) to the price maintenance account 14, the process proceeds to the next step.
Step 104: The payment maintenance server 10 stores payment information data such as a payment person, a payment date, and a payment amount in the account data table 14a based on the payment contents to the payment maintenance account 14.
Step 105: The price maintenance server 10 refers to the distribution setting data table 16a stored in the distribution setting data storage unit 16, and acquires distribution condition data.
Step 106: The price maintenance server 10 distributes the payment amount to each receiving company according to the distribution conditions of the distribution setting table 16a, and stores the maintenance information data in the account data table 14b, thereby distributing the payment amount in a state where the payment amount is distributed. Manage and maintain with the maintenance account 14.
Step 107: The price maintenance server 10 refers to the distribution setting data table 16a stored in the distribution setting data storage unit 16, and acquires payment condition data.
Step 108: The price maintenance server 10 determines whether or not the acquired payment condition (payment date) is satisfied. If it is determined that the payment condition is met, the process proceeds to the next step.
Step 109: The payment maintenance server 10 stores the withdrawal information data in the account data table 14d after performing payment processing to the designated account of each receiving company stored in the distribution setting data table 16a according to the payment conditions.

FIG. 6 is a flowchart schematically showing a processing flow executed by the price maintenance system of the embodiment shown in FIG. Reference numerals in FIG. 4 are referred to as necessary.
Step 201: The price maintenance server 10 installs the price maintenance account 14 based on the contract contents between the member company group (consisting of the final paying company and the receiving company) and the financial institution, and the account data tables 14a and 14c. Is created and stored in the storage device.
Step 202: The price maintenance server 10 creates and allocates a distribution setting data table 16a for setting distribution conditions and payment conditions for the maintenance price to each receiving company based on contracts between member companies and financial institutions. Store in the setting data storage unit 16.
Step 203: The price maintenance server 10 checks at any time (every predetermined period or on a predetermined date) whether there is any payment to the price maintenance account 14. If there is a deposit (transfer) to the price maintenance account 14, the process proceeds to the next step.
Step 204: The price maintenance server 10 stores the deposit information data such as the depositor, the deposit date, and the deposit amount in the account data table 14a based on the contents of the deposit to the price conservation account 14, thereby maintaining the deposit amount as the price conservation. Secure with account 14.
Step 205: The price maintenance server 10 refers to the distribution setting data table 16a stored in the distribution setting data storage unit 16 at any time (every predetermined period or on a predetermined date), and acquires payment condition data.
Step 206: The price maintenance server 10 determines whether or not the acquired payment condition (payment date) is met. If it is determined that the payment condition is met, the process proceeds to the next step.
Step 207: The price maintenance server 10 acquires distribution condition data stored in the distribution setting data table 16a.
Step 208: The price maintenance server 10 allocates the deposit amount stored in the price maintenance account 14 according to the acquired allocation condition, pays the designated company account of each recipient company, and then withdraws information data. Store in the account data table 14c.

1 is a configuration diagram schematically and schematically showing an embodiment of a price maintenance system according to the present invention. It is a block diagram which shows schematically and typically another embodiment of the price maintenance system by this invention. (A) And (B) is a figure which shows another Example of a distribution setting table, respectively. It is a block diagram which shows schematically and typically another embodiment of the price maintenance system by this invention. It is a flowchart which shows roughly the processing flow performed by the price maintenance system of FIG. It is a flowchart which shows roughly the processing flow performed by the price maintenance system of FIG. It is the figure which showed typically the conventional chain transaction in which several companies A, B, C, D, and E relate.

Explanation of symbols

10 Price maintenance server 12 Control unit 14 Price maintenance account 14a, 14b, 14c Account data table 16 Distribution setting data storage unit 16a, 16b, 16c, 16d Distribution setting data table A, B, C, D, E Manufacturer

Claims (4)

In a price maintenance system having a price maintenance server that executes processing for allocation and maintenance of prices related to chain transactions by a plurality of companies, the price maintenance server includes:
Distribution condition data including percentage data or amount data for allocating the received money to each receiving company in the chain transaction, as well as payment date, instruction data reception or payment of a certain amount or more Distribution setting data table (16a) storing payment condition data including,
A first account data table (14a) for storing the deposit amount in accordance with the deposit to the maintenance account from the final paying company in the chain transaction;
Means for determining whether the payment condition data corresponds to the payment condition data stored in the distribution setting data table (16a);
When it corresponds to the payment condition data, it is stored in the first account data table (14a) based on the distribution condition data by obtaining the distribution condition data stored in the distribution setting data table (16a). Means for determining a distribution amount for each recipient company from the deposit amount;
A price maintenance system comprising: a second account data table (14c) storing withdrawal information data indicating payment to a designated account of each recipient company made according to the determined distribution amount.   2. The price maintenance system according to claim 1, wherein the distribution condition data includes amount data with a priority order to be paid to each receiving company. In the method in which the price maintenance server executes processing for distribution and maintenance of the price related to the chain transaction by a plurality of companies, the price maintenance server includes:
Distribution condition data including percentage data or amount data, and payment date, receipt of instruction data, or receipt of a certain amount or more for allocating the received money to each recipient company in the chain transaction Storing the payment condition data including the distribution setting data table (16a),
Storing the deposit amount in the first account data table (14a) according to the deposit to the maintenance account from the final paying company in the chain transaction;
Acquiring the payment condition data stored in the distribution setting data table (16a), and determining whether the acquired payment condition data is satisfied;
Obtaining the distribution condition data stored in the distribution setting data table (16a) in response to determining that the payment condition data is satisfied;
Determining a distribution amount from the deposit amount data according to the acquired distribution condition data;
Storing in the second account data table (14c) withdrawal information data indicating payment of the distribution amount to the designated account of each recipient company made according to the determined distribution amount. Price preservation method.   4. The price maintenance method according to claim 3, wherein the distribution condition data includes amount data with a priority order to be paid to each receiving company.

Images