JP2016184340A - Automated rejection system for electronic recording credit transfer recording claim - Google Patents

Abstract

PROBLEM TO BE SOLVED: To reject the transfer recording claim of electronic recording credit associated with no assurance.SOLUTION: A method executed by a server computer connected with an electronic credit recording institution system includes the steps of: receiving transfer recording claim occurrence notification data, which includes assurance association information showing grant of assurance for electronic recording credit, for the electronic recording credit from an electronic credit recording institution system; determining whether assurance for the electronic recording credit is granted based on the assurance association information; and transmitting transfer recording claim rejection notification data to the electronic credit recording institution system on the basis of determination results whether assurance is granted or not.SELECTED DRAWING: Figure 3

Description

  The present invention relates to an electronic record receivable assignment record automatic exclusion system, and particularly to an electronic record receivable assignment record automatic request that rejects an assignment request for an electronic record receivable that is not accompanied by a guarantee. Concerning exclusion system.

  In place of the settlement using a conventional bill, settlement using an electronically recorded bond is increasing. Electronic record receivables become effective when they are registered in a record ledger managed by an electronic receivable recording organization. The user usually requests the occurrence of electronic record receivables through the window of each financial institution (hereinafter referred to as “window financial institution”).

  Users who wish to use electronically recorded receivables need to register their accounts through a system provided by the contact financial institution (hereinafter referred to as “banking system”). When an account is registered, a user number for identifying a user is allocated in the electronic bond recording institution, and user information including a user name is recorded in the record book of the electronic bond recording institution.

  When the account is registered, the user can make a request for recording of the occurrence of electronic record receivables. When an accrual record request is made, the banking system creates an accrual record request data file having a format common to all financial institutions and sends it to a system provided by the electronic bond recording institution (hereinafter referred to as “electronic bond recording institution system”). To do. In response to the receipt of the request data file, the electronic bond recording institution system adds the corresponding record ledger record to the electronic record receivable database of the electronic bond recording institution system, thereby generating the electronic record receivable become.

  Many window financial institutions provide an input interface for the user in their banking system, and the user can make the above described record request by using the input interface. Specifically, by inputting information such as creditor and debtor user numbers and settlement account information from the input interface, the above-described occurrence record request data file is created based on the information. .

Yamaguchi Bank, Ltd., “Transfer Densai”, [online], Yamaguchi Bank website, [March 3, 2015 search], Internet (URL: https://www.yamaguchibank.co.jp/corporate /densai/pdf/pdf_03.pdf) Aomori Bank, Ltd., “Densai Designation Permission Function”, [online], Aomori Bank Home Page, [March 3, 2015 Search], Internet (URL: http://www.a-bank.jp/ contents / houjin / densai / pdf / shitei_kyoka_kinou20131204.pdf) Iyo Bank, Ltd., “2. Receivables Recording Business, Bulk Record Request, Designated Permission Registration”, [online], Iyo Bank Home Page, [March 3, 2015 Search], Internet (URL: https: // www. iyobank.co.jp/library/new/main/houjin/densai/densai_manual_2-2-8.pdf)

  By the way, the electronic record receivable can be transferred to another person by requesting the transfer record. When a transfer record request is made, a user who becomes the transfer person requests a transfer record through the bank system a of the counter financial institution A, and the bank system a creates a transfer record request file, and the electronic bond recording institution system Send to. When the electronic bond recording institution system receives the transfer record request file, the bank system b of the window financial institution B of the user who becomes the transferee (the window financial institutions A and B may be the same financial institution), The transfer record request occurrence notification data is transmitted. If the user who becomes the transferee does not do anything after 5 business days have passed since the transfer record request occurrence notification data was sent (that is, no rejection notice is given), it is considered to have been accepted. (Acceptance), the transfer of the electronically recorded receivable is recorded in the record book of the electronic receivables recording institution system, and the transfer becomes effective (see Non-Patent Document 1).

  When requesting a transfer record, in principle, the transfer is recorded with the guarantee of the subject electronic record receivable (transfer guarantee record). However, it is also possible for the user who becomes the assignee of the electronic record receivable to request the transfer record without accompanying the guarantee, such as when the guarantee of the assignor is not required.

  For this reason, when the bank system accepts a transfer record request, a transfer record request without a guarantee may occur, including a case where a guarantee is not accompanied by mistake. Recognizing such a transfer record request is not preferable because it reduces the number of retrospective destinations of the user who is the transferee. This is mainly due to the fact that the transferee accepts without notice that the guarantee is not accompanied when the transfer record request occurs.

  As disclosed in Non-Patent Documents 2 and 3, register business partners in advance and do not accept requests for transfer records of electronically recorded receivables from users other than registered business partners (designated authorized customers) Is possible. However, this function rejects the transfer of electronic record receivables other than registered business partners, and does not reject the transfer record of electronic record receivables that are not accompanied by any guarantee.

  In addition, when the assignee notices that the guarantee is not accompanied and refuses the transfer record request for that reason, the transferee is notified of the rejection via the electronic bond recording institution system ( A notification data file indicating rejection is transmitted from the electronic bond recording institution system to the bank system a).

  FIG. 1 shows a data format of a notification data file transmitted from the electronic bond recording institution system to the bank system a. When the transferee rejects the request for transfer record, “1: Cancel” is set in the item “Cancel Category” of item number 25 in FIG. 1, and transfer of the electronic record receivable becomes unsuccessful. As can be understood with reference to FIG. 1, this notification data file does not include an item indicating the reason for refusal, and has a problem that the transferor cannot recognize the reason for refusal.

  The present invention has been made in view of such problems, and when a request for transfer record of an electronic record receivable not accompanied by a guarantee is made to a user registered in advance, the request is rejected. Another object of the present invention is to provide an electronic record receivable assignment record automatic request elimination system that notifies the reason for refusal.

  In order to solve the above problems, an electronic record receivable assignment record request automatic exclusion system according to the present invention is a method executed by a server computer connected to an electronic receivable recording institution system, and includes an assignment record for an electronic record receivable Receiving the claim occurrence notification data from the electronic bond recording institution system, the transfer record request occurrence notification data including guarantee accompanying information indicating grant of a guarantee for the electronic record claim; and the guarantee Based on the accompanying information, determining whether or not a guarantee for the electronic record receivable is granted, and determining whether or not the guarantee is granted, transfer record request rejection notification data is sent to the electronic claim record Transmitting to the engine system.

  According to the electronic record receivable transfer record request automatic exclusion system according to the present invention, when a request for transfer record of an electronic record receivable not accompanied by a guarantee occurs, such transfer record request is rejected, and It becomes possible to notify the user of the reason. Therefore, it is possible to prevent the transfer of the electronic record receivable whose recourse destination is limited, and the user who becomes the transfer person can grasp the reason why the transfer record request is rejected.

It is a figure which shows the data format of the notification data file which concerns on one Embodiment of this invention. It is a block diagram which shows the example of a structure of the whole electronic recording receivable assignment record request automatic exclusion system which concerns on one Embodiment of this invention. It is a flowchart which shows the process which the electronic record receivable assignment record request automatic exclusion system which concerns on the 1st Embodiment of this invention performs. It is a figure which shows the example of the electronic record bond data table 400 which concerns on the 1st Embodiment of this invention. It is a figure which shows the example of the screen of the transfer record request data input interface screen 500 which concerns on the 1st Embodiment of this invention. It is a figure which shows the example of the user data table 600 which concerns on the 1st Embodiment of this invention. It is a figure which shows the example of the transfer record request result confirmation interface screen 700 which concerns on the 1st Embodiment of this invention. It is a flowchart which shows the process which the electronic record receivable assignment record request automatic exclusion system which concerns on the 2nd Embodiment of this invention performs. It is a figure which shows the structure of the disclosure result data which concern on the 2nd Embodiment of this invention.

<System configuration>
Hereinafter, an electronic record receivable assignment record request automatic removal system according to an embodiment of the present invention will be described in detail with reference to the accompanying drawings. FIG. 2 shows an example of the configuration of the entire electronic record receivable assignment record request automatic exclusion system according to the present invention.

  As shown in FIG. 2, the electronic record receivable assignment record request automatic exclusion system includes an electronic record receivable assignment record request automatic exclusion apparatus 1, an electronic receivable recording institution system 3, and a client computer 5. The electronic record receivable assignment record request automatic exclusion device 1 is connected to an electronic receivable recording organization system 3 via a network 2 including a dedicated line or a public line such as the Internet. The electronic record receivable assignment record request automatic exclusion apparatus 1 is connected to client computers 5 and 6 via a network 4 including a dedicated line or a public line such as the Internet.

  The electronic record receivable assignment record request automatic exclusion apparatus 1 is a main computing device that provides a service of the electronic record receivable assignment record request automatic exclusion system according to the present invention. The electronic record receivable transfer record request automatic exclusion device 1 is assigned to a transfer format having a common format for all financial institutions upon request for transfer record request for an electronic record receivable from a user who becomes a transferor (hereinafter referred to as “user A”). A record request data file is created, and the transfer record request data file is transmitted to the electronic bond recording institution system 3. In other words, the electronic record receivable assignment record request automatic exclusion device 1 is a bank system that provides a service related to an electronic record receivable provided by a window financial institution for users of the electronic record receivable. In addition, the electronic record receivable assignment record request automatic exclusion device 1 may be implemented alone, or may be additionally implemented in a server or host of a bank system that provides a bank accounting service existing in the past. Also good.

  The electronic record receivable assignment record request automatic exclusion apparatus 1 includes a network I / F 11, a control unit 12, a main storage unit 13, and an auxiliary storage unit 14, and these elements are connected via a system bus.

  The network I / F 11 transmits and receives data to and from the electronic bond recording institution system 3 and the client computers 5 and 6 connected via the networks 2 and 4, respectively.

  The control unit 12 is also called a central processing unit (CPU), performs control of each of the above-described constituent elements and data calculation, and reads various programs stored in the auxiliary storage unit 14 to the main storage unit 13 and executes them. To do.

  The main storage unit 13, also called a main memory, stores input data received by the electronic record receivable assignment record request automatic exclusion apparatus 1, computer-executable instructions, data after arithmetic processing by the instructions, and the like.

  The auxiliary storage unit 14 is a storage device represented by a hard disk (HDD) and stores a database table such as a user data storage unit 14a. The auxiliary storage unit 14 stores a program (not shown) for causing the control unit 12 to execute various processes according to the present invention.

  The electronic bond recording institution system 3 is a system for recording generation, transfer, etc. of electronic record receivables provided by an electronic receivable recording institution established by the National Bank Association, and stores a record book for each electronic record receivable An electronic record loan database 31 is provided. Upon receipt of the transfer record request data file from the electronic record receivable transfer record request automatic exclusion device 1, the electronic bond recording institution system 3 sends transfer record occurrence notification data to a user who becomes the transferee (hereinafter referred to as “user B”). When it is transmitted (via the bank system of the window financial institution used by the user B) and the consent is deemed to be accepted, processing such as updating the corresponding record ledger record in the electronic record bond database 31 is executed.

  The client computers 5 and 6 are computer terminals respectively used by the user A who makes a transfer record request to the electronic record receivable transfer record request automatic exclusion system according to the present invention and the user B who is the transferee. . The user A inputs information necessary for requesting the transfer record of the electronic record receivable from the transfer record request data input interface screen displayed on the client computer 5. Details of the transfer record request data input interface screen will be described later.

  The input information is transmitted to the electronic record receivable assignment record request automatic exclusion apparatus 1 to create a transfer record request data file and further transmitted to the electronic receivable recording institution system 3. When the client computer 6 receives the transfer record request occurrence notification data file from the electronic bond recording institution system 3 via the electronic record bond transfer record request automatic exclusion apparatus 1, the client computer 6 displays an indicator indicating the fact on the display (FIG. Not shown). In such a state, when the transfer record request is accepted and the approval is given, the transfer of the corresponding electronic record receivable transfer is established.

  The above-described client computers 5 and 6 may be information terminal devices such as a personal computer, a workstation, and a PDA having a communication function, for example. These information terminal devices are computing devices including a central processing unit (CPU), a memory, a storage device, and the like, and are comprehensively controlled by the CPU processing computer programs stored in the memory or the storage device. The processing according to the present invention can be executed to realize its function. Note that the above-described system configuration is for illustration, and does not limit the system configuration capable of executing the present invention.

<First Embodiment>
Next, processing executed by the electronic record receivable assignment record request automatic exclusion system according to the first embodiment of the present invention will be described with reference to the flowchart of FIG. In the present embodiment, the following matters are assumed. 1) A request for transfer record of an electronically recorded claim is made with user A as the transferor and user B as the transferee. 2) Users A and B shall use services related to the transfer of electronically recorded receivables with financial institution C as a window.

  User A inputs the record number of the electronic record receivable subject to the transfer record request from the initial screen (not shown) displayed on the client computer 5. The input record number is transmitted from the client computer 5 to the electronic record receivable assignment record request automatic exclusion apparatus 1 (step S301).

  When the network I / F 11 of the electronic record receivable assignment record request automatic exclusion apparatus 1 receives the record number transmitted in step S301, the control unit 12 reads the corresponding record from the electronic record receivable data table 400 based on the record number. A record is acquired (step S302). The acquired electronic record bond data record is transmitted to the client computer 5 again.

  FIG. 4 shows an electronic record bond data table 400. The electronic record receivable data table 400 stores information on the electronic record receivable managed by the electronic record receivable assignment record automatic request elimination apparatus 1, and includes items “record number”, “creditor user number”, “debt” Including "creditor user number", "credit amount", "payment date", "creditor settlement account information", and "obligor settlement account information", but are not limited to these items.

  When the client computer 5 receives the electronic record bond data record transmitted in step S302, the client computer 5 displays information of the record on the transfer record request data input interface screen 500. In this state, the user A inputs transfer record request data from the transfer record request data input interface screen 500. The input assignment record request data is transmitted from the client computer 5 to the electronic record receivable assignment record request automatic exclusion apparatus 1 (step S303).

  FIG. 5 shows a transfer record request data input interface screen 500. The assignment record request data input interface screen 500 includes an assigner information display field 501, an assignee information input field 502, an assigned receivable information input field 503, and a confirmation button 504.

  The transferor information display column 501 is a column for displaying the user number, settlement account information, and the like of the user A who is the transferor (displays information included in the electronic record bond data record transmitted in step S302). The assignee information input field 502 is a field for inputting the user number of the user B who is the assignee, payment account information, and the like. The transfer receivable information input field 503 displays the record number, the amount of receivable, and the payment date of the electronic record receivable to be transferred (displays information included in the electronic record receivable data record transmitted in step S302), and This is a field for inputting information such as the date of electronic recording that is the date of transfer and whether or not a warranty has been granted. If “None” is selected for whether or not a guarantee is granted, the subject electronic record receivable will not be accompanied by a guarantee (“0: Guarantee” in the item “Guarantee accompanying flag” included in the transfer record request data described later) None ”is set).

  When the above information is input and the confirmation button 504 is pressed, the client computer 5 creates transfer record request data and transmits it to the electronic record receivable transfer record request automatic exclusion apparatus 1. The transfer record request data input interface screen 500 is not limited to the items described above, but transfer record request data includes transferor information (user number, settlement account information, etc.), transferee information (users). Number, payment account information, etc.) and transferable receivable information (record number, electronic record date, guarantee accompanying flag), it is necessary to be able to check and / or input the above-mentioned information. is there.

  The transfer record request data includes debtor information, and displays the obligor information on the transfer record request data input interface screen 500 (displays information included in the electronic record bond data record transmitted in step S302). The information may be confirmed, but the display field is omitted in the present embodiment.

  Returning to the description of FIG. 3, the network I / F 11 of the electronic record receivable assignment record request automatic exclusion apparatus 1 receives the assignment record request data transmitted in step S303, and the control unit 12 includes the assignment record request data. With reference to the item “guarantee-accompanying flag”, it is determined whether or not the guarantee accompanies (step S304). If the guarantee is accompanied (Yes in step S304), the process proceeds to step S311. If the guarantee is not accompanied (No in step S304), the process proceeds to the subsequent process. That is, in the determination process in this step, if it is determined that the guarantee is accompanied, the process after step S311 is executed as a normal transfer record request.

  Next, the control unit 12 selects the corresponding user from the user data table 600 stored in the auxiliary storage unit 14 based on the user number of the transferee included in the transfer record request data transmitted in step S303. A data record is acquired (step S305). The user data table 600 is a database table that stores information related to users registered in the financial institution C as users who have used services related to electronic record receivables.

  As shown in FIG. 6, the user data table 600 includes items “record number”, “user name”, “account information”, and “automatic exclusion flag”. The item “automatic exclusion flag” is a flag indicating whether or not to automatically reject the transfer record request received by the user B when it is determined in step S304 that the guarantee is not accompanied. If (Automatic Exclusion) is set, it is automatically rejected. In the item “e-mail address”, an e-mail address that is a destination when a reason for rejection notification described later is transmitted is set.

  In the present embodiment, the user data record is acquired based on the transferee's user number, but the user data record may be acquired based on the transferee's account information ( User B can be identified by the account information of the assignee).

  Next, in step S306, the control unit 12 refers to the item “automatic exclusion flag” included in the user data record acquired in step S305, and determines whether or not it is automatic exclusion. In the case of automatic exclusion (Yes in step S306), the process proceeds to the subsequent process. In the case of not automatic exclusion (No in step S306), the process proceeds to step S309. In other words, in the determination process in this step, if it is determined that it is not automatic exclusion, the user B as the assignee does not indicate the intention to automatically exclude because the guarantee is not accompanied. As a normal transfer record request, the processing from step S311 is executed.

  In step S307, the control unit 12 determines whether or not the transferor is the financial institution C with reference to transferor information included in the transfer record request data transmitted in step S303. If the transferor is the financial institution C (Yes in step S307), the process proceeds to step S311. If the transferor is not the financial institution C (No in step S307), the process proceeds to the subsequent process. That is, in the determination process in this step, if it is determined that the transferor is the financial institution C, the process after step S311 is executed as a normal transfer record request even if no guarantee is accompanied. Become.

  Electronically recorded receivables can be cashed by transferring them to financial institutions. That is, in the transfer record request, when the user A who is the transferor is the financial institution C and the user B who is the transferee, the transferred and cashed receivable is reassigned (return of receivable). Therefore, in this case, the guarantee is usually not accompanied. Therefore, the determination process as in step S307 is executed.

  In step S308, the control unit 12 refers to the debtor account information included in the transfer record request data transmitted in step S303, and determines whether the debtor account is an SPC (Special Purpose Company). Determine whether or not. If the debtor account is an SPC account (Yes in step S308), the process proceeds to step S311. If the debtor account is not an SPC account (No in step S308), the process proceeds to the subsequent process. That is, in the determination process in this step, if it is determined that the debtor account is an SPC account, the process after step S311 is executed as a normal transfer record request even if no guarantee is accompanied. Become.

  The determination as in step S308 is executed according to the Special Measures Law concerning the receivables management and collection business. Receivables with SPCs as debtors are designated as monetary receivables, the right to reimburse such receivables is restricted, and debtors This is because the transfer of claims using an SPC account as the account is usually not accompanied by a guarantee.

  In step S309, the control unit 12 acquires a corresponding user data record from the user data table 600 based on the transferor's user number included in the transfer record request data transmitted in step S303.

  Next, the control unit 12 includes items included in the user data record (transferee user data record) acquired in step S304 and the user data record (transferr user data record) acquired in step S309. Reject notification reason data is transmitted with the addresses set in the “e-mail address” as destinations (the destinations of the e-mail are the client computers 5 and 6) (step S310). Rejection notification reason data includes at least information on the subject electronic record receivable (record number, payment date, etc.), information on transferor and transferee (user number, account information, etc.), and information indicating the reason for rejection (Such as a reason code or a message indicating the reason).

  FIG. 7 shows an example of a transfer record request result confirmation interface screen 700 displayed on the display unit by the client computers 5 and 6 that have received the rejection notification reason data. The transfer record request result confirmation interface screen 700 displays information about the transferor, the transferee, and the receivable of the target electronic record receivable, and the request result display field 701 displays the result of the transfer record request and when it is rejected. The reason is displayed.

  In this way, when there is a transfer record request that is not accompanied by a guarantee, the electronic record receivable transfer record request automatic exclusion device 1 automatically rejects the transfer record request. It is possible to avoid the transfer record that is contrary to the intention. In addition, both the transferor and the transferee will be notified of the reason for refusal of the automatic exclusion, so it is not possible to grasp the reason why the transfer request was rejected, especially from the standpoint of the transferor. The situation can be avoided.

  In this embodiment, the reason for refusal is displayed on a dedicated interface screen such as the transfer record request result confirmation interface screen 700, but the present invention is not limited to such a format. A rejection notification may be transmitted to the client computers 5 and 6.

  Returning to the description of FIG. 3, in step S311, (in step S304, it is determined that the guarantee is accompanied, in step S306, in the case where it is determined that there is no automatic exclusion, in step S307, from the financial institution C. If it is determined to be transfer or if it is determined in step 308 that the debtor account is an SPC account), the electronic record receivable transfer record request automatic exclusion apparatus 1 sends the transfer record request data to the electronic receivable recording institution system. 3 to send. When the electronic bond recording institution system 3 receives the transfer record request data, it creates transfer record request notification data and transmits it to the client computer 6 via the electronic record bond transfer record request automatic exclusion device 1 (step S312). When the client computer 6 receives the transfer record request notification data and is deemed to be accepted (step S313), the record in the electronic record bond database 31 is updated and the transfer record is recorded in the electronic bond record institution system 3 (step S313). Step S315). On the other hand, when the user B refuses (step S314), the transfer record request is not established.

  Although the above steps S311 to S314 have been briefly described, these processes are the same as the existing processes executed between the bank system and the electronic bond recording institution system when a transfer record request is made. Therefore, detailed description is omitted in this specification.

  In the present embodiment, an example is explained in which both the users A and B use the financial institution C as a window, but the window financial institution used by the user A who is the transferor is another financial institution. In a certain example (that is, when the transfer financial institution used by the transferor is not a financial institution that provides the electronic record receivable assignment record request automatic exclusion system service according to the present invention (hereinafter referred to as “financial institution D”)), This is different from the above processing.

  First, in step S303, transfer record request data is input and transmitted to a bank system provided by the financial institution D (hereinafter, “bank system d”). The bank system d then transfers the transfer record request data to an electronic bond record. Transmit to the engine system 3. In response to receiving the transfer record request data, the electronic bond record institution system 3 transmits transfer record request generation notification data to the electronic record bond transfer record request automatic exclusion apparatus 1. Then, the control unit 12 of the electronic record receivable assignment record request automatic exclusion device 1 refers to the value of the item “guarantee-accompanying flag” included in the transfer record request occurrence notification data transmitted from the electronic receivable recording institution system 3, It is determined whether or not the guarantee is accompanied (corresponding to step S304 described above).

  In step S310, in addition to / instead of transmitting the rejection notification reason data to the client computers 5 and 6, the control unit 12 of the electronic record receivable assignment record request automatic exclusion device 1 performs the electronic receivable recording institution system 3 In addition, notification data indicating rejection of the transfer record request is transmitted. Due to the transmission of the notification data, the transfer record request from the user A who becomes the transfer person is not established.

  That is, when both users A and B are using the financial institution C as a window (case 1), the electronic bond recording institution system 3 is not notified that a transfer record request has occurred, The rejection reason notice is returned to the client computer as it is. On the other hand, when user A uses financial institution D and user B uses financial institution C as a window (case 2), it responds to the transfer record request occurrence notification data transmitted from electronic bond recording institution system 3. Thus, notification data indicating rejection of the transfer record request is transmitted to the electronic bond recording institution system 3. By transmitting the rejection notification data to the electronic bond recording institution system 3, the transfer record request is not established.

  That is, when the electronic record receivable transfer record request automatic exclusion device 1 receives the transfer record request occurrence notification data from the electronic receivable record institution system 3, it refers to the transfer record request occurrence notification data to determine automatic rejection, Rejection notification data is transmitted to the electronic bond recording institution system 3. When the electronic record receivable transfer record request automatic exclusion apparatus 1 receives the transfer record request data directly from the client computer of the user who becomes the transferor, the rejection notification is sent to the client computer without going through the electronic receivable recording organization system 3 Send reason data. Any of the cases described above can be applied to the second embodiment described later.

  Note that the automatic exclusion determination process in step S306 may not be executed. In this case, if a transfer record request not accompanied by a guarantee is made, it will be automatically rejected unconditionally. In this embodiment, both users A and B receive services related to electronic record receivables with financial institution C as a window, but the same configuration applies even when different financial institutions are used. can do.

<Second Embodiment>
Next, processing executed by the electronic record receivable assignment record request automatic exclusion system according to the second embodiment of the present invention will be described with reference to the flowchart of FIG. In the second embodiment, the same embodiment as the first embodiment is used.

  Steps S801 to S805 are the same processes as steps S301 to S303 and steps S305 to S306 described with reference to FIG. 3, respectively, and thus description thereof will be omitted.

  In step S806 (in step S805, it is determined that the user B as the assignee indicates the intention of automatic removal), the control unit 12 of the electronic record receivable assignment record request automatic removal apparatus 1 Disclosure request data for the electronic record receivable will be created. The disclosure request data is data in which a common data format for requesting the electronic bond recording institution system 3 to disclose the contents of the electronic record bond is defined. The disclosure request data includes at least the record number of the electronic record receivable subject to the transfer request, transferor information (user number, account information, etc.), and transferee information (user number, account information, etc.). When the disclosure request data is created, it is transmitted to the electronic bond recording institution system 3.

  When the electronic bond recording institution system 3 receives the disclosure request data (step S807), the disclosure result data is created and transmitted to the electronic record bond transfer record request automatic exclusion apparatus 1 (step S808).

  The disclosure result data is a data file having a unified format having information related to the disclosure result in response to a request for disclosure of the contents of the electronic record bond to the electronic bond recording institution system 3. As shown in FIG. 9, the disclosure result data includes a header record 901, a data record (bond information) 902, data records (guarantor information) 903 a and 903 b, a trailer record 904, and an end record 905.

  The data record (bond information) 902 includes data indicating the contents of the electronic record bond to be disclosed, and includes information indicating the number of transfer records, that is, the number of times the corresponding electronic record bond has been transferred. .

  The data records (guarantor information) 903a and 903b have guarantor data of the corresponding electronic record receivable, and can include up to three guarantor data for one data record. In this embodiment, two data records (guarantor information) 903a and 903b are provided for one data record (bond information) 902, and the data record (guarantor information) 903a is guarantor data for three persons. The data record (guarantor information) 903b includes guarantor data for two persons. That is, five guarantors are associated with the subject electronic record receivable.

  In addition, since the disclosure result data is publicly known in this technical field, the detailed description of the content is omitted in this specification.

  Returning to the description of FIG. 8, the control unit of the electronic record receivable assignment record request automatic exclusion device 1 includes the number of transfers included in the data record (bond information) 902 and the data records (guarantor information) 903a and 903b. The total number of guarantor data is compared to determine whether the numbers match (step S809). If they match (Yes in step S809), the process proceeds to step S814. If they do not match (No in step S809), the process proceeds to the subsequent process.

  In step S809, such a determination is made when, for example, the number of transfers is five, but the total number of guarantor data is 4, a guarantee is accompanied when a transfer record has been recorded in the past. It can be judged that there was not. Such requests for transfer records of electronic record receivables are excluded.

  In the first embodiment, the automatic exclusion is determined based on the value of the guarantee accompanying flag of the notification data transmitted from the electronic bond recording institution system 3 (that is, the latest electronic recorded bond is accompanied by a guarantee). In the present embodiment, since it is also determined whether or not a guarantee was accompanied at the time of past assignment, the user B who becomes the assignee is further retroactively requested. Will be able to transfer the secured electronic record receivable.

  Thereafter, the processing from step S810 onward is executed, but the processing from step S810 to step S817 is the same as the processing from step S307 to step S314 described in FIG.

  As described above, the description of the electronic record receivable assignment record request automatic exclusion system according to the present invention has been described in detail, but specific data such as the electronic record receivable data table 400 and the user data table 600 described in the embodiment. The structure is illustrative only and changes may be made without departing from the claimed subject matter. Further, the order of the steps in the flowcharts described in FIGS. 3 and 8 may be changed within the scope of the principle of the present invention, and arbitrary steps may be omitted.

2 Network 4 Network 400 Electronic Record Claim Data Table 500 Assignment Record Request Data Input Interface Screen 501 Assignee Information Display Field 502 Assignee Information Input Field 503 Assigned Claim Information Input Field 504 Confirm Button 600 User Data Table 700 Confirmation of Request for Transfer Record Request Interface screen 701 Billing result display field 901 Header record 902 Data record (bond information)
903a Data record (guarantor information)
903b Data record (guarantor information)
904 Trailer record 905 End record

Claims (12)

A method executed by a server computer connected to an electronic bond recording agency system,
Receiving transfer record request occurrence notification data for an electronic record claim from the electronic claim recording institution system, wherein the transfer record request occurrence notification data includes guarantee accompanying information indicating grant of a guarantee for the electronic record claim , Steps and
Determining whether a guarantee for the electronically recorded bond is granted based on the guarantee accompanying information;
Transmitting transfer record request rejection notification data to the electronic bond recording institution system based on a result of determining whether or not the guarantee is given. The server computer includes a user storage unit of a user registered in the electronic bond recording institution system,
The assignment record request occurrence notification data further includes assignee identification data,
The method further comprises obtaining a user data record from the user storage unit based on the assignee identification data;
The method of claim 1, wherein the step of determining whether the guarantee is granted is controlled based on the acquired user data record. The transfer record request occurrence notification data further includes transferor data,
The method further comprises the step of determining whether a transferor of the transfer record request is a financial institution based on the transferor data,
The method according to claim 1, wherein the step of transmitting the transfer record request rejection notification data is further based on a result of determining whether the transfer is a financial institution. The transfer record request occurrence notification data further includes debtor account data,
The method further comprises determining whether the debtor account of the electronically recorded receivable is an SPC account based on the debtor account data;
The method according to any one of claims 1 to 3, wherein the step of transmitting the transfer record request rejection notification data is further based on a result of determining whether the transfer record request rejection notification data is the SPC account. A method executed by a server computer connected to an electronic bond recording agency system,
Receiving transfer record request occurrence notification data for an electronic record claim from the electronic claim recording institution system, wherein the transfer record request occurrence notification data includes a record number for identifying the electronic record claim;
Transmitting disclosure request data to the electronic bond recording agency system based on the record number;
Receiving disclosure result data from the electronic bond recording agency system, wherein the disclosure result data includes the number of transfers of the electronic record bond and guarantor data; and
Comparing the number of transfers with the total of the guarantor data;
And a step of transmitting transfer record request rejection notification data to the electronic bond recording institution system based on the comparison result. A method executed by a server computer connected to a client computer,
Receiving transfer record request data for an electronic record claim from the client computer, wherein the transfer record request data includes guarantee accompanying information indicating grant of a guarantee for the electronic record claim;
Determining whether a guarantee for the electronically recorded bond is granted based on the guarantee accompanying information;
And a step of transmitting, to the client computer, transfer record request rejection reason data indicating a reason for rejecting the transfer record request based on a result of determining whether the guarantee has been granted. A method executed by a server computer connected to an electronic bond recording institution system and a client computer,
Receiving transfer record request data for an electronic record claim from the client computer, wherein the transfer record request data includes a record number identifying the electronic record claim;
Transmitting disclosure request data to the electronic bond recording agency system based on the record number;
Receiving disclosure result data from the electronic bond recording agency system, wherein the disclosure result data includes the number of transfers of the electronic record bond and guarantor data; and
Comparing the number of transfers with the total of the guarantor data;
Transmitting transfer record request rejection reason data indicating a reason for rejecting the transfer record request to the client computer based on the comparison result. A computer system connected to an electronic bond recording agency system,
A transfer record request occurrence notification data receiving unit for receiving transfer record request occurrence notification data for an electronic record claim from the electronic claim recording institution system, wherein the transfer record request occurrence notification data provides a guarantee for the electronic record claim A transfer record request occurrence notification data receiving unit including warranty accompanying information indicating:
Based on the guarantee accompanying information, a guarantee grant determining unit that determines whether a guarantee for the electronic record receivable is given,
A computer system, comprising: a transfer record request rejection notification data transmission unit that transmits transfer record request rejection notification data to the electronic bond recording institution system based on a determination result by the guarantee grant determination unit. A computer system connected to an electronic bond recording agency system,
A transfer record request occurrence notification data receiving unit for receiving transfer record request occurrence notification data for an electronic record claim from the electronic claim recording institution system, wherein the transfer record request occurrence notification data is a record for identifying the electronic record claim A transfer record request notification data receiving unit including a number;
Based on the record number, a disclosure request data transmission unit that transmits disclosure request data to the electronic bond recording institution system,
A disclosure result data receiving unit for receiving disclosure result data from the electronic bond recording institution system, wherein the disclosure result data includes the number of transfers of the electronic record bond and guarantor data;
A comparison unit for comparing the number of transfers and the total of the guarantor data;
A computer system, comprising: a transfer record request rejection notification data transmission unit that transmits transfer record request rejection notification data to the electronic bond recording institution system based on a comparison result by the comparison unit. A computer system connected to a client computer,
A transfer record request data receiving unit for receiving transfer record request data for an electronic record claim from the client computer, wherein the transfer record request data includes guarantee accompanying information indicating grant of a guarantee for the electronic record claim A recording request data receiving unit;
Based on the guarantee accompanying information, a guarantee grant determining unit that determines whether a guarantee for the electronic record receivable is given,
A transfer record request rejection reason data transmission unit that transmits transfer record request rejection reason data indicating a reason for rejecting the transfer record request to the client computer based on a determination result by the guarantee grant determination unit. Computer system. A computer system connected to an electronic bond recording agency system and a client computer,
An assignment record request data transmission unit for receiving assignment record request data for an electronic record claim from the client computer, wherein the assignment record request data includes a record number for identifying the electronic record claim And
Based on the record number, a disclosure request data transmission unit that transmits disclosure request data to the electronic bond recording institution system,
A disclosure result data receiving unit for receiving disclosure result data from the electronic bond recording institution system, wherein the disclosure result data includes the number of transfers of the electronic record bond and guarantor data;
A comparison unit for comparing the number of transfers and the total of the guarantor data;
A transfer record request rejection reason data transmission unit that transmits transfer record request rejection reason data indicating a reason for rejecting the transfer record request to the client computer based on a comparison result by the comparison unit; Computer system.   The program for making a computer perform the method as described in any one of Claims 1 thru | or 6.

Images