JP2014026512A - Electronic-recording credit generation system and method for repeat transactions - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide electronic-recording credit generation system and method for repeat transactions.SOLUTION: A system includes: a repeat transaction contract DB for storing occurrence condition of a credit generated for every predetermined due date; means for accessing the aforementioned DB and confirming presence of occurrence condition under which an electronic credit is to be generated; means for generating an electronic credit on the basis of the occurrence condition; means for transmitting an occurrence record of the generated electronic credit to Densai Net (i.e., an electronic credit network) and receiving a debtor agreement request therefrom; means for determining whether the electronic credit requires a creditor to indicate a credit amount; means for determining whether the electronic credit needs an actual agreement of a debtor, in response to the debtor agreement request; and means for presenting, via an Internet banking system, the electronic credit determined to be presented with the credit amount, and receiving the credit amount from the creditor. In response to a determination that an agreement of the debtor is not individually required, the present system transmits, to Densai Net, a signal indicating that an agreement of the debtor on the electronic credit has been obtained.

Description

  The present invention relates to an electronic record receivable generation system and method. More specifically, the present invention relates to a system and method for generating an electronically recorded bond for repetitive transactions that can be an alternative to direct debit.

  As a method of raising funds by a company utilizing monetary claims, transfer of bills and accounts receivable is known. However, there are problems with bills such as high costs for creation, delivery, and storage, risk of loss or theft, and inability to divide. There is a problem that there is a risk, and it takes time and cost to confirm the existence and attribution of the receivable.

  In order to solve these problems, an electronic record credit system was established, and an electronic credit record organization (commonly known as Densai Net (registered trademark)) was established by the National Bank Association (JBA). “Densai Net” will provide a new settlement infrastructure that records and distributes electronically-recorded receivables, which financial institutions participate in. Specifically, “Densai Net” records the occurrence, transfer, payment, etc. of electronic receivables (hereinafter “Densai”) in the record book. In addition, some financial institutions established their own electronic bond recording institutions to provide additional services.

  As a method of generating “Densai”, “obligor claim method” and “creditor claim method” are known (for example, Non-Patent Document 1, pages 52 to 55). The obligor claim method is a method in which the obligor identifies the creditor and requests the occurrence record to the “Densai Net” through the transaction financial institution. This is a method of requesting occurrence records to the “Densai Net” through a transaction financial institution after identifying the person.

  In the creditor claim method, in response to a request for a record of occurrence from a creditor, an approval request notification is transmitted from the “Densai Net” to the debtor via a financial institution. If the debtor accepts “Densai”, the occurrence record is established.

  In addition, it is known that account transfer has been conventionally performed for transactions (payment transactions) in which payments are generated every month. Account transfer is a financial institution service that automatically debits the specified fee from the depositor's account on the designated transfer date, transfers it to the collector's account, and completes the payment based on the contract between the financial institution, the collector and the depositor. .

The Bank of Japan National Bank Association Electronic Credit Recorder Establishment Preparatory Office, “Practical Q & A on Electronic Record Credits-Illustrated by Zenginkyo Electronic Credit Recorder“ Densai Net ””

  In transactions between companies, there are many cases where debts and debts are generated every month (or every predetermined period). Such transactions include a transaction in which the payment amount is a fixed amount every month and a transaction in which the payment amount varies each time.

  Although it was possible to use traditional account transfers as a means of settlement for such transactions, conventional account transfers can be partly transferred and transferred to a third party. There wasn't.

  When using “Densai” as a payment method, it was possible to divide a portion of the amount of receivables and transfer it to a third party. Or even if the amount of payment varies each time, the creditor or debtor must generate “Densai” each time through the transaction financial institution.

  In addition, when using “Densai” by the creditor claim method, in order to establish the occurrence record of “Densai”, it was assumed that the contents were well understood by the above-mentioned repetitive transaction However, it was necessary to obtain the obligor's consent each time, and the procedure was troublesome for the obligor.

  The present invention has been made in view of such a problem, and an object thereof is to provide an electronic record receivable generation system and method for repetitive transactions that can be an alternative to account transfer.

  In order to solve the above-described problems, an electronic record receivable generation system according to the present invention includes an iterative transaction contract DB that stores conditions for generating receivables generated on a predetermined date based on transactions of a creditor and a debtor; , The recurring transaction contract DB is accessed at every predetermined timing, the confirmation means for confirming the existence of the occurrence condition for generating the electronic bond, and the occurrence condition when the generation condition for generating the electronic bond exists. Generation means for generating an electronic bond based on conditions, first transmission / reception means for transmitting the generated record of the electronic bond to the first external system and receiving a debtor consent request from the first external system; Amount designation determination means for determining whether or not the generated electronic receivable needs to be instructed by a creditor for a credit amount, and a debtor consent received from the first external system In response to the request, an acceptance request judging means for judging whether or not the electronic claim actually needs the consent of the debtor, and the electronic claim that is judged to need to be instructed for the amount of the second A second transmission / reception means for transmitting to an external system and receiving a credit amount from the creditor via the second external system, wherein the first transmission / reception means requires the obligor's consent individually by the consent request determination means; In response to the determination that the electronic debt is not approved, a signal indicating that the electronic debt is approved by the debtor is further transmitted to the first external system without individually obtaining the consent of the debtor. Characterize.

  In addition, an electronic record receivable generation method according to the present invention is a method executed in an electronic record receivable generation system, wherein the electronic record receivable generation system is based on transactions of a creditor and a debtor every predetermined date. A recurring transaction contract DB for storing conditions for generating a bond to be generated, wherein the method accesses the repetitive transaction contract DB at predetermined timings and confirms whether or not the generation condition for generating an electronic bond is present And when the generation condition for generating the electronic bond exists, the step of generating the electronic bond based on the generation condition, and the generated electronic bond needs to be instructed by the creditor for the amount of the bond Determining whether or not it is necessary to instruct the amount of receivable, the electronic receivable is transmitted to a second external system, and the second external system is Receiving a credit amount from the creditor, transmitting the generated electronic bond occurrence record to the first external system, receiving a debtor consent request from the first external system, In response to the obligor consent request received from the first external system, the step of determining whether the electronic receivable actually requires the obligor's consent and that the obligor's consent is not individually required In response to the determination, the method includes a step of transmitting a signal indicating that the electronic credit is approved by a debtor to the first external system without obtaining the consent of the debtor individually. .

  According to the present invention, it is possible to generate “densai” every predetermined period without requiring the creditor and debtor to carry out billing and acceptance actions one by one, and the generated “densai” It can be divided and transferred to a third party.

It is a figure explaining the structure and other relevant elements of the starch generation system which concerns on this invention. It is a functional block diagram of a densai generation system according to the present invention. It is a flowchart of the process implemented in the densai generation system which concerns on this invention. It is a figure explaining an example of the occurrence record of "densai" of bond record DB. It is a figure explaining an example of the repeated transaction contract data of a repeated transaction contract DB.

  Hereinafter, embodiments of the present invention will be described in detail. In the following description, an embodiment based on the above-mentioned “creditor billing method” will be described. However, it should be noted that a part of the gist of the present invention can be naturally applied to the “obligor billing method”. Since the present invention can be used as an alternative to account transfer, it will be described on the assumption that the creditor and the debtor are customers of the same financial institution.

  FIG. 1 is a diagram for explaining the configuration of a starch generation system 100 according to the present invention and other related elements. The densai generation system 100 is connected to a system apparatus that provides the densai net 110 and the internet banking 130 via a network. The network can be a known network such as a dedicated line.

  As described above, the Densai Net 110 is a system that becomes a settlement infrastructure operated by the Zenginkyo. The Densai Net 110 can maintain a record of occurrence of “Densai”, a transfer record, a record of payment, etc. in a record book. The densai net 110 can communicate with the densai generation system 100 to send and receive various data and signals.

  The internet banking 130 is a well-known internet banking system. The internet banking 130 can provide business services related to “Densai” to the customer 140, and can receive a predetermined instruction from the customer 140 and forward it to the Densei generating system 100.

  The customer 140 is a user of the Internet banking 130 and can be a creditor or a debtor through a business transaction with another customer 140.

  The densai generation system 100 includes a transmission / reception unit 101, a bond record DB 102, a repetitive transaction contract DB 103, and a customer I / F 104.

  The transmission / reception unit 101 can communicate with the Densai net 110 to transmit / receive various data and signals. The bond record DB 102 is a database (DB) that stores data on occurrence records, transfer records, payment records, etc. of “Densai” in which the Densai generation system 100 is involved. Here, an example of data stored in the bond record DB 102 will be described with reference to FIG.

  FIG. 4 is a diagram for explaining an example of the “Densai” occurrence record 400 stored in the bond record DB 102. The occurrence record 400 includes at least biller information 401, debtor information 402, creditor information 403, credit amount 404 and payment date 405.

  The claimant information 401 indicates whether “Densai” was claimed by the creditor or the debtor. In other words, it indicates whether “Densai” is based on the creditor claim method or the debtor claim method. The claimant information 401 includes an ID for identifying a creditor or a debtor, a description, and the like.

  The debtor information 402 and the creditor information 403 indicate the identification ID and account information of the debtor and creditor, respectively. This account information is information used for inter-account remittance settlement performed on the due date. The amount of receivable 404 and the due date 405 indicate the amount of receivable “Densai” and the due date, respectively.

  Referring back to FIG. 1 again, the iterative transaction contract DB 103 is a database (DB) that stores the conditions for the occurrence of receivables generated every predetermined date by transactions of creditors and debtors. Here, an example of data stored in the repeated transaction contract DB 103 will be described with reference to FIG.

  FIG. 5 is a diagram for explaining an example of iterative transaction contract data 500 stored in the iterative transaction contract DB 103. The iterative transaction contract data 500 includes at least obligor information 501, a withdrawal date 502, an amount 503, a site 504, and creditor information 505.

  The debtor information 501 and the creditor information 505 indicate the identification ID and account information of the debtor and creditor, respectively. This account information is used when the densai generation system 100 generates “densai”. For example, the debtor information 501 and the creditor information 505 are used as data set in the debtor information 402 and the creditor information 403 of the occurrence record 400. Note that the bank code of the debtor information 402 and the creditor information 403 can be a code of a financial institution that operates the dansai generation system 100.

  The date of withdrawal 502 indicates the date on which “densai” is generated. A specific date (for example, 10th) can be set as the date of departure 502, and information “end date” whose actual date varies depending on the month can be set.

  The amount 503 indicates the amount of bond set in the generated “densai”. If the same payment amount occurs every month in a recurring transaction, that amount can be set. On the other hand, by setting information other than a specific amount such as “every time”, the creditor can instruct the credit amount of “Densai” to be generated later.

  The site 504 shows information for setting a payment date (settlement time limit) of “Densai”. For example, if “1 month” is designated, the payment date is one month after the date when “Densai” is generated (the date of the withdrawal).

  Referring back to FIG. 1 again, the customer I / F 104 is an interface for communicating with the customer 140 via the Internet banking 130. Although not clearly shown in FIG. 1, the densai generation system 100 has a control unit, a main storage unit, an auxiliary storage unit, an I / F unit, A display part is provided.

  The control unit is also called a central processing unit (CPU), performs control of each component in the starch generation system 100 and calculation of data, and also stores various programs stored in the auxiliary storage unit in the main storage unit To read and execute. The main storage unit is also called a main memory, and stores various received data, computer-executable instructions, data after arithmetic processing by the instructions, and the like. The auxiliary storage unit is a storage device typified by a hard disk (HDD) and is used when data and programs are stored for a long period of time.

  The I / F unit serves as an interface for transmitting and receiving data to and from other systems and devices, and provides an interface for receiving various commands and input data (such as various masters and tables) from the system operator. . The customer I / F 104 described above is a component corresponding to the I / F unit. The display unit provides a display screen for displaying the processed data.

  FIG. 2 is a functional block diagram of the starch generation system 100 according to the present invention. In addition to the above-described bond record DB 102 and repetitive transaction contract DB 103, the densai generation system 100 includes a confirmation unit 201, a generation unit 202, a first transmission / reception unit 203, an amount designation determination unit 204, a consent request determination unit 205, and a second A transmission / reception unit 206 is included.

  The confirmation unit 201 reads the iterative transaction contract DB 103 at a predetermined timing (for example, a time determined every day), and confirms whether there is data that should generate “Densai”. Specifically, when the processing day is the last day of the month, the generation generation system 100 identifies data stored in the iterative transaction contract DB 103 and having information “end date” stored on the date of withdrawal 502. Read out.

  The generation unit 202 generates “Densai” based on the data read from the repeated transaction contract DB 103 by the confirmation unit 201. The generated “densai” includes the data illustrated in the occurrence record 400 and is stored in the bond record DB 102.

  The first transmission / reception unit 203 communicates with the Densai net 110 to transmit / receive predetermined data. More specifically, the first transmission / reception unit 203 transmits the “Densai” occurrence record generated by the Densai generation system 100 to the Densai net 110, and the “Densai” ”Is transmitted to indicate that the obligor has consented (acceptance is OK). Further, the first transmission / reception unit 203 receives a debtor approval request requesting that the debtor consents to the content of “densai” from the densai net 110.

  The amount designation determination unit 204 determines whether the “densai” generated by the densai generation system 100 needs to be instructed by the creditor for the amount of the receivable. More specifically, “densai” generated based on the iterative transaction contract data 500 in which the amount 503 includes information other than a specific amount such as “every time”, the receivable amount 404 is blank. It is determined that the creditor amount needs to be instructed by the creditor.

  In response to the debtor consent request received from the densai net 110, the consent request determination unit 205 determines whether the “densai” actually requires the debtor's consent. More specifically, the “Densai” generated by the Densai generation system 100 is generated according to the conditions agreed in advance between the creditor and the debtor. No consent is required. Whether the combination of the borrower and creditor user numbers included in “Densai” matches the combination of the debtor and creditor user numbers stored in the repeated transaction contract DB 103. It can be done depending on whether or not.

  The second transmission / reception unit 206 communicates with the internet banking 130 and transmits / receives predetermined data. Specifically, the second transmitting / receiving unit 206 presents “Densai”, which needs to be instructed of the amount of receivable, to the creditor customer 140 via the Internet banking 130 or the like, and also instructed by the creditor. The received credit amount is received via the Internet banking 130 or the like.

  FIG. 3 is a flowchart of processing performed in the starch generation system 100 according to the present invention. As a precondition for this processing flow, it is agreed between the two parties that payment of transactions between the creditor and the debtor will be made by “Densai”, and the creditor and the debtor have agreed in advance. It is assumed that data indicating the generated credit generation conditions is stored in the repeated transaction contract DB 103.

  In step S301, the densai generation system 100 reads the iterative transaction contract DB 103 at a predetermined timing (for example, a time determined every day), and confirms whether there is data that should generate “densai”. . Specifically, when the processing day is the last day of the month, the generation generation system 100 identifies data stored in the iterative transaction contract DB 103 and having information “end date” stored on the date of withdrawal 502. Read out.

  In step S <b> 302, the densai generation system 100 generates “densai” based on the data read from the repeated transaction contract DB 103. The generated “densai” is stored in the bond record DB 102. FIG. 4 shows an example of the generated “densai”.

  In step S <b> 303, the densai generation system 100 determines whether the generated “densai” requires designation of an amount by the creditor. Specifically, the “densai” generated in step S302 has information such as the occurrence record 400. When the amount 503 of the data of the repetitive transaction contract DB 103 that is the basis of this “densai” is “every time” (meaning that the amount fluctuates every time) or the like, the “den” shown in FIG. Since the receivable amount 404 of “Sai” is blank, it is determined that “densai” where the receivable amount 404 is blank needs to be designated by the creditor.

  If it is determined that it is necessary to specify the amount by the creditor, the process proceeds to step S304. On the other hand, if no such determination is made, the process proceeds to step S305.

  In step S <b> 304, the densai generation system 100 presents “densai” to the customer 140 (creditor) through the internet banking 130. The customer 140 who is a creditor designates the amount of the credit on the internet banking 130 through a predetermined screen and transmits it to the densai generation system 100. The densai generation system 100 stores the “densai” data updated with the designated amount of receivables in the receivable record DB 102.

  In step S <b> 305, the densai generation system 100 transmits the occurrence record of “densai” to the densai net 110. Here, the sent “Densai” is based on the creditor claim method in which the creditor has previously agreed to make the payment “Densai”. Note that the debtor's consent is required for the record to be established.

  In step S <b> 306, the densai generation system 100 receives a debtor consent request from the densai net 110. The debtor consent request is a signal requesting that the debtor accepts the contents of “Densai”. As described above, since “Densai” is based on the creditor claim method, the approval of the debtor is required for the establishment of the occurrence record.

  In step S307, the densai generation system 100 reads the iterative transaction contract DB 103 and determines whether or not the “densai” related to the obligor consent request received in step S306 requires confirmation to the obligor each time. judge. More specifically, the combination of the user numbers of the obligor information 501 and the creditor information 505 stored in the iterative transaction contract DB 103 is “densai” obligor information 402 and creditor information 403. The determination is made based on whether or not the combination matches each user number combination. Alternatively, according to another embodiment, the determination can be made based on another data item indicating that the generation is performed by the dansai generation system 100. If “densai” related to the debtor consent request does not need to be confirmed with the debtor, the process proceeds to step S308.

  If the “densai” related to the obligor's consent request requires confirmation from the obligor each time, the “densai” is the “densai” of the ordinary creditor claim method. Therefore, the densai generation system 100 notifies the customer 140, who is a debtor, via the internet banking 130 that the consent of “densai” is requested, and this processing flow is performed. finish.

  In step S308, the densai generation system 100 receives the “densai” related to the debtor consent request received in step S306, and obtains the “deni” "Sai" transmits a signal (OK response) indicating that it is OK by the debtor. In response to receiving the signal, the densai net 110 registers the “densai” in the record book as having been established.

  Although the principle of the present invention has been described above with reference to exemplary embodiments, those skilled in the art will appreciate that various embodiments that change in configuration and details can be realized without departing from the spirit of the present invention. Will understand. That is, the present invention can take an embodiment as, for example, a system, apparatus, method, program, or computer-readable storage medium.

100 Densai generation system 101 Transmitter / receiver 102 Bond record DB
103 Iterative Transaction Contract DB
104 Customer I / F
110 Densai Net 130 Internet Banking 140 Customer 201 Confirmation Unit 202 Generation Unit 203 First Transmission / Reception Unit 204 Amount Specification Determination Unit 205 Acceptance Request Determination Unit 206 Second Transmission / Reception Unit 400 Occurrence Record of “Densai” 500 Repeat Transaction Contract Data

Claims (5)

A recurring transaction contract DB that stores conditions for generating receivables that are generated on a predetermined date based on the transactions of creditors and debtors;
Confirming means for accessing the iterative transaction contract DB at a predetermined timing and confirming the presence or absence of the generation condition for generating an electronic bond,
Generating means for generating an electronic bond based on the generation condition when the generation condition for generating the electronic bond exists;
First transmission / reception means for transmitting the generated electronic bond occurrence record to a first external system and receiving a debtor consent request from the first external system;
Amount designation determination means for determining whether or not the generated electronic receivable needs to be instructed by a creditor for a receivable amount;
In response to a debtor consent request received from the first external system, an acceptance request determination means for determining whether or not the electronic claim actually requires the consent of the debtor;
A second transmission / reception means for transmitting the electronic bond determined to be instructed to receive a credit amount to a second external system and receiving the credit amount from the creditor via the second external system;
In response to the determination that the obligor's approval is not individually required by the approval request determination unit, the first transmission / reception unit outputs a signal indicating that the obligor has approved the electronic bond. And further transmitting to the first external system without individually obtaining approval from the person. A bond record DB for storing the electronic bond,
The electronic bond stored in the bond record DB includes a first creditor ID and a first creditor ID,
The occurrence conditions of receivables stored in the repetitive transaction contract DB include a second creditor ID and a second creditor ID,
The approval request determination means determines whether the electronic bond is based on whether the combination of the first obligor ID and the first creditor ID matches the combination of the second obligor ID and the second creditor ID. 2. The electronic record receivable generating system according to claim 1, wherein it is determined whether or not the approval of the debtor is actually required.   The amount designation determining means determines whether the generated electronic receivable needs to be instructed by the creditor for the amount of receivable based on whether the receivable amount of the generated electronic receivable is blank or not. The electronic record receivable generating system according to claim 1, wherein:   2. The electronically recorded bond generating system according to claim 1, wherein the first external system is a densai net, and the second external system is an internet banking system. An electronic record receivable generation method executed in an electronic record receivable generation system,
The electronic record receivable generation system includes a repetitive transaction contract DB that stores a generation condition of a receivable generated every predetermined date based on a transaction of a creditor and a debtor,
The method
Accessing the iterative transaction contract DB at a predetermined timing and confirming the presence or absence of the generation condition for generating an electronic bond;
Generating the electronic bond based on the generation condition when the generation condition for generating the electronic bond exists;
Determining whether the generated electronic receivable needs to be instructed by a creditor for a receivable amount;
Transmitting the electronic bond determined to need to be instructed to the amount of receivable to a second external system, and receiving the amount of receivable from the creditor via the second external system;
Transmitting the generated electronic bond occurrence record to the first external system;
Receiving a debtor consent request from the first external system;
In response to a debtor consent request received from the first external system, determining whether the electronic claim actually requires the debtor's consent;
In response to the determination that the obligor's consent is not individually required, a signal indicating that the obligor's consent has been made for the electronic receivable is obtained without obtaining the obligor's individual consent. Transmitting to the system.

Images