JP5525573B2 - Inter-account remittance settlement funds total withdrawal system and method - Google Patents

Description

  More particularly, the present invention relates to a method for summing and withdrawing funds in an inter-bank remittance settlement for electronically recorded receivables, and more specifically, summing the amount of receivables of electronically recorded receivables with the amount of receivables of original electronically recorded receivables. System and method for withdrawal.

  The settlement of electronic record receivables (hereinafter referred to as “electronic receivables”) in the Zengin Electronic Receivables Network (hereinafter referred to as “Densai Net”) of electronic receivables record institutions is generally performed by transfer between accounts using a transfer form. . For example, when the due date of a certain electronic receivable arrives, the financial institution receives settlement (withdrawal) data from Densai Net, withdraws the amount of the receivable from the underlying debtor's settlement account, and transfers it to the creditor's settlement account. Make a deposit.

The settlement process of electronic receivables on Densai Net is performed for each electronic receivable. Therefore, when the electronic receivable is divided and transferred, the settlement process is performed for each of the original electronic receivable (that is, the parent receivable) and the divided receivable (that is, the child receivable). For this reason, the amount of receivables of the parent receivable and each child receivable is deducted from the settlement account of the underlying debtor. For example, there is an electronic receivable whose amount of receivable is 200,000 yen from Company A (the underlying debtor) to Company B (the creditor). Suppose that 90,000 yen is divided and transferred to Company D. In this case, when the due date arrives,
・ Original electronic receivable (parent receivable): Company A → Company B ¥ 100,000
-Dividend receivable 1 (child receivable): Company A → Company C ¥ 10,000
-Dividend receivable 2 (child receivable): Company A → Company D ¥ 90,000
The three settlement processes are performed, and the amount of each receivable is withdrawn individually from the settlement account of Company A, which is the underlying debtor. This may be very confusing and troublesome for the underlying debtor Company A. Furthermore, if the obligor A did not know that the electronic receivables were split and transferred by Company B, the original electronic receivables of 200,000 yen would be 100,000 yen, 10,000 yen and 90,000 yen. You will feel uncomfortable with the withdrawal.

  In order to solve the above problems, according to one aspect of the present invention, in order to perform withdrawal processing by combining split receivables, a computer system is provided with an original debtor, a creditor, a claim amount, and a record number of an electronic claim. Based on the means to receive the settlement data included and the record number in the settlement data, it is determined whether the settlement data received includes split settlement data, and the split debt settlement data is included The withdrawal data by means of identifying the split loans divided from the same parent loan, and by adding the credit amount included in the settlement data of the identified split loan to the credit amount included in the settlement data of the parent loan And means for performing a withdrawal process for the sum of the amounts from the settlement account of the underlying debtor based on the generated withdrawal data.

  In the above system, the record number of the split claim is composed of a common number for identifying the parent claim of the split claim and a number specific to the split claim, and the means for identifying the split claim is the received settlement data Among these, by identifying settlement data including a record number having the same common number, a divided bond divided from the same parent loan is identified.

  The means for generating the withdrawal data can set the transaction classification of the withdrawal data so as to indicate that the withdrawal amount of the electronic bond is withdrawn.

  According to the present invention, since it is possible to withdraw the sum of the amount of receivable of the parent receivable and the amount of receivable of the split receivable, even if the electronic receivable is split and transferred, Withdrawal can be made from the settlement account in the same manner as the original electronic bond. In addition, according to the present invention, by converting the transaction classification, it is possible for the obligor / creditor to determine whether a normal transfer transaction or a transfer on the Densai Net has been performed. become.

It is a block diagram explaining typical payment processing of an electronic bond. It is a figure which shows the system environment which implements the settlement process of the split bond which concerns on one Embodiment of this invention. It is a flowchart which shows the flow of the settlement process of the split bond which concerns on one Embodiment of this invention. It is a figure which shows the system environment which implements conversion of the transaction classification based on the 2nd Embodiment of this invention. It is a flowchart which shows the flow of the conversion process of the transaction classification which concerns on the 2nd Embodiment of this invention.

  Hereinafter, embodiments of the present invention will be described in detail.

  FIG. 1 is a block diagram illustrating a typical settlement process for an electronic bond. Environment 100 includes Densai Net 110, which is an electronic bond recording institution, X Bank system 120 in which the obligor has a settlement account, Zengin Exchange Network 130, and Y Bank system 140 in which the creditor has a settlement account. Including.

  The X bank system 120 includes a Densai Net Cooperation System (DRS) 122, an exchange system 124, and a billing system 126. The DRS 122 is a relay system with the Densai net 110, and exchanges information related to the electronic bond with the Densai net 110.

  The DRS 122 receives, from the Densai Net 110, settlement data of an electronic bond that should be settled, such as an electronic bond that is due for payment. The settlement data from Densai Net 110 includes, for example, the settlement date of electronic receivables, destination information (for example, settlement account information of the obligor, user number, record number of electronic receivable, amount of receivable, and due date) ), And destination information (for example, settlement account information of creditors). In the example of FIG. 1, DRS 122 receives payment data from Densai Net 110 for the electronic debt “A111” with the underlying debtor “Company A”, the creditor “B Company”, and the credit amount “200,000 yen”. Receive. Each electronic bond is assigned a unique record number, and each electronic bond can be identified by the record number. The user number is a number uniquely assigned to a Densai Net user. Transmission of settlement data from the Densai net 110 is typically performed by daily batch, and settlement data is transmitted for each electronic bond whose due date comes.

  When the DRS 122 receives payment data from the Densai Net 110, the DRS 122 generates withdrawal data based on the received payment data and transmits it to the billing system 126. When the account system 126 receives the withdrawal data from the DRS 122, the account system 126 performs a withdrawal process of the amount of receivable from the settlement account of the underlying debtor (for example, the settlement account 128 of the underlying debtor A).

  The DRS 122 also transmits the settlement data received from the Densai net 110 to the exchange system 124. Upon receiving the settlement data, the exchange system 124 generates transfer data, and through the Zengin exchange network 130, the bank 140 system 140 (eg, the exchange system 144 having the settlement account of the creditor B, for example) ). Thereafter, when the bank bank exchange system 144 receives the transfer data, the account system 146 performs the process of depositing the credit amount into the creditor's settlement account (for example, the account 148 of the creditor B).

  If the electronic bond is split, settlement data is sent from Densai Net 110 for each of the original electronic bond (parent loan) and split bond (child loan), and DRS 122 Perform a withdrawal process like this. The payment date of the split receivables is the same as the due date of the original electronic receivables. Therefore, the settlement data for the original electronic receivables and the split receivables will be sent from Densai Net 110 on the same day. Withdrawal processing as described above for multiple receivables, withdrawing multiple times on the same day from the same obligor's account (ie, for each of the original electronic receivables and split receivables) Become. Such processing is not efficient and can be confusing and troublesome for the underlying debtor. Therefore, in the present invention, when the original obligor of the split receivable is the same (that is, when the original electronic receivable is the same), the DRS 122 combines the settlement data of the individual split receivables and performs the withdrawal process as one receivable. .

  By the way, the record number of each electronic bond is assigned by the electronic bond recording organization when the electronic bond is recorded. When the electronic bond is divided and the occurrence record of the divided bond (child loan) is performed, a new record number is assigned to the child bond. The record number associated with the record number of the parent claim is assigned to the record number of the child claim so that the original electronic claim (parent claim) can be identified. In one example, a number obtained by changing only the last digit of the record number of the parent claim is assigned as the record number of the child claim.

  Next, with reference to FIG. 2, a settlement process for split bonds according to an embodiment of the present invention will be described. In the embodiment of FIG. 2, creditor B divides 10,000 yen into C company and 90,000 yen into D company among 200,000 yen electronic receivable “A111” with company A as the underlying debtor. It shall be transferred. When the occurrence record of each split bond is performed, a record number is assigned to each split bond by the electronic bond recording organization. As stated above, the record number of the split receivable (child receivable) is the same as the part of the parent receivable record number for identifying the original electronic receivable (parent receivable) (for example, the upper x digit). For example, it is composed of a part unique to a child credit different from the record number of the parent claim, such as changing the last digit from the record number of the parent claim. Therefore, a group of related electronic receivables including the parent receivable and the child receivable divided from the parent receivable can be specified by the common part of the record number. In the example of FIG. 2, the record number “A112” is assigned to the child receivable dividedly transferred from the electronic receivable “A111” as the parent receivable to the creditor C, and the record number “A112” is assigned to the child receivable dividedly transferred to the creditor D. A113 ”is assigned, and in this example, the three related electronic bonds can be specified by the common part“ A11 ”of the record number. For ease of explanation, in this specification, the record number is represented by a simplified number, but the record number is actually a predetermined number of digits according to the agreement of the electronic bond recording organization. (20 digits). Therefore, the common part is also actually composed of a predetermined number of digits, for example, the first 19 digits of the recording number.

  When the due date comes, the settlement data of the parent loan A111, the child bond A112, and the child bond A113 are transmitted from the Densai net 110 to the DRS 122. The payment date of the split receivable is the same date as the payment date of the original electronic receivable, and the settlement data is transmitted on the same date. The DRS 122 identifies the settlement data of the child loans divided from the same parent receivable from among the settlement data transmitted individually as described above, and combines it with the settlement data of the original parent receivable to obtain a single withdrawal data. Create For example, the DRS 122 uses a common part (for example, “A11”) of the record numbers included in each settlement data, and the related group of electronic bonds (that is, the parent loan A111, the child bond A112, and the child bond A113). Extract payment data. Next, the amount of receivables included in the settlement data of the subordinated receivables (the amount of receivables of subordinated receivable A112: 10,000 yen and the amount of receivables of subordinated credit A113: 90,000 yen) ) To generate withdrawal data in which the total amount (200,000 yen) is set, and passes it to the accounting system 126. Next, the accounting system 126 deducts the total amount (200,000 yen) from the settlement account of the original obligor A as the amount of electronic receivable A111 based on the generated withdrawal data. Accordingly, the same withdrawal as when the withdrawal process is performed without dividing the electronic bond (FIG. 1) is performed from the settlement account of the underlying debtor A.

  On the other hand, regarding the deposit process, the DRS 122 transmits the individual settlement data to the exchange system 124 without combining them. The exchange system 124 creates transfer data based on the payment data received from the DRS 122, and transmits the transfer data to the bank system having the payment account of each creditor via the Zengin Exchange Network 130.

  With reference to FIG. 3, the flow of the settlement process for installment claims according to an embodiment of the present invention will be described.

  In step S <b> 310, the DRS 122 of the bank system 120 receives electronic bond settlement data from the Densai net 110. For electronic receivables that are due for payment, payment data including the settlement date, the underlying debtor's settlement account information, user number, electronic debt record number, credit amount, payment date, creditor's settlement account information, etc. It is generated by the Densai net 110 and transmitted to the DRS 122 in a daily batch or the like.

  In step S312, the DRS 122 temporarily stores the payment data received from the Densai net 110 on the day.

  In step S314, the DRS 122 determines whether or not the payment data for the split bond is included in the received payment data based on the recording number included in each payment data. When the payment data for the split bond is included, the DRS 122 Next, in step S316, based on the record number included in the settlement data, the original electronic bond and one or more split bonds divided from the same electronic bond are identified. Each electronic bond is identified by a unique record number, and the record number of the split loan consists of a common number with a predetermined number of digits common to the parent loan and a number of predetermined digits unique to the split bond . The DRS 122 can identify the original electronic bond and the divided bond divided from the same electronic bond by extracting the payment data including the record number having the same common number from the received payment data.

  In step S318, the DRS 122 adds the amount of receivable of each split receivable to the amount of receivable of the parent receivable, and generates withdrawal data in which all amounts of receivable are added. The total amount included in the withdrawal data matches the amount of the original electronic bond before the split.

  After generating the withdrawal data, the DRS 122 passes the withdrawal data to the billing system 126 in step S320.

  Thereafter, in step S322, the accounting system 126 deducts the total amount from the settlement account of the underlying debtor, such as the settlement account 128 of the underlying debtor A, based on the withdrawal data received from the DRS 122.

  In step S324, when the DRS 122 passes each settlement data to the exchange system 124, then in step S326, the exchange system 124 transfers the transfer data from the settlement data to each creditor's settlement account. And transfer data to the Zengin Exchange Network 130. The transfer data is transmitted to a bank system (for example, Y bank system 140, Z bank system 250) having a settlement account of each creditor via the Zengin Exchange Network 130, and an exchange system such as an exchange system 144, 254 or the like. As a result, each credit amount is deposited into the settlement account of each creditor.

  According to the above, for the obligor, the total amount equal to the amount of the original electronic receivable before the split is not deducted from the receivable amount of the parent receivable and individual receivables. While it can be withdrawn in a lump sum, the credit amount of the split receivable can be appropriately transferred to creditors.

  By the way, the remittance settlement of electronic receivables between accounts is performed by “transfer transaction” via a Zengin exchange. The withdrawal of the credit amount from the settlement account of the obligor is treated as “transfer withdrawal”, and the deposit amount of the credit amount to the settlement account of the creditor is treated as “transfer deposit”. For this reason, when the account information is queried, these deposits and withdrawals are presented as “transfer” transactions, and the underlying debtor and creditor have either made a normal transfer, or have withdrawn or deposited the credit amount of the electronic credit. It is impossible to determine at a glance whether this was done.

  Therefore, in order to solve such a problem, in the second embodiment of the present invention, the transaction classification is clarified so that the electronic bond transfer on the Densai Net can be distinguished from the normal transfer. A second embodiment of the present invention will be described with reference to FIGS. FIG. 4 is a diagram showing a system environment for implementing transaction category conversion according to the second embodiment of the present invention, and FIG. 5 is a flowchart showing a flow of transaction category conversion processing.

  As shown in FIG. 4, in this embodiment, the Y bank system 140 in which the creditor has a settlement account includes a conversion DB 442 in the exchange system 144. The conversion DB 442 converts the transaction classification of the transfer data so that the transfer of Densai Net can be distinguished from the normal transfer. When the exchange system 144 receives the transfer data from the Zengin Exchange Network 130, the conversion DB 442 determines whether the received transfer data is a Densai Net transfer. In the case of Densai Net, the record number of the electronic bond is included in a predetermined field (for example, EDI information) in the transfer data. Therefore, the conversion DB 442 can determine whether the transfer data is a normal transfer or a transfer on the Densai Net depending on whether or not the record number is included in a predetermined field in the transfer data. it can. In the case of a Densai Net transfer, the conversion DB 442 converts the transaction category of the transfer data to indicate that it is a Densai Net transfer (for example, from “Transfer” to “Densai”). ). When the transaction classification is converted by the conversion DB 442, the converted transfer data is transmitted from the exchange system 144 to the account system 146 and the electronic banking (EB) host 443. Thereafter, the account system 146 deposits the credit amount into the creditor's settlement account (for example, creditor B's settlement account 148). On the other hand, when the record number is not included in the transfer data, the conversion DB 442 determines that the transfer is a normal transfer by the transfer requester, and a normal transfer process is performed by the exchange system 144. In the example of FIG. 4, the conversion DB 442 is illustrated to be included in the exchange system 144, but may be configured to be provided separately from the exchange system 144.

  Next, with reference to FIG. 5, the flow of the transaction classification conversion process will be described.

  In step S <b> 510, the exchange system 144 receives the transfer data via the Zengin exchange network 130.

  In step S512, the exchange system 144 passes the received transfer data to the conversion DB 442.

  In step S514, the conversion DB 442 determines whether or not the electronic bond record number is set in a predetermined field of the transfer data. When the recording number is not set in the transfer data, the process proceeds to step S516 and is processed as a normal “transfer”.

  On the other hand, when the record number is set in the transfer data, the process proceeds to step S518, and the conversion DB 442 displays “Transfer” to indicate that the transfer data transaction classification is a transfer of Densai Net. To "Densai".

  When the transaction classification is converted to “Densai”, the exchange system 144 passes the converted transfer data to the account system 146 and the EB host 443 (steps S520 and S522).

  According to the above, when the creditor inquires about his / her account information by, for example, the EB service, the transfer deposit made to his / her account is, for example, a transfer requester (for example, from the transfer requester S) It is possible to recognize whether the transfer amount is a transfer deposit of the amount of receivable (for example, from the obligor A).

  Further, in a further embodiment of the present invention, the transaction classification can be converted so as to indicate that the transfer amount from the settlement account on the debtor side is a withdrawal of the amount of the electronic bond. For example, the bank system 120 on the obligor side can include a conversion DB (not shown) in the DRS 122. When the DRS 122 receives the settlement data from the Densai Net 110, the DRS 122 generates withdrawal data to be provided to the account system 126 based on the received settlement data. Can be converted from “transfer” to “densai”. Next, the account system 126 can withdraw the receivable amount from the settlement account of the underlying debtor based on the withdrawal data whose transaction classification is converted to “Densai”. Thereby, when the obligor inquires about the information of his / her settlement account, the obligor can recognize that the credit amount of the electronic receivable has been deducted from his / her account. In another embodiment, the conversion DB may be provided separately from the DRS 122 in the banking system on the debtor side.

  In this specification, the case where the electronic receivable is divided and transferred to different creditors has been described. However, when the split receivable is transferred to the same creditor, the funds summed up using the present invention are similarly applied. Can be withdrawn.

110 Densai Net 120 Debt Bank System 122 Densai Net Cooperation System (DRS)
124 Foreign exchange system 126 Account system 128 Primary debtor's settlement account 130 Zengin exchange network 140, 250 Creditor's banking system 144, 254 Foreign exchange system 146, 256 Account system 148, 258 Creditor's settlement account 442 Conversion DB
442 Electronic Banking (EB) Host 460 Bank system on the client side

Claims (5)

A computer system for performing payment processing by combining settlement data of installment receivables,
Means for receiving settlement data including the original debtor of the electronic bond, the creditor, the amount of the bond, and the record number from the electronic bond recording organization ;
Based on the record number in the settlement data, it is determined whether or not the settlement data received includes settlement data for split receivables. A means for identifying a split claim , wherein the record number of the split claim comprises a common number for identifying the parent claim of the split claim and a number unique to the split claim, and the received settlement data A means for identifying payment data including a record number having the same common number ,
Means for generating withdrawal data by adding the amount of receivable included in the settlement data of the identified split receivable to the amount of receivable included in the settlement data of the parent receivable;
And a means for performing a withdrawal process of the combined amount from the settlement account of the obligor based on the generated withdrawal data.   2. The system according to claim 1, wherein the means for generating the withdrawal data sets a transaction category of the withdrawal data so as to indicate that the withdrawal amount of the electronic bond is a withdrawal amount. A method for performing withdrawal processing by combining settlement data of installment receivables,
Receiving payment data from an electronic bond recording institution including an original debtor of an electronic bond, a creditor, a bond amount, and a record number;
Based on the record number in the settlement data, it is determined whether or not the settlement data received includes settlement data for split receivables. A step of identifying a split claim , wherein the record number of the split claim comprises a common number for identifying a parent claim of the split claim and a number unique to the split claim, and the received settlement data Identifying the payment data including the record number having the same common number ,
Generating withdrawal data by adding the amount of receivable included in the settlement data of the identified split receivable to the amount of receivable included in the settlement data of the parent receivable;
Performing a withdrawal process of the summed amount from the settlement account of the underlying debtor based on the generated withdrawal data. The step of generating the payment data, to indicate that a withdrawal of the claim amount of electronic claims, according to claim 3, characterized in that it comprises setting the trading section of the dispensing data Method. A program for causing a computer to execute a process for performing a withdrawal process by combining settlement data of installment receivables,
Receiving payment data from an electronic bond recording institution including an original debtor of an electronic bond, a creditor, a bond amount, and a record number;
Based on the record number in the settlement data, it is determined whether or not the settlement data received includes settlement data for split receivables. A step of identifying a split claim , wherein the record number of the split claim comprises a common number for identifying a parent claim of the split claim and a number unique to the split claim, and the received settlement data Identifying the payment data including the record number having the same common number ,
Generating withdrawal data by adding the amount of receivable included in the settlement data of the identified split receivable to the amount of receivable included in the settlement data of the parent receivable;
And a step of performing a withdrawal process of the summed amount from the settlement account of the obligor based on the generated withdrawal data.

Images