JP4494183B2 - Claim management system, control method of debt management system, and program - Google Patents

Description

  The present invention relates to a claim management system, a control method for a claim management system, and a program.

  With recent advances in information technology, various technologies for electronically distributing monetary values such as bills and claims (hereinafter also simply referred to as claims) have been developed (for example, Patent Literature 1 and Patent Literature). 2).

  These techniques can be roughly classified into two types depending on the method. One is a method where a third-party organization called a transfer organization centrally manages the contents of the receivables and information on who owns them (electronic bond distribution that distributes receivables electronically using this method) The system is also referred to as a book entry system). The other is a method in which electronic data representing the contents of a claim is stored in an IC card, etc., and the electronic data stored in the IC card etc. is distributed between traders. The electronic bond distribution system is also referred to as an IC card type system).

  In Patent Document 1, as a technique for realizing a book entry type system, a server computer on a network manages electronic check information in a database for each member, and transfer of electronic checks occurs between members. Discloses a technique for transferring information on a subject electronic check from a transferee's account to a transferee's account on a database.

In Patent Document 2, as a technology for realizing an IC card type system, the exchange of electronic checks is realized by communication between parties without using a third party such as a certification authority for registering electronic checks. Techniques to do this are disclosed.
Japanese Patent Laid-Open No. 2001-273452 Japanese Patent No. 3365599

In this way, two methods have been developed to distribute receivables electronically, but electronic receivables are expected to have a large number of issuers and issuances. Since there is a need for coordination between interested parties such as banks undertaking issuance, each type of electronic bond distribution system is considered to coexist.
In this case, since the electronic bond issued in one electronic bond distribution system cannot be distributed in the other electronic bond distribution system, the distribution range of the electronic bond is limited. This would be a system that is inconvenient for creditors who want to distribute their credits widely.
Therefore, a technique for distributing electronic bonds between electronic bond distribution systems of various methods is desired.

  The present invention has been made in view of the above-mentioned problems, and a main object of the present invention is to provide a system capable of distributing electronic bonds between a book entry type bond distribution system and an IC card type bond distribution system. And

One aspect of the present invention for achieving the above object is a first claim management system communicatively connected to a second claim management system and a third claim management system, wherein the first claim As information indicating that a claim has been transferred between a member of the management system and a member of the second claim management system, a second that describes the claim according to the second standard in the second claim management system A first claim correspondence management table for storing a first record in which claim transfer information is associated with first claim transfer information in which the claim is described in accordance with a first standard in the first claim management system; As information indicating that a claim has been transferred between a member of the first claim management system and a member of the third claim management system, the first claim transfer information describing the claim and the note A second claim correspondence management table that stores a second record that associates with the third claim transfer information described in accordance with the third standard in the third claim management system, and When a request to transfer a claim from the claim management system to the third claim management system is received from a member of the second claim management system, both the first and second claim correspondence management tables If there is no record describing the first claim transfer information for the claim, the second record for the claim is stored in the second claim management table, and the claim for the claim is stored. The third receivable transfer information is transmitted to the third receivable management system.

  In addition, the problems disclosed by the present application and the solutions thereof will be clarified by the column of the best mode for carrying out the invention and the drawings.

  It is possible to provide a receivable management system that can distribute electronic receivables between a book entry receivable distribution system and an IC card receivable distribution system, a control method for the receivable management system, and a program.

=== Example of Overall Configuration ===
<Book entry type electronic bond system>
FIG. 1 shows an X-type electronic bond system including a transfer server (X) 200 (corresponding to the first bond management system described in claims) according to the present embodiment. The X system electronic bond system is a book entry type electronic bond distribution system. As will be described in detail later, the transfer server (X) 200 has an account information table 700 that stores each member in association with identification information of the member and data that proves the claim owned by the member. The transfer of the bond between the members is managed by changing the identification information of the member associated with the data to be certified from the identification information of the original owner of the bond to the identification information of the new owner.

  The data certifying the bond is described in accordance with a standard (corresponding to the first standard described in the claims, hereinafter also referred to as standard X) applied in the X-type electronic bond system.

  Each member uses the transfer server user terminal (corresponding to the member terminal described in the claims) 300 of each member to register the generated receivables and buy and sell receivables with respect to the transfer server (X) 200. Instructing reimbursement, etc. FIG. 1 illustrates “k” and “k ′” as members of the X-type electronic bond system.

  The transfer server (X) 200 is communicably connected to a bank server (corresponding to an information processing system possessed by a financial institution described in claims) 600 via a network 400. In the example shown in FIG. 1, a P bank server 600, a Q bank server 600, and an R bank server 600 are illustrated. When the transfer server (X) 200 receives an instruction to redeem the credit from the transfer server user terminal 300 of the member, the credit server designates the bank server 600 from the bank account of the debtor. Send money transfer request to the bank transfer account.

<IC card type electronic bond system A>
The A-type electronic bond system is an IC card type electronic bond distribution system. In the A system electronic bond system, the transfer of the bond between the owners of each IC card is managed by moving the data that certifies the bond between the IC cards that record the data that certifies the bond.

  The data for certifying the bond is described in accordance with a standard (corresponding to the second standard or the third standard described in the claims, hereinafter also referred to as the standard A) applied in the A-system electronic bond system. For this reason, data certifying a bond cannot be distributed between the X-type electronic bond system and the A-type electronic bond system.

  Data for certifying a bond is transferred using an IC card (A) user terminal 100 that each member of the A-type electronic bond system has. In other words, a member of the A method electronic credit system, when transferring his own receivable to another member, attaches his own IC card (A) 120 to the IC card (A) reader / writer 110, The IC card (A) user terminal 100 is used to transmit data certifying the credit to the IC card (A) user terminal 100 owned by the assignee. The IC card (A) user terminal 100 owned by the assignee writes the transmitted data to the IC card (A) 120 attached to the IC card (A) reader / writer 110. Thereby, transfer of the claim between the owners of the IC card (A) 120 is performed. FIG. 1 exemplifies “a” and “a ′” as members of the A-type electronic bond system.

  FIG. 2A shows an example of data exchanged between the IC card (A) user terminals 100 of the respective owners when the receivables are transferred between the owners of the IC card (A) 120. In FIG. 2A, the portion of the electronic bond data (A) corresponds to data for certifying the bond. The electronic bond data (A) is encrypted according to a standard applied in the A-type electronic bond system, and can only be read from and written to the IC card (A) 120 using the IC card (A) reader / writer 110. Also, it cannot be duplicated. Therefore, the electronic bond data (A) cannot be exchanged with another type of electronic bond system.

  The electronic bond data (A) is added with control data used when each member of the A-type electronic bond system performs a bond transaction. This control data includes data indicating the contents of the bond certified by the electronic bond data (A). The control data is displayed on an output device such as a display provided in the IC card (A) user terminal 100 as necessary at the time of bond transaction, and whether or not a member of the A-type electronic bond system performs the bond transaction. It is used as information when making decisions. For example, in the control data, as illustrated in FIG. 2A, “electronic bond method”, “bond ID”, “transaction type”, “creditor”, “obligor”, “credit” Information indicating “amount”, “payment date”, “debtor's bank account”, “transferer”, “transferee”, and “transfer account” is described as necessary.

  In the A system electronic bond system, each IC card (A) user terminal 100 is connected to a settlement center (A) server 500 via a network 400 so as to be communicable. The settlement center (A) server 500 is communicably connected to the bank server 600 via the network 400.

  Each member of the A-type electronic bond system uses the IC card (A) user terminal 100 to redeem the claims recorded on the IC card (A) 120 owned by the member. Instructs 500 to redeem the bond. The settlement center (A) server 500 transmits a money transfer request from the debtor's bank account to the bank transfer account designated by the creditor to the bank server 600.

<IC card type electronic bond system B>
The B-type electronic bond system is an IC card type electronic bond distribution system similar to the A-type electronic bond system. That is, in the B-system electronic bond system, the transfer of the bond between the owners of each IC card is managed by moving the data that certifies the bond between the IC cards that record the data that certifies the bond.

  However, the data for certifying the bond is different from the standard applied in the A-type electronic bond system, and the standard applied in the B-type electronic bond system (corresponding to the second standard or the third standard described in the claims) (Hereinafter also referred to as standard B). For this reason, the A-system electronic bond system and the B-system electronic bond system are both IC card-type bond distribution systems, but cannot mutually distribute data certifying bonds. In addition, it is not possible to circulate data for certifying a mutual bond between the X-type electronic bond system and the B-type electronic bond system.

  Data for certifying a bond is transferred using an IC card (B) user terminal 100 that each member of the B-type electronic bond system has. In other words, a member of the B-type electronic credit system, when transferring his own receivable to another member, attaches his own IC card (B) 120 to the IC card (B) reader / writer 110 and The IC card (B) user terminal 100 is used to transmit data certifying the credit to the IC card (B) user terminal 100 owned by the assignee. The IC card (B) user terminal 100 owned by the assignee writes the transmitted data to the IC card (B) 120 attached to the IC card (B) reader / writer 110. Thereby, transfer of the claim between the owners of the IC card is performed. FIG. 1 illustrates “b” and “b ′” as members of the B-type electronic bond system.

  FIG. 2B shows an example of data exchanged between the IC card (B) user terminals 100 of the respective owners when the receivables are transferred between the owners of the IC card (B) 120. In FIG. 2B, the electronic bond data (B) corresponds to data for certifying the bond. The electronic bond data (B) is encrypted according to the standard applied in the B-type electronic bond system, and can only read and write to the IC card (B) 120 using the IC card (B) reader / writer 110. Also, it cannot be duplicated. Therefore, the electronic bond data (B) cannot be exchanged with another type of electronic bond system.

  The electronic bond data (B) is added with control data used when each member of the B-system electronic bond system performs a bond transaction. This control data includes data indicating the contents of the bond certified by the electronic bond data (B). The control data is displayed on an output device such as a display provided in the IC card (B) user terminal 100 as necessary at the time of bond transaction, and whether or not a member of the B-type electronic bond system performs the bond transaction. It is used as information when making decisions. For example, as illustrated in FIG. 2B, the control data includes “electronic bond method”, “bond ID”, “transaction type”, “creditor”, “obligor”, “credit Information indicating “amount”, “payment date”, “debtor's bank account”, “transferer”, “transferee”, and “transfer account” is described as necessary.

  In the B-type electronic bond system, each IC card (B) user terminal 100 is connected to a settlement center (B) server 500 via a network 400 so as to be communicable. The settlement center (B) server 500 is communicably connected to the bank server 600 via the network 400.

  Each member of the B-type electronic bond system uses the IC card (B) user terminal 100 to redeem the bond recorded on the IC card (B) 120 owned by the member. Instructs 500 to redeem the bond. The settlement center (B) server 500 transmits a money transfer request from the debtor's bank account to the bank transfer account designated by the creditor to the bank server 600.

<Network>
The network 400 can be a local area network (LAN), the Internet, or any other wired or wireless communication network.

=== Configuration of the transfer server ===
Next, the configuration of the transfer server (X) 200 is shown in FIG. The transfer server (X) 200 according to the present embodiment includes a CPU (Central Processing Unit) 210, a memory 220, a port 230, a recording medium reading device 240, an input device 250, an output device 260, a storage device 280, and an A method electronic bond. A data storage device 290 and a B-type electronic bond data storage device 290 are provided.

  The CPU 210 is responsible for overall control of the transfer server (X) 200, and executes the transfer server control program 800 composed of codes for performing various operations according to the present embodiment stored in the storage device 280. Thus, various functions as the transfer server (X) 200 according to the present embodiment are realized. For example, the transfer server control program 800 is executed by the CPU 210 and transferred to an external bond by cooperating with hardware devices such as the memory 220, the port 230, the recording medium reading device 240, the input device 250, the output device 260, and the storage device 280. Request receiving unit, first standard data generation unit, assignment receivable registration unit, assignment receivable correspondence table search unit, assignment association information addition unit, second standard data deletion unit, association information deletion unit, transfer error transmission unit , Internal receivable transfer request receiving unit, transfer receivable correspondence table search unit, second standard data generating unit, internal receivable transfer request transmitting unit, transfer association information adding unit, transferred receivable erasing unit, transfer error transmitting unit, third Standard data generator, Receivables redemption request receiver, Receivables receivables correspondence table search part, Receivables redemption request transmitter, Redeemable debt elimination part, Second standard data Erasing unit is realized.

The memory 220 can be constituted by a semiconductor memory device, for example.
The recording medium reading device 240 is a device for reading a program and data recorded on the recording medium 270. The read program and data are stored in the memory 220 and the storage device 280. Therefore, for example, the transfer server control program 800 recorded on the recording medium 240 can be read from the recording medium 240 and stored in the memory 220 or the storage device 280.
As the recording medium 240, a flexible disk, a magnetic tape, a compact disk, or the like can be used. The recording medium reading device 240 may be built in the transfer server (X) 200 or may be externally attached.
The storage device 280 can be, for example, a hard disk device or a semiconductor storage device. The storage device 280 stores a transfer server control program 800, an account information table 700, and a bond correspondence management table 710.

  An account information table 700 is shown in FIG. In the account information table 700, member identification information is associated with data certifying a claim owned by a member described in accordance with the standard X (corresponding to data of the first standard described in claims) for each member. Is remembered. Specifically, the account information table 700 includes a “member No.” field, a “date” field, a “creditor ID” field, a “obligor” field, a “creditor amount” field, a “payment date” field, a “obligor payment” field. “Account” field. The data described in the “obligor” column, “credit amount” column, “payment date” column, and “obligor payment account” column corresponds to the data that certifies the bond.

  In the “member No.” column, identification information of each member such as an identification number assigned to each member is described. Identification information for identifying data indicating each bond granted by the transfer server (X) 200 is written in the “bond ID” column. In the “date” column, information indicating the date when data certifying the credit specified by the credit ID is stored in the account information table 700 is described. In the “obligor” column, information for identifying the obligor is stored. Information indicating the amount of debt is written in the “Amount of Receivable” column. In the “Payment due date” column, information indicating the due date for paying the debt is written. In the “obligor payment account” column, information indicating an account of a financial institution used as a transfer source when the debtor repays the debt is described.

  A bond correspondence management table 710 is shown in FIG. The claim correspondence management table 710 will be described later.

The input device 250 is a device used for data input to the transfer server (X) 200 and functions as a user interface. For example, a keyboard or a mouse can be used as the input device 250.
The output device 260 is a device for outputting information to the outside and functions as a user interface. For example, a display or a printer can be used as the output device 260.

  The port 230 is a device for communicating with other computers. For example, communication with the transfer server user terminal 300 and the bank server 600 can be performed via the network 400. Further, in transfer server (X) 200 according to the present embodiment, IC card (A) user terminal 100, settlement center (A) server 500, IC card (B) user terminal 100, settlement center (B) server. 500 can also communicate. Further, for example, the transfer server control program 800 may be received from another computer via the network 230 through the port 230 and stored in the memory 220 or the storage device 280.

  An A-type electronic bond data storage device (corresponding to the second standard data recording unit or the third standard data recording unit described in claims) 290 is a bond written in accordance with a standard applied in the A-type electronic bond system It is a device for recording data proving that. A type A electronic bond data storage device 290 is shown in FIG. The A-system electronic bond data storage device 290 includes an IC chip control unit 291 and an IC chip 292. The IC chip 292 is the same as the IC chip built in the IC card 120 used in the A-system electronic bond system or an IC chip 292 that complies with the standard applied in the A-system electronic bond system. The IC chip control unit 291 is a device for reading / writing data from / to the IC chip 292 in accordance with a standard applied in the A-system electronic bond system.

  As described above, the A-system electronic bond data storage device 290 reads and writes data for certifying the bond to the IC chip 292 according to the standard applied in the A-system electronic bond system. Therefore, the transfer server (X) 200 according to the present embodiment exchanges data indicating the electronic bond stored in the IC card (A) 120 with the IC card (A) user terminal 100. Can do.

  The A-system electronic bond data storage device 290 can also be constituted by an IC card (A) reader / writer 110 as shown in FIG. In this case, as shown in FIG. 5, the IC chip control unit 291 provided in the IC card (A) reader / writer 110 reads / writes data from / to the IC chip 292 provided in the IC card (A) 120.

  A B-type electronic bond data storage device (corresponding to the second standard data recording unit or the third standard data recording unit described in claims) 290 is a bond written in accordance with a standard applied in the B-type electronic bond system It is a device for recording data proving that. The configuration is the same as that of the A-system electronic bond data storage device 290 and is shown in FIG. 4 or FIG. Then, the B-system electronic bond data storage device 290 reads and writes data certifying the bond to the IC chip 292 according to the standard applied in the B-system electronic bond system, whereby the transfer server (X ) 200 can exchange data indicating the electronic bond stored in the IC card (B) 120 with the IC card (B) user terminal 100.

  The claim correspondence management table 710 associates claims received from other electronic bond distribution systems, claims transferred to other electronic bond distribution systems, and claims generated and distributed in the own distribution system. It is a table that manages. Specifically, the identification information attached to the data certifying the X standard receivable and the identification information attached to the data certifying the A standard or B standard receivable corresponding to the data certifying the X standard receivable And the data certifying the A standard or B standard receivable is transmitted from the A method electronic receivable system or the B method electronic receivable system, or transmitted to the A method electronic receivable system or the B method electronic receivable system. Information indicating whether it is a thing is stored in association with each other.

  In the example shown in FIG. 7, the first line is a bond with a code (identification information) “001” in an IC card type electronic bond distribution system (A method electronic bond system) of the standard “A”. Is distributed with the code (identification information) of “X001” in the self-distribution system (X method electronic bond system), and then to the IC card type electronic bond distribution system (B method electronic bond system) of the standard “B” On the other hand, it has been transferred as a claim of the code (identification information) “001”. The second line shows that the credit of the code “002” is transferred from the IC card type electronic credit distribution system of the standard “A” and is currently distributed in the distribution system with the code “X002”. The third line indicates that the credit that was distributed by generating the credit of the code “X003” in the distribution system was transferred to the electronic credit distribution system of the standard “B” as the credit of code “003”. ing.

=== Flow of processing ===
In the following, the electronic bond distribution system A (A type electronic bond system) and the electronic bond distribution system B (B type electronic bond system) are both IC card type, but the standards are different. The processing procedure will be described in detail for a method for distributing electronic bonds between the electronic bond distribution system X (X-type electronic bond system), the electronic bond distribution system A, and the electronic bond distribution system B in a situation where it is impossible. The following processing is executed by the CPU 210 in accordance with the transfer server control program 800 unless otherwise specified.

<Acquisition processing>
First, a case where an electronic bond is transferred from a user of the electronic bond distribution system A or B to a user of the electronic bond distribution system X will be described.
The user of the electronic bond distribution system A or B connects the IC card 120 to the IC card (A) user terminal 100 or the IC card (B) user terminal 100, and the transfer procedure in the standard of each electronic bond distribution system To implement. At that time, the identifier of the electronic bond distribution system X and the identifier of the transfer partner are input. Then, from the IC card (A) user terminal 100 or the IC card (B) user terminal 100 to the transfer server (X) 200, a transfer request for a claim owned by the IC card owner and the control data are included. Data of A standard or B standard for certifying a bond and identification information indicating a new owner of the bond are transmitted.

The IC chip control unit 291 receives an electronic bond (data for certifying a bond) in the IC chip 292 by a method defined by the transfer-side electronic bond distribution system. Thereafter, based on the control data shown in FIG. 2, an X standard electronic bond corresponding to the received electronic bond is generated.
FIG. 8 is a flowchart showing a series of processes executed thereafter. The flow of processing will be described in detail using this flowchart.

  First, the transfer server (X) 200 acquires the identifier of the electronic bond distribution system and the bond code of the received bond from the IC chip 292 through the IC chip control unit 291 (S1000). Hereinafter, when describing the exchange of data with the IC chip 292, the description that it is performed through the IC chip control unit 291 is omitted for the sake of simplicity. Here, if the identifier of the acquired electronic bond distribution system is “A” and the bond code is “004”, this information is retrieved from the bond correspondence management table 710 (S1010). Assuming that the claim correspondence management table 710 is as shown in FIG. 7, when a record in which the identifier of the electronic bond distribution system is recorded in the “standard” column and the bond code is recorded in the “code” column is searched, Does not exist (S1020). Therefore, the process proceeds to S1030.

  Then, the transfer server (X) 200 gives a new bond code “X004” based on the code system of the self-distribution system to the transferred bond (S1030). Then, the correspondence between the original claim code and the assigned claim code is recorded in the claim handling management table 710 (S1040). For the record, information on the transferred receivable is recorded in the “Accepted” column, and a code in the distribution system is recorded in the “Transferd receivable” column. Thereby, the claim correspondence management table 710 becomes as shown in FIG.

  Next, the transfer server (X) 200 checks the identifier of the transfer destination. If the transfer destination identifier indicates the user of the self-distribution system (S1080), the bond information is added to the account of the user indicated by the transfer destination identifier in the account information table 700 (S1090).

  If the transfer destination is another IC card type electronic bond distribution system (S1080), the process proceeds to (1) in FIG. This shows the case where the user of the electronic bond distribution system A passes the book entry type electronic bond distribution system when transferring the bond to the user of the electronic bond distribution system B. The IC card type electronic bond distribution system Can be realized by combining the transfer of credits to the book entry-type electronic bond distribution system and the reverse transfer. The process after the transition to (1) is the reverse transfer process referred to here, and details will be described later.

  Returning to the processing start, and considering that the identifier of the acquired electronic bond distribution system is “B” and the bond code is “003” (S1000), this information is retrieved from the bond management table 710 (S1010). . If the bond correspondence management table 710 is as shown in FIG. 7, the third line in FIG. 7 is extracted as a result of the search. In the “transfer” column, “B” and “003”, which are receivables to be transferred this time, are recorded (S1020). This indicates that the credit "X003" generated in the self-distribution system has been transferred to the electronic bond distribution system of the standard "B" with the code "003". This transfer was previously transferred It can be determined that the bond has been returned. Therefore, since the linkage with other distribution systems is canceled, this record is deleted from the bond management table 710 (S1060). Thereby, the claim correspondence management table 710 becomes as shown in FIG. Further, the electronic bond specified by the code “003” of the standard “B” recorded in the IC chip 292 is deleted (S1070). Next, the transfer server (X) 200 checks the identifier of the transfer destination. If the transfer destination identifier indicates the user of the self-distribution system (S1080), the bond information is added to the account of the user indicated by the transfer destination identifier in the account information table 700 (S1090). If the transfer destination is another IC card type electronic bond distribution system (S1080), the process proceeds to (1) in FIG.

  In S1020, an error is generated in cases other than the above two states. In particular, when the identifier of the acquired electronic bond distribution system is “A”, the bond code is “002”, and the bond management table 710 is as shown in FIG. 7, “A” and “002” have already been transferred, Since it can be seen from the record of the claim correspondence management table 710 that it is currently circulated in its own distribution system, it is found that the electronic claim acquired this time is a copy thereof. In this case, error processing is performed. For example, information indicating that the same electronic bond as the received electronic bond exists is transmitted to the credit management system that has transmitted the electronic bond.

<Transfer process>
Next, a case where an electronic bond is transferred from a user of the electronic bond distribution system X to a user of the electronic bond distribution system A or B will be described.
A user of the electronic bond distribution system X uses the transfer server user terminal 300 to execute a transfer procedure for the transfer server (X) 200. At that time, the user inputs the identifier of the electronic bond distribution system A or B, the claim ID of the transferred claim, and the identifier of the transfer partner. Then, the transfer server (X) 200 receives the transfer request for the receivable owned by the user, the identification information of the transferred receivable, and the identification information of the owner of the IC card indicating the new owner of the receivable. The
FIG. 11 is a flowchart showing a series of processes executed thereafter. The flow of processing will be described in detail using this flowchart.

  The transfer server (X) 200 acquires the claim code of the claim subject to the transfer procedure (S2000). Here, assuming that the acquired bond code is “X005”, first, the holder information of the bond of “X005” is deleted from the account information table 700. That is, it is changed so that no one holds it (S2010). Subsequently, this information is retrieved from the claim management table 710 (S2020). If the bond correspondence management table 710 is as shown in FIG. 7, when a record in which the bond code “X005” is recorded in the “transfer loan” column is searched, such a record does not exist (S2030). Therefore, the process proceeds to S2040.

  If the transfer destination is the electronic bond distribution system B, the IC chip controller 291 is instructed to generate a bond equivalent to the bond code “X005” with respect to the IC chip 292 corresponding to the transfer destination (S2040). Here, it is assumed that the bond is generated with a bond code of “005”. Information that the electronic bond distribution system X has been issued for redemption described later is also added. Further, the electronic bond distribution system B is instructed to transfer the generated bond in the IC chip to the partner designated by the identifier of the transfer partner (S2050). That is, data for certifying the generated credit in the IC chip is transmitted to the IC card (B) user terminal 100 owned by the transfer partner. After that, in the claim correspondence management table 710, as a new record, the claim code “X005” is recorded in the “transfer credit” column, and the standard “B” and the claim code “005” are recorded in the “transfer” column. As a result, the bond correspondence management table 710 is as shown in FIG.

  Next, consider a case where the claim code of the claim subject to the assignment procedure is “X002” and is transferred to the user of the electronic bond distribution system B. Furthermore, it is assumed that the claim correspondence management table 710 is as shown in FIG.

  After performing S2000 and S2010, when the corresponding data is searched in S2020, the second row is extracted (S2020). In the second line, “A” and “002” are recorded in the “Accept” column, which is a standard different from the electronic bond distribution system B of the transfer destination (S2030), so the process proceeds to S2070.

  The IC chip controller 291 is instructed to generate a bond equivalent to the bond code “X002” for the IC chip 292 corresponding to the electronic bond distribution system B of the transfer destination (S2070). Here, it is assumed that the bond is generated with a bond code of “002”. Information that the electronic bond distribution system X has been issued for redemption described later is also added. Further, the electronic bond distribution system B is instructed to transfer the generated bond in the IC chip to the partner designated by the identifier of the transfer partner (S2080). That is, data for certifying the generated credit in the IC chip is transmitted to the IC card (B) user terminal 100 owned by the transfer partner. Thereafter, the standard “B” and the bond code “002” are recorded in the “transfer” column of the record extracted in S2020 of the bond management table 710. As a result, the bond correspondence management table 710 is as shown in FIG.

  Next, consider a case where the claim code of the claim subject to the assignment procedure is “X002” and this is transferred to the user of the electronic bond distribution system A. Furthermore, it is assumed that the claim correspondence management table 710 is as shown in FIG. After performing S2000 and S2010, when the corresponding data is searched in S2020, the second row is extracted (S2020). In the second line, “A” and “002” are recorded in the “transfer” column, which is the same standard as the transfer destination electronic bond distribution system A (S2030), so the process proceeds to S2100.

 Since the receivable is originally transferred from the electronic receivable distribution system A, the electronic receivable that has been transferred and stored in the IC chip 292 may be transferred as it is. Accordingly, the electronic bond distribution system A is instructed from the IC chip 292 of the standard of the electronic bond distribution system A to transfer the corresponding bond “A” “002” to the partner designated by the identifier of the transfer partner ( S2100). That is, data for proving the credit in the IC chip 292 is transmitted to the IC card (A) user terminal 100 owned by the transfer partner. Thereafter, the record extracted in S2020 in the bond correspondence management table 710 is deleted. As a result, the bond correspondence management table 710 is as shown in FIG. Further, the corresponding record is deleted from the account information table 700.

<Redemption processing>
Next, I will explain the redemption procedure.
The redemption process begins with the application of redemption by the ultimate credit holder. The applicant may be a user of an IC card type electronic bond distribution system or a user of a book entry type electronic bond distribution system. First, the former case will be described.

  In order to redeem the receivables held by users of the electronic bond distribution system B, the IC card (B) user terminal 100 notifies the settlement center (B) 500 of the receivables and the transfer account information and applies for reimbursement. Suppose. The settlement center (B) 500 recognizes that the electronic bond is issued by the electronic bond distribution system X from the bond information, transmits the bond and the transfer account information to the transfer server (X) 200, and redeems the bond. Request.

  FIG. 15 is a flowchart showing a series of processing executed by the transfer server (X) 200 thereafter. The flow of processing will be described in detail using this flowchart.

  First, the transfer server (X) 200 obtains a claim code and a transfer account of a claim for which redemption is applied (S3000). Next, the acquired bond code is searched in the bond management table 710 (S3010). FIG. 7 shows the claim correspondence management table 710. When the claim code of the claim to be redeemed is “B” “003”, the record in the third row of the claim correspondence management table 710 is extracted (S3020). ). This record has a record in the “transfer receivable” column and the “transfer” column, and no record in the “transfer” column (S3020). Since this indicates that the bond is generated by the electronic bond distribution system X, the redemption process may be performed within the own distribution system. Therefore, the transfer server (X) 200 performs redemption processing based on the corresponding transfer receivable code “X003” and the transfer account information (S3030). That is, the transfer server (X) 200 transmits, to the bank server 600, a money transfer request corresponding to the debt amount from the bank account of the debtor to the bank transfer account designated by the creditor.

  Then, the transfer server (X) 200 deletes the record extracted in S3010 of the bond correspondence management table 710. Further, the corresponding record is deleted from the account information table 700. Further, the transfer server (X) 200 deletes the electronic bond specified by the code “003” of the standard “B” recorded in the IC chip 292.

Next, the case where the claim correspondence management table 710 is as shown in FIG. 7 and the claim codes of the receivable receivables are “B” and “001” will be described. In this case, in S3010, the record in the first row of the claim management table 710 is extracted (S3010). This record is recorded in all of the “transfer receivable” column, the “transfer” column, and the “transfer” column (S3020). This indicates that the receivable generated in the electronic bond distribution system A has been transferred to the electronic bond distribution system X and then transferred to the electronic bond distribution system B. You must follow the method. Therefore, first, the receivable receivable in the IC chip 292 of the standard of the electronic receivable distribution system A is specified from the receivable code “A” “001” recorded in the “assigned” column (S3050). Subsequently, the transfer server (X) 200 requests the settlement center (A) server 500 to redeem the claims with the claim codes “A” and “001” held in the IC chip 292. At that time, transfer account information is also communicated (S3060).
In S3020, if the status is other than the above, an error is returned.

 Next, a case where a user of the book entry type electronic bond distribution system makes a redemption application will be described. Assume that a user of the electronic bond distribution system X has made a reimbursement application by notifying the transfer server (X) 200 of the receivable and transfer account information from the transfer server user terminal 300 in order to redeem the receivable. You may register the transfer account in advance.

  FIG. 16 is a flowchart showing a series of processes executed thereafter. The flow of processing will be described in detail using this flowchart.

  First, the transfer server (X) 200 acquires a claim code and a transfer account of a claim for which redemption has been applied (S4000). Next, the acquired bond code is searched in the bond management table 710 (S4010). If the claim management table 710 is as shown in FIG. 7 and the credit code of the credit to be redeemed is “X005”, there is no corresponding record in the claim management table 710 (S4010, S4020). This indicates that the receivables generated by the electronic bond distribution system X may be redeemed in the normal electronic bond distribution system X in order to indicate that the bonds generated by the electronic bond distribution system X are distributed as they are. Therefore, the transfer server (X) 200 performs redemption processing based on the corresponding transfer receivable code “X005” and the transfer account information (S4030). That is, the transfer server (X) 200 transmits, to the bank server 600, a money transfer request corresponding to the debt amount from the bank account of the debtor to the bank transfer account designated by the creditor.

Next, the case where the claim correspondence management table 710 is as shown in FIG. 7 and the claim code of the redeemed credit is “X002” will be described. In this case, in S4010, the record in the second row of the bond correspondence management table 710 is extracted (S4010). This record is recorded in the “transfer” column and the “transfer receivable” column, but not in the “transfer” column (S4020). This indicates that the receivables generated by the electronic bond distribution system A have been transferred to the electronic bond distribution system X, and the redemption processing method in the electronic bond distribution system A must be followed. Therefore, first, the assigned receivable in the IC chip 292 of the standard of the electronic receivable distribution system A is specified from the receivable code “A” “002” recorded in the “assigned” column (S4050). Subsequently, the transfer server (X) 200 transmits the receivable of the receivable code “A” “002” held in the IC chip 292 and the transfer account information to the settlement center (A) server 500 and issues a reimbursement instruction. Perform (S4060). Then, the transfer server (X) 200 deletes the record extracted in S4010 of the bond management table 710. Further, the corresponding record is deleted from the account information table 700.
In S4020, if the status is other than the above, an error is returned.

  In this way, it becomes possible to perform redemption processing between electronic bond systems of different methods.

  Although the present embodiment has been described above, in the present embodiment, a book entry type bond distribution system is given a function as a member in an IC card type distribution system. Specifically, an IC chip 292 is held in a book entry type bond distribution system so that an IC card type electronic bond can be exchanged. Here, what is possessed may be any IC card-type electronic bond that can be received, or the IC card itself. In the case of a book entry type credit distribution system, when an electronic credit is transferred from an IC card type credit distribution system, the electronic credit is received by the IC chip 292 possessed, and the credit is generated and distributed in the system based on the credit. On the other hand, when transferring receivables to an IC card-type receivable distribution system, stop the distribution of receivables distributed in the system and generate the same rights as the receivables on the IC chip 292 Transfer. When it is desired to distribute a bond between a plurality of IC card type bond distribution systems having different standards, an IC chip 292 corresponding to each standard is held.

  By doing so, it becomes possible to distribute electronic bonds between the book entry type bond distribution system and the IC card type bond distribution system. In addition, the distribution of electronic bonds between IC card type bond distribution systems of different standards can be realized by a book entry type bond distribution system mediating.

  In general, when a due date comes, the debtor will be redeemed, which is an act of repaying the debt to the creditor. In the case of a book entry-type receivable distribution system, the redemption may be performed by settlement between bank accounts registered in the system. In the IC card-type receivable distribution system, a settlement center that takes over the settlement of IC card receivables. Will be used. In this case, the redemption procedure may differ depending on the credit distribution system. Therefore, when distributing electronic claims among multiple credit distribution systems, which credit distribution system is used by the creditor at the time of redemption. Regardless, the debtor must be able to carry out redemption procedures in the credit distribution system that generated electronic claims. It can be said that the distribution of receivables among multiple receivable distribution systems was realized only after this redemption procedure was completed.

  In the present embodiment, the correspondence relationship of which credit distribution system the book entry type credit distribution system has been assigned to and which credit distribution system has been assigned for each individual bond is managed. As a result, when the ultimate creditor holder at the time of redemption requests reimbursement in the credit distribution system that he / she uses, the debtor returns to the credit distribution system that generated the claim and pays the debtor It can be obtained.

  In addition, when distributing electronic bonds between electronic bond distribution systems of different methods, it is necessary to be able to detect illegal duplication of electronic bonds made in electronic bond distribution systems of other methods. In the embodiment, since the information on the receivables transferred from other receivable distribution systems is managed as described above, it is possible to detect the transfer of the duplicate by associating it with the information on the newly transferred receivables.

  As described above, according to the electronic bond system according to the present embodiment, when a plurality of electronic bond distribution systems having different specifications are launched, it is possible to meet the need to distribute bonds between the electronic bond distribution systems. .

  Although the best mode for carrying out the invention has been described above, the above embodiment is intended to facilitate understanding of the present invention and is not intended to limit the present invention. The present invention can be changed and improved without departing from the gist thereof, and the present invention includes equivalents thereof.

It is a figure which shows the system configuration | structure which concerns on this Embodiment. It is a figure which shows the data used in the IC card type electronic bond system which concerns on this Embodiment. It is a figure which shows the structure of the transfer server (X) which concerns on this Embodiment. It is a figure which shows the electronic bond data storage device which concerns on this Embodiment. It is a figure which shows the electronic bond data storage device which concerns on this Embodiment. It is a figure which shows the account information table which concerns on this Embodiment. It is a figure which shows the receivable correspondence management table which concerns on this Embodiment. It is a flowchart which shows the flow of the process which concerns on this Embodiment. It is a figure which shows the receivable correspondence management table which concerns on this Embodiment. It is a figure which shows the receivable correspondence management table which concerns on this Embodiment. It is a flowchart which shows the flow of the process which concerns on this Embodiment. It is a figure which shows the receivable correspondence management table which concerns on this Embodiment. It is a figure which shows the receivable correspondence management table which concerns on this Embodiment. It is a figure which shows the receivable correspondence management table which concerns on this Embodiment. It is a flowchart which shows the flow of the process which concerns on this Embodiment. It is a flowchart which shows the flow of the process which concerns on this Embodiment.

Explanation of symbols

100 IC card user terminal 110 IC card reader / writer 120 IC card 200 transfer server 210 CPU
220 memory 230 port 240 recording medium reading device 250 input device 260 output device 270 recording medium 280 storage device 290 electronic bond data storage device 291 IC chip control unit 292 IC chip 300 transfer server user terminal 400 network 500 settlement center server 600 bank server 700 Account information table 710 Claim management table 800 Transfer server control program

Claims (9)

A first claim management system communicatively connected to a second claim management system and a third claim management system,
Information indicating that a claim has been transferred between a member of the first claim management system and a member of the second claim management system according to the second standard in the second claim management system. A first claim that stores a first record that associates the described second claim transfer information with the first claim transfer information that describes the claim according to the first standard in the first claim management system. Correspondence management table,
As information indicating that a claim has been transferred between a member of the first claim management system and a member of the third claim management system, the first claim transfer information describing the claim and the claim A second claim correspondence management table for storing a second record in association with third claim transfer information described according to a third standard in the third claim management system;
Manage
When a request to transfer a claim from the first claim management system to the third claim management system is received from a member of the second claim management system, any one of the first and second claim management tables In addition, if there is no record describing the first claim transfer information for the claim, the second record for the claim is stored in the second claim management table, and the claim Sending the third claim transfer information for the third claim management system to
A loan management system characterized by this. The claim management system according to claim 1, further comprising:
A request for transfer of a claim from the first claim management system to the second claim management system is received from a member of the third claim management system as the third claim transfer information described in accordance with the third standard. When received, a record about the claim is stored in the first claim correspondence management table, and the record is the second claim transfer information described in accordance with the second standard. , Storing the second record for the claim in the second claim management table, and sending the second claim transfer information for the claim to the second claim management system
A loan management system characterized by this. The claim management system according to claim 1, further comprising:
A request for transfer of a claim from the first claim management system to the second claim management system is received from a member of the second claim management system as the second claim transfer information described in accordance with the second standard. When received, a record about the claim is stored in the first claim correspondence management table, and the record is the second claim transfer information described in accordance with the second standard. , Delete the record from the first claim management table, and send the second claim transfer information for the claim to the second claim management system
A loan management system characterized by this. A control method of a first bond management system that is communicably connected to a second bond management system and a third bond management system,
The first bond management system is
Information indicating that a claim has been transferred between a member of the first claim management system and a member of the second claim management system according to the second standard in the second claim management system. A first claim that stores a first record that associates the described second claim transfer information with the first claim transfer information that describes the claim according to the first standard in the first claim management system. Correspondence management table,
As information indicating that a claim has been transferred between a member of the first claim management system and a member of the third claim management system, the first claim transfer information describing the claim and the claim A second claim correspondence management table for storing a second record in association with third claim transfer information described according to a third standard in the third claim management system;
Manage
When a request to transfer a claim from the first claim management system to the third claim management system is received from a member of the second claim management system, any one of the first and second claim management tables In addition, if there is no record describing the first claim transfer information for the claim, the second record for the claim is stored in the second claim management table, and the claim Sending the third claim transfer information for the third claim management system to
A control method of a claim management system characterized by the above. A control method for a claim management system according to claim 4,
The first bond management system further includes:
A request for transfer of a claim from the first claim management system to the second claim management system is received from a member of the third claim management system as the third claim transfer information described in accordance with the third standard. When received, a record about the claim is stored in the first claim correspondence management table, and the record is the second claim transfer information described in accordance with the second standard. , Storing the second record for the claim in the second claim management table, and sending the second claim transfer information for the claim to the second claim management system
A control method of a claim management system characterized by the above. A control method for a claim management system according to claim 1,
The first bond management system further includes:
A request for transfer of a claim from the first claim management system to the second claim management system is received from a member of the second claim management system as the second claim transfer information described in accordance with the second standard. When received, a record about the claim is stored in the first claim correspondence management table, and the record is the second claim transfer information described in accordance with the second standard. , Delete the record from the first claim management table, and send the second claim transfer information for the claim to the second claim management system
A control method of a claim management system characterized by the above. In the first bond management system that is communicably connected to the second bond management system and the third bond management system,
Information indicating that a claim has been transferred between a member of the first claim management system and a member of the second claim management system according to the second standard in the second claim management system. A first claim that stores a first record that associates the described second claim transfer information with the first claim transfer information that describes the claim according to the first standard in the first claim management system. Correspondence management table,
As information indicating that a claim has been transferred between a member of the first claim management system and a member of the third claim management system, the first claim transfer information describing the claim and the claim A second claim correspondence management table for storing a second record in association with third claim transfer information described according to a third standard in the third claim management system;
Functions to manage
When a request to transfer a claim from the first claim management system to the third claim management system is received from a member of the second claim management system, any one of the first and second claim management tables In addition, if there is no record describing the first claim transfer information for the claim, the second record for the claim is stored in the second claim management table, and the claim A function for transmitting the third claim transfer information to the third claim management system
A program to realize The program according to claim 7,
In addition to the above functions, the first bond management system
A request for transfer of a claim from the first claim management system to the second claim management system is received from a member of the third claim management system as the third claim transfer information described in accordance with the third standard. When received, a record about the claim is stored in the first claim correspondence management table, and the record is the second claim transfer information described in accordance with the second standard. , A function of storing the second record for the claim in the second claim management table and transmitting the second claim transfer information for the claim to the second claim management system
A program that realizes The program according to claim 7,
In addition to the above functions, the first bond management system
A request for transfer of a claim from the first claim management system to the second claim management system is received from a member of the second claim management system as the second claim transfer information described in accordance with the second standard. When received, a record about the claim is stored in the first claim correspondence management table, and the record is the second claim transfer information described in accordance with the second standard. The function of deleting the record from the first claim management table and transmitting the second claim transfer information for the claim to the second claim management system
A program that realizes

Images