JP2020003872A - Processing system of electronically recorded monetary claim processing system, method and program - Google Patents

Abstract

To provide a processing system of an electronically recorded monetary claim, a method and a program to improve convenience in a case of generating an electronic recording credit in a creditor claim method.SOLUTION: A processing system of an electronically recorded monetary claim comprises a receiving part to receive a notification of an accrual recording claim to a debtor from an electronic monetary claim recording institution, and a transmitting part to transmit an acceptance reply to the notification to the electronic monetary claim recording institution when a credit attribute is within a prescribed range. In a credit processing method, the receiving part receives the notification of the accrual recording claim to the debtor from the electronic monetary claim recording institution, and the transmitting part transmits the acceptance reply to the notification to the electronic monetary claim recording institution when the credit attribute is within the prescribed range.SELECTED DRAWING: Figure 6

Description

  The present invention relates to an electronically recorded loan processing system, method, and program. More specifically, the present invention relates to an electronically recorded claim processing system, method, and program that enable a creditor to respond to a creditor claim method in which a creditor makes a claim recording request to an electronic claim recording organization through a trading financial institution.

  Conventionally, electronically recorded receivables have been widely used as settlement means. Users of electronically recorded receivables (creditors and debtors) can record the occurrence of electronically recorded receivables by recording them in a record ledger of an electronic receivables recording organization (for example, Densai Net (registered trademark)) through a financial institution. Procedures such as transfer and payment can be performed (Patent Document 1).

JP 2011-175571 A

  The procedure for generating electronically recorded receivables includes a debtor claim method in which a debtor makes a request for recording and issuing an electronic credit to a credit receivable institution through a trading financial institution, and a claim in which a creditor makes a request for recording and generating a credit to an electronic receivables recording institution through a trading financial institution There are two billing schemes: a single billing scheme. Conventionally, of the two billing methods, a procedure in which a debtor generates an electronically recorded claim by the debtor claim method has been widely used.

  On the other hand, if the creditor wants to generate an electronically recorded claim by the creditor claim method and start the settlement flow by fund transfer, the creditor cannot independently perform the procedure for generating the electronically recorded claim. That is, if the debtor denies the notification of the request for accrual record, or the debtor responds to the notification of the request for accrual record within a predetermined period (for example, within 5 days) (acceptance or denial; If no "accept / deny" is transmitted, no electronically recorded receivable is generated. Therefore, there is a problem that the consent of the debtor is required every time the creditor requests the recording of the occurrence.

  Accordingly, it is an object of the present invention to provide an electronically recorded loan processing system, a method, and a program, which have improved convenience in generating an electronically recorded loan by the above-mentioned creditor claim method.

  In one embodiment of the present invention, a receiving unit that receives a notification of an occurrence record request addressed to a debtor from an electronic credit recording institution, and when the attribute of the bond is within a predetermined range, the electronic bond recording institution responds to the notification. An electronic record receivables processing system comprising: a transmission unit for transmitting an acceptance reply;

  The electronically recorded claim processing system according to one embodiment of the present invention may further include an occurrence record requesting means for transmitting a request for an electronically recorded claim to be recorded by a creditor claim method to the electronic claim recording organization. Good.

  In the electronically recorded claim processing system according to one embodiment of the present invention, the attribute of the claim may be a claim amount.

  In the electronically recorded loan processing system according to one embodiment of the present invention, the attribute of the bond may be a creditor.

  In one embodiment of the present invention, a receiving unit receives a notification of an occurrence record request addressed to a debtor from an electronic bond recording institution, and the transmitting unit transmits the electronic bond recording institution when the attribute of the bond is within a predetermined range. A method for processing an electronically recorded receivable is provided that sends an acceptance response to the notification.

  In one embodiment of the present invention, a computer is connected to a receiving unit that receives a notification of an occurrence record request addressed to a debtor from an electronic debt recording organization, and to the electronic debt recording organization when the attribute of the debt is within a predetermined range. A program is provided for operating as an electronically recorded loan processing system having a transmission unit for transmitting an acceptance reply to the notification.

  It is possible to provide an electronically recorded loan processing system, a method, and a program, in which the convenience in the case of generating an electronically recorded loan by the creditor claim method is improved.

1 is a configuration diagram illustrating an electronically recorded loan processing system according to an embodiment of the present invention. FIG. 2 is a diagram showing client information recorded and managed in a client management database (DB) of the electronically recorded loan processing system according to one embodiment of the present invention. It is a figure showing the service use information recorded and managed in the client management DB of the electronically recorded claim processing system according to one embodiment of the present invention. It is a figure showing processing history information recorded and managed in the history management DB of the electronically recorded claim processing system according to one embodiment of the present invention. It is a figure showing the service use information recorded and managed in the client management DB of the electronically recorded claim processing system according to one embodiment of the present invention. It is a flowchart which shows the electronically recorded claim processing method concerning one Embodiment of this invention.

  Hereinafter, an information management apparatus, method, and program according to an embodiment of the present invention will be described in detail with reference to the drawings. The embodiments described below are examples of the embodiments of the present invention, and the present invention is not limited to these embodiments.

  FIG. 1 is a configuration diagram illustrating an electronically recorded loan processing system according to an embodiment of the present invention. FIG. 1 also shows an electronic bond recording institution 120, a creditor terminal 132, and a debtor terminal 134 connected to the electronically recorded loan processing system 100 via a network.

  The electronic bond recording organization 120 is, for example, a national electronic bond network (Densai Net) provided by the National Bankers Association, and has a record ledger DB 122. The electronically recorded loan processing system 100 is, for example, a system operated by participating financial institutions of Densai Net.

  The electronically recorded debt processing system 100 can be, for example, a computer including hardware resources such as a processor, a memory, a storage device, a communication device, and an input / output device. The electronic record receivables processing system 100 includes a communication control unit 102 configured by hardware resources and / or programs, a collation unit 104, and a data generation unit 108.

  The electronically recorded loan processing system 100 includes a client management DB 106 for recording and managing client information (FIG. 2) and service usage information for each client (FIG. 3), and a history management DB 110 for recording and managing processing history information (FIG. 4). And

  The communication control unit 102 transmits and receives data to and from the electronic credit recording agency 120, the creditor terminal 132, and the debtor terminal 134 via the network. The communication control unit 102 receives the request for the occurrence record request from the creditor terminal 132, transmits the request for the occurrence record request by the creditor claim method to the electronic bond recording organization 120, and sends the request to the debtor from the electronic bond recording organization 120. It is possible to receive the notification of the occurrence record request by the creditor request method and transmit a response to the debtor to the electronic credit recording organization 120 for the acceptance of the occurrence record request by the creditor request method.

  Alternatively, the communication control unit 102 transmits to the debtor terminal 134 a notification of the occurrence record request by the creditor request method addressed to the debtor, which is received from the electronic debt recording organization 120, and the debtor terminal 134 generates the notification by the creditor claim method. The response (consent / denial) of the notification of the recording request can be received and transmitted to the electronic bond recording organization 120.

  The collation unit 104 extracts the information of the client (obligor) from the client management DB 106 in response to the notification of the occurrence record request addressed to the obligor from the electronic debt recording organization 120, and collates the information on the service use. More specifically, for example, the collation unit 104 determines the number (user number) and / or debt of the user designated as the obligor of the electronically recorded receivable in the notification of the occurrence record request received from the electronic receivables recording organization 120. A record related to the client that matches the account number of the financial institution of the user designated as the user is extracted from the client management DB 106.

  Next, the collation unit 104 determines that the client (user designated as a debtor) in the extracted record indicates that the electronically recorded receivables processing system 100 Is set to automatically transmit a response to the consent to the electronic receivables recording agency 120 when the attribute satisfies a predetermined condition (for example, a predetermined amount of credit, a predetermined creditor, etc.) Collate.

  Hereinafter, "automatically transmitting a response to acceptance to the electronic credit recording agency 120 when the predetermined condition is satisfied (for example, when the amount is a predetermined amount of credit, when the case is a predetermined creditor, etc.)" The condition is also referred to as "automatic consent" and the "condition for performing automatic consent".

  Further explanation will be given regarding the automatic consent. The condition for performing the automatic consent is to determine the attribute of the receivable. In other words, automatic consent is determined by determining the attributes of the bond. As a specific example of the attribute, in one embodiment of the present invention, a predetermined amount of credit and a predetermined creditor can be cited. That is, the debtor automatically sends a response to the electronic credit recording agency 120 to the electronic credit recording agency 120 when the credit amount is a predetermined credit amount (for example, when the credit amount is within a predetermined credit amount range) and when the creditor is a predetermined creditor. You can set it by sending it.

  For example, the collation unit 104 determines the user number of the creditor registered in association with the client (user designated as the debtor) in the extracted record (automatically within a predetermined frame by the electronically recorded loan processing system 100). The user number of the creditor who is permitted to answer the consent) and the number (user number) of the user designated as the creditor of the electronically recorded credit in the notification of the request for the occurrence record received from the electronic credit recording organization 120 It can be checked whether they match.

  The data generation unit 108 generates data of a response to the consent to the electronic receivables recording institution 120 in accordance with the collation result of the collation unit 104 (when automatic consent by the electronically recorded receivables processing system 100 is permitted).

  Further, the data generation unit 108 generates data for transmitting to the debtor terminal 134 the notification of the occurrence record request by the debtor claim method to the debtor received from the electronic debt recording agency 120 (the electronically recorded debt processing system). 100 if automatic consent is not allowed and / or if automatic consent is allowed).

  Further, the data generation unit 108 transmits the notification (or the result) of the occurrence record by the debtor claim method to the creditor and the debtor received from the electronic debt recording organization 120 to the creditor terminal 132 and the debtor terminal 134. Generate data for

  Further, after the occurrence of the electronically recorded claim is registered in the record ledger DB 122, the data generating unit 108 notifies the creditor terminal 132 and the debtor terminal 134 of the notification of the occurrence of the electronically recorded claim received from the electronic claim recording organization 120. Generate data for transmission.

  The communication control unit 102 transmits the consent notice to the electronic bond recording organization 120. As described above, in one embodiment of the present invention, the financial institution automatically transmits, to the electronic credit recording institution 120 on behalf of the debtor, an acceptance response to the notice of the creditor's request for recording the occurrence of the creditor claim method. Thus, it is possible for the creditor to start the settlement by fund transfer using the electronically recorded loan.

  Next, a method of processing an electronically recorded loan in the electronically recorded loan processing system 100 will be described.

(Pre-registration of client information)
In the client management DB 106 of the electronically recorded receivables processing system 100, for each client, that is, for each record, a debtor use flag indicating whether a debtor of an electronically recorded receivable can be obtained. A service use flag indicating whether or not a service for transmitting a response to the automatic approval is transmitted in response to the notification of the record, a condition for performing the automatic approval, a creditor request that is permitted to transmit the response to the automatic approval by the electronically recorded receivables processing system 100 A user number for identifying a requester (user designated as a creditor) of the system occurrence record is registered.

  FIG. 2 is a diagram showing client information recorded and managed in the client management DB 106 of the electronically recorded loan processing system 100 according to one embodiment of the present invention. The first record of the client information in the client management DB 106 shown in FIG. 2 includes account identification information (financial institution code, branch code, branch name, account number, and account type) for the user identified by the user number “1214”. Code, etc., not shown), together with the value of a debtor use flag indicating that the debtor can be an electronically recorded debt (1: be a debtor / 0: do not become a debtor (become a creditor)) and services The value of the service use flag (1: usable / 0: not usable) indicating that the service can be used is registered.

  The service use flag whose value is set to 1 (available) indicates that the financial institution (the electronically recorded receivables processing system 100) responds to the reception of the notification from the electronically receivable recording institution 120 or the user (debt This means that the financial institution automatically sends an acceptance response to the electronic credit recording agency 120 on behalf of the debtor when a response from the creditor or creditor is not received within a predetermined period.

  FIG. 3 is a diagram showing service usage information recorded and managed in the client management DB 106 of the electronically recorded loan processing system 100 according to one embodiment of the present invention. The service usage information shown in FIG. 3 includes, for the user identified by the user number “1214”, a request for the occurrence record of the creditor claim method in which the transmission of the response of the automatic approval by the electronically recorded claim processing system 100 is permitted. The user identified by the user number “2017” is registered as a user.

  In addition to the user name (user name) identified by the user number “1214” in the record of the client management DB 106, kana name, representative name, representative kana name, address, and contact information (telephone number, electronic (E-mail address) and the like, and the user name and the like of the user identified by the user number “2017” may be registered.

  Also, in the service usage information shown in FIG. 3, for the user (“Y”) identified by the user number “3150”, the user (“B”) identified by the user number “4410” and The electronic record receivables processing system 100 is allowed to transmit a response to the notification of the occurrence record requested by the user (“C”) identified by the user number “6666” by the creditor claim method. It is registered.

  FIG. 4 is a diagram showing processing history information recorded and managed in the history management DB 110 of the electronically recorded loan processing system 100 according to one embodiment of the present invention. Each time the electronically recorded loan information is transmitted or received, the electronically recorded loan processing system 100 associates the information with the user number and name of the creditor and the user number and name of the debtor, and records the occurrence in the electronically receivable recording organization 120. Request transmission date and time, consent notification transmission date and time, consent notification transmission type and other information (receivable amount, payment date, occurrence record request reception date and time, record request notification reception date and time, occurrence record notification reception date and time, etc. Z) is stored.

  The consent notification transmission type is stored as “set” or “normal”. The setting indicates that the response data of the consent generated by the electronically recorded receivables processing system 100 has been transmitted to the electronically receivable recording agency 120. Normally, it indicates that the electronically recorded receivables processing system 100 has received the response data for notifying the consent or denial from the debtor, and has transmitted the response data to the electronic receivable recording agency 120.

  FIG. 5 is a diagram showing service use information recorded and managed in the client management DB 106 of the electronically recorded receivables processing system 100 according to one embodiment of the present invention. The service usage information shown in FIG. 5 includes the user number and name of the creditor, the user number and name of the debtor, and the value of the transaction start flag indicating the start of the transaction of the electronically recorded receivable (1: 0: the transaction has not started).

  When a transaction is started between creditor A and debtor X, the transaction start flag is stored as "1". On the other hand, since the transaction has not been started between the creditor B and the debtor Z, the transaction start flag is stored as “0”.

(Method of processing electronically recorded receivables)
FIG. 6 is a flowchart showing an electronically recorded loan processing method according to an embodiment of the present invention. Hereinafter, a method of processing an electronically recorded claim in the electronically recorded claim processing system 100 will be described with reference to FIG.

  As an example, the creditor “A” identified by the user number “2017” having the transaction start flag “1” shown in FIG. 5 becomes the debtor “X” identified by the user number “1214” ] Describes a flow for requesting recording of electronically recorded receivables by a creditor request method. When the creditor terminal 132 of the creditor “A” transmits a request for a request to generate and record an electronically recorded loan to the electronically recorded loan processing system 100 (communication control unit 102), the flow in FIG. 6 starts.

  In step S301, the electronically recorded loan processing system 100 (communication control unit 102) receives a request for an electronically recorded bond generation record request from the creditor terminal 132 of the creditor “A”.

  The request for the occurrence record request includes the user number and account identification information of the creditor “A” and the user number and account identification information of the debtor “X”. Further, the request for the occurrence record request includes information necessary for registration in the record ledger DB 122 of the electronic bond recording organization 120, such as information on the amount of the bond, the due date, and the like.

  The electronically recorded receivables processing system 100 extracts these pieces of information from the request for occurrence record request, records them in the history management DB 110 (FIG. 4), and starts record management of the processing history information.

  In step S301, the electronically recorded receivables processing system 100 (collation unit 104) further extracts the record of "X" from the client management DB 106 by the same processing as step S307 described below, and sets the value of the debtor use flag. May be registered as 1 (“X” can be a debtor).

  In this case, if “X” cannot be a debtor, the electronically recorded receivables processing system 100 (data generation unit 108) generates data for notifying the creditor “A” of an error, and performs communication control. The data is transmitted to creditor terminal 132 via section 102, and the process is terminated.

  In step S303, the electronically recorded bond processing system 100 (data generation unit 108) generates the received creditor claim generation generation request data and transmits the generated data to the electronic bond recording organization 120 via the communication control unit 102. Send to

  The data of the occurrence record request includes information necessary for registration in the record ledger DB 122 of the electronic bond recording organization 120, such as the user numbers and account identification information of the creditors and the debtors. The electronically recorded receivables processing system 100 updates the record management of the processing history information by recording the transmission date and time of the occurrence record request (FIG. 4).

  After receiving the data of the claim record request in the creditor claim method, the electronic bond recording organization 120 sends a notice of the request for record to the user “X” (user number “1214”) designated as the debtor electronically. It transmits to the recorded loan processing system 100 and waits for a response from the debtor.

  In the case where “X” has not been registered as a user who can be a debtor in the electronic bond recording organization 120 and cannot be a debtor, the electronic bond recording organization 120 notifies the electronically recorded bond processing system 100 of an error. May be transmitted.

  When an error notification is received from the electronic bond recording organization 120, the electronically recorded bond processing system 100 (data generation unit 108) generates data for notifying the creditor “A” of an error, and the communication control unit 102 The processing may be transmitted to the creditor terminal 132 via the terminal, and the processing may be terminated.

  In step S305, the electronically recorded bond processing system 100 (communication control unit 102) receives a notification of the occurrence record request addressed to the debtor “X” from the electronic bond recording agency 120. The notification of the occurrence record request includes the user numbers and account identification information of the creditors and debtors.

  In step S307, the electronically recorded bond processing system 100 (checking unit 104) checks the service use flag and checks the attribute of the bond.

  More specifically, the electronically recorded receivables processing system 100 (collation unit 104) performs client management using the user number and / or account identification information of the debtor "X" indicated in the received notification of the occurrence record request as a key. The record of "X" is extracted from the DB 106, and the user number "2017" of the creditor "A" registered in association with "X" in the extracted record (response of the automatic approval by the electronically recorded loan processing system 100 is possible. Registered as a user number of the user) and the user number of the user designated as the creditor of the electronically recorded claim (“A” "2017") is matched.

  Prior to the collation of the user number, the electronically recorded receivables processing system 100 (collation unit 104) determines whether or not the value of the service use flag in the extracted record is registered as 1 (usable) (“X” indicates that the service is used). If the value of the service use flag is 1 (usable), the conditions for performing the automatic consent are confirmed, and it is determined whether the automatic consent may be performed (step S309). .

  Referring to FIG. 2, since the value of the “X” service use flag is 1 (usable), the condition for performing the automatic approval is confirmed. The condition for performing automatic consent is described as "3 million yen or less if A (No. 2017)". If the creditor is A and the loan is 3 million yen or less, , Can perform automatic consent. Therefore, it is determined whether or not the claim to be approved in the present case is “the creditor is A and the claim is 3 million yen or less”.

  If the verification is successful (Yes in step S309: the user number “2017” of the creditor “A” registered in the extracted record “X” and the user “A” indicated in the notification of the occurrence record request ), The electronic record receivables processing system 100 (data generation unit 108) automatically records the occurrence of the receivables addressed to the electronic receivable recording agency 120 in place of the debtor in step S311. Generates consent response data to the billing notification.

  That is, the data for transmitting the notification of the occurrence record request by the obligor claim method to the obligor received from the electronic receivable recording agency 120 to the obligor terminal 134 of the obligor “X” is the electronically recorded receivable processing system 100 ( It is not generated or transmitted by the data generation unit 108), and there is no trouble in answering the consent of the debtor "X".

  Note that the electronically recorded loan processing system 100 (data generation unit 108) automatically sends a response to the electronic debt recording agency 120 to the notification of the occurrence record request issued by the creditor “A” based on the contract. The data indicating the transmission may be generated and transmitted to the debtor terminal 134 of the debtor “X” via the communication control unit 102 as a mere notification to the debtor “X”.

  However, in the case where the debtor secures an opportunity to confirm and deny the contents of the electronic bond for which the creditor has requested the occurrence record request by the creditor request method, first in step S311, the data generation unit 108 Generates data for transmitting the notification of the occurrence record request by the creditor claim method to the debtor received from the recording organization 120 to the debtor terminal 134 of the debtor “X”, and the debtor via the communication control unit 102 The information is transmitted to the debtor terminal 134 of “X” and the information of the debtor “X” is extracted from the client management DB 106, and the attribute of the claim (for example, the amount of the claim, the creditor) described in the notification of the occurrence record request is It is determined whether the information is within the range specified in the information. If it is determined that the attribute of the claim described in the notification of the occurrence record request is within the range specified in the information, the electronically recorded claim processing system is performed. 100 (data generator 108), automatically place the debtor, and generates answer data for acceptance of generating recording notification request for Electronic receivable recording engine 120 addressed. As a result, it is possible to secure an opportunity for the debtor to confirm and deny the contents of the electronic receivable, and to avoid “deemed denial” caused by not receiving a response from the debtor within a predetermined period.

  In step S313, the electronically recorded bond processing system 100 (the communication control unit 102) transmits the generated consent response data to the electronic bond recording organization 120. The electronically recorded receivables processing system 100 can update the record management of the processing history information by recording the date and time of transmission of the consent notification and setting the consent notification transmission type to “setting” (FIG. 4).

  If the verification fails (No in step S309: “X” is not a service user, or the creditor's user number registered in the extracted record of “X” and the notification of the occurrence record request are displayed) In the case where the user number “2017” of the user “A” does not match), the electronically recorded loan processing system 100 (data generation unit 108) in step S315 executes Data for transmitting the notice of the occurrence record request to the debtor by the creditor claim method received from the debtor 120 to the debtor terminal 134 of the debtor “X” is generated, and the debtor “X” is transmitted via the communication control unit 102. "To the debtor terminal 134.

  In step S317, the electronically recorded receivables processing system 100 (communication control unit 102) receives an acceptance response from the debtor terminal 134 of the debtor "X". In response to receiving the response, the electronically recorded receivables processing system 100 (data generation unit 108) generates consent response data, and transmits the data to the electronic receivable recording organization 120 via the communication control unit 102 in step S313.

  The electronically recorded receivables processing system 100 can update the record management of the processing history information by recording the consent notice transmission date and time and setting the consent notification transmission type to "normal" (FIG. 4). Thereby, on the processing history information, it can be distinguished from the automatic transmission of the response data of the consent by the electronically recorded receivables processing system 100 in step S313.

  In step S319, the electronically recorded receivables processing system 100 (communication control unit 102) notifies the electronically receivables recording facility 120 of the notification of the occurrence record of the electronically recorded receivable addressed to the creditor “A” and the electronically recorded receivables addressed to the debtor “X”. Receive notification of occurrence record.

  In step S321, the electronically recorded receivables processing system 100 (data generation unit 108) transmits a notification of the occurrence record of the electronically recorded receivable to the creditor terminal 132 of the creditor “A” and the debtor terminal 134 of the debtor “X”. 6 is generated and transmitted to the creditor terminal 132 of the creditor “A” and the debtor terminal 134 of the debtor “X” via the communication control unit 102, and the flow in FIG. 6 ends.

  It should be noted that the request for requesting the generation and recording of an electronically recorded claim by the creditor request method and the means for requesting the generation and recording of an electronically recorded claim are not essential components in this embodiment. As a result, the operation and effect of the present invention can be exerted even when a request for the generation and recording of an electronically recorded claim is made from another financial institution.

  As described above, according to the electronically recorded claim processing method of the present embodiment, the burden on the debtor in the creditor claim method can be reduced, and a highly convenient electronically recorded claim processing system, processing method, and processing A device can be provided.

  100: Electronically Recorded Claim Processing System, 102: Communication Control Unit, 104: Collation Unit, 106: Client Management DB, 108: Data Generation Unit, 110: History Management DB, 120: Electronic Claim Recording Institution, 122: Record Master DB, 132: creditor terminal, 134: debtor terminal

Claims (6)

  A receiving unit that receives a notification of the occurrence record request addressed to the debtor from the electronic credit recording organization, and a transmission unit that transmits an acceptance reply to the notification to the electronic credit recording organization when the attribute of the bond is within a predetermined range. , With electronic record receivables processing system.   2. The electronically recorded claim processing system according to claim 1, wherein the transmission unit transmits a request for an electronically recorded claim requesting the generation of an electronically recorded claim by a creditor claim method to the electronically claimable recording facility.   2. The electronically recorded claim processing system according to claim 1, wherein the attribute of the claim is a claim amount.   2. The electronically recorded loan processing system according to claim 1, wherein the attribute of the bond is a creditor.   The receiving unit receives the notification of the request for the occurrence record addressed to the debtor from the electronic credit recording organization, and the transmitting unit transmits an acceptance reply to the electronic credit recording organization to the electronic credit recording organization when the attribute of the bond is within a predetermined range. To process electronically recorded receivables.   A receiving unit that receives a notification of a request for an occurrence record addressed to a debtor from an electronic credit recording organization, and transmits an acceptance reply to the electronic credit recording organization to the electronic credit recording organization when the attribute of the credit is within a predetermined range. A program that operates as an electronically recorded loan processing system having a transmission unit.

Images