JP7286277B2 - Electronically Recorded Monetary Claims Management Method, Management Server and Management Program - Google Patents

Description

The present invention relates to an electronically recorded monetary bond management method, a management server, and a management program.

Conventionally, electronically recorded monetary claims have been widely used as means of settlement. Electronically Recorded Monetary Claims users (obligees and obligors) can record electronically recorded Procedures such as assignment and payment can be performed (Patent Document 1).

JP 2011-175571 A

Electronically Recorded Monetary Claims transaction procedures include generation, modification, guarantee and payment transactions of Electronically Recorded Monetary Claims (hereinafter referred to as "acceptance response transactions") that require the user's acceptance or rejection.

In the acceptance/rejection response transaction, the user can individually confirm the acceptance/rejection status for each electronically recorded monetary claim by making an application inquiry or a notification inquiry for acceptance/rejection.

However, there is a problem that it is not easy for the user to confirm the acceptance/rejection status because the procedure for checking individual acceptance/rejection status for each electronically recorded monetary claim is complicated.

Accordingly, one of the objects of the present invention is to enable the user to easily confirm the acceptance/rejection status of each electronically recorded monetary claim.

According to an embodiment of the present invention, a rewriting unit that rewrites response status information stored in a database in association with an electronically recorded monetary bond upon receipt of acceptance/rejection response information for an electronically recorded monetary bond; and a list display information generating unit that generates list display information of answer status information that satisfies the above.

The response status information may correspond to any of non-response, acceptance and denial for acceptance/rejection transaction of electronically recorded monetary claims.

The rewriting unit may rewrite the answer status information from "unanswered" to "accepted" or "denied."

Electronically recorded monetary claims that meet predetermined conditions may include electronically recorded monetary claims that are specific obligees.

In response to a request from a terminal, the list display information generation unit provides a list display for displaying a list of electronically recorded monetary claims for which the user of the terminal is the obligee and response status information associated with the electronically recorded monetary claims. information may be generated.

Electronically recorded monetary claims that meet predetermined conditions may include electronically recorded monetary claims that are specific obligors.

In response to a request from a terminal, the list display information generation unit provides a list display for displaying a list of electronically recorded monetary claims for which the user of the terminal is the obligor and response status information associated with the electronically recorded monetary claims. information may be generated.

The electronically recorded monetary claims that meet predetermined conditions may include electronically recorded monetary claims for which the response status information is unanswered.

The rewriting unit may rewrite the response status information from non-response to deemed denial when a predetermined time has elapsed since the electronically recorded monetary claim was stored in the database.

When the rewriting unit receives the acceptance/rejection response information for acceptance/rejection response transactions for electronically recorded monetary claims, if a predetermined time has passed since the electronically recorded monetary claims were stored in the database, the rewriting unit regards the response status information as unanswered. It can be rewritten as denial.

According to one embodiment of the present invention, a management server connected to a database that associates and stores electronically recorded monetary claims and response status information corresponding to either non-response, acceptance, or denial of acceptance or rejection transactions for electronically recorded monetary claims In the method of execution, when acceptance/rejection response information for acceptance/rejection transaction of electronically recorded monetary claims is received, response status information of said electronically recorded monetary claims is rewritten from non-response to acceptance/rejection according to said acceptance/rejection response information, and reference is made to the database. Then, there is provided a management method for generating list display information for displaying a list of electronically recorded monetary claims satisfying predetermined conditions and response status information associated with the electronically recorded monetary claims.

According to one embodiment of the present invention, a computer stores electronically recorded monetary claims and response status information in a database that associates and stores response status information corresponding to either non-response, acceptance, or denial of electronically recorded monetary claims A rewriting unit that rewrites information, and upon receiving acceptance/rejection reply information for acceptance/rejection reply transactions of electronically recorded monetary claims, rewrites the answer status information of said electronically recorded monetary claims from non-response to acceptance or denial according to said acceptance/rejection reply information. and a list display information generation unit that refers to the database and generates list display information for displaying a list of electronically recorded monetary claims that meet predetermined conditions and response status information associated with the electronically recorded monetary claims. program is offered.

According to the present invention, the user can easily confirm the acceptance/rejection status for each electronically recorded monetary claim.

1 is a configuration diagram showing an electronically recorded monetary bond processing system according to an embodiment of the present invention; FIG. 3 is a configuration diagram showing the functional configuration of a management device according to one embodiment of the present invention; FIG. 4 is a diagram showing a management database of a storage unit of the management device according to one embodiment of the present invention; FIG. 1 is a flow chart showing a method of processing electronically recorded monetary claims according to an embodiment of the present invention; FIG. 4 is a diagram showing a management database of a storage unit of the management device according to one embodiment of the present invention; FIG. 1 is a flow chart showing an electronically recorded monetary bond processing method according to an embodiment of the present invention. 1 is a flow chart showing an electronically recorded monetary bond processing method according to an embodiment of the present invention. 1 is a flow chart showing a method of processing electronically recorded monetary claims according to an embodiment of the present invention; FIG. 4 is a diagram showing a management database of a storage unit of the management device according to one embodiment of the present invention; FIG. 1 is a flow chart showing a method of processing electronically recorded monetary claims according to an embodiment of the present invention; FIG. 4 is a diagram showing a management database of a storage unit of the management device according to one embodiment of the present invention; FIG. 1 is a flow chart showing a method of processing electronically recorded monetary claims according to an embodiment of the present invention; FIG. 4 is a diagram showing a management database of a storage unit of the management device according to one embodiment of the present invention; FIG. 1 is a flow chart showing a method of processing electronically recorded monetary claims according to an embodiment of the present invention; FIG. 4 is a diagram showing a management database of a storage unit of the management device according to one embodiment of the present invention; FIG. 1 is a flow chart showing an electronically recorded monetary bond processing method according to an embodiment of the present invention. 1 is a flow chart showing a method of processing electronically recorded monetary claims according to an embodiment of the present invention; FIG. 4 is a diagram showing a management database of a storage unit of the management device according to one embodiment of the present invention; FIG. 1 is a flow chart showing a method of processing electronically recorded monetary claims according to an embodiment of the present invention; FIG. FIG. 4 is a diagram showing a list of electronically recorded monetary claims displayed on a user terminal according to one embodiment of the present invention; FIG. 4 is a diagram showing a list of electronically recorded monetary claims displayed on a user terminal according to one embodiment of the present invention; FIG. 4 is a diagram showing a list of electronically recorded monetary claims displayed on a user terminal according to one embodiment of the present invention; FIG. 4 is a diagram showing a list of electronically recorded monetary claims displayed on a user terminal according to one embodiment of the present invention; 1 is a flow chart showing an electronically recorded monetary bond processing method according to an embodiment of the present invention.

Hereinafter, a method for managing electronically recorded monetary claims, a management server, and a management program according to an embodiment of the present invention will be described in detail with reference to the drawings. The embodiments shown below are examples of embodiments of the present invention, and the present invention is not limited to these embodiments.

(composition)
FIG. 1 is a configuration diagram showing an electronically recorded monetary bond processing system according to one embodiment of the present invention. FIG. 1 shows a recording institution server DN, a first financial institution server A1, a second financial institution server B1, a terminal C1 of an electronically recorded monetary bond user c1, and a terminal D1 of a user d1.

In this example, the user c1 is the obligee of the electronically recorded monetary bond, and the user d1 is the obligee of the electronically recorded monetary bond. That is, the user c1 is the creditor c1, the user d1 is the debtor d1, the terminal C1 is the creditor terminal C1, and the terminal D1 is the debtor terminal D1.

Note that the user d1 may be the obligee of the electronically recorded bond, and the user c1 may be the obligee of the electronically recorded bond. That is, the user d1 may be the creditor d1, the user c1 may be the debtor c1, the terminal D1 may be the creditor terminal D1, and the terminal C1 may be the debtor terminal C1.

The recording institution server DN, the first financial institution server A1, the second financial institution server B1, the creditor terminal C1, and the debtor terminal D1 are each connected via a network NW.

The first financial institution server A1 is the server of the financial institution that handles the creditor terminal C1. The first financial institution server A1 has an electronically recorded monetary bond management device MD, which will be described later. The creditor terminal C1 communicates information with the first financial institution server A1 via the electronically recorded credit management device MD.

The second financial institution server B1 is the server of the financial institution that handles the debtor terminal D1. The debtor terminal D1 communicates information with the second financial institution server B1.

The server of the teller financial institution of the debtor terminal D1 may be the first financial institution server A1. That is, the contact financial institution server of the creditor terminal C1 and the debtor terminal D1 may be the same first financial institution server A1.

(Functional configuration of management device)
FIG. 2 is a configuration diagram showing the functional configuration of the management device MD according to one embodiment of the present invention. The electronically recorded monetary bond management device MD of the first financial institution server A1 has a communication unit 102, a storage unit 104, and a control unit .

The communication unit 102 is a communication module that communicates with other devices via the network NW. In this example, communication takes place over the Internet. Other devices to be communicated with are the recording institution server DN, the second financial institution server B1 and the creditor terminal C1.

The storage unit 104 is a logical storage area. Specifically, they are a storage area inside the CPU, a main storage device, and an auxiliary storage device. The storage unit 104 stores programs for realizing various functions of the control unit 106 and a management database DB for managing information on electronically recorded monetary claims, which will be described later.

The program may be provided in a state stored in a computer-readable recording medium such as a magnetic recording medium, an optical recording medium, a magneto-optical recording medium, or a semiconductor memory. Each program may be downloaded via the network NW.

The management database DB may be provided as an external device to the management device MD.

Now, with reference to FIG. 3, the management database DB for managing information on electronically recorded monetary claims will be described. FIG. 3 is a diagram showing the management database DB of the storage unit 104 of the management device MD according to one embodiment of the present invention.

Information on electronically recorded monetary claims is stored in the management database DB. Information on electronically recorded monetary claims consists of identification information corresponding to identification numbers 1 to 6 for identifying electronically recorded monetary claims, and management information corresponding to obligee, obligor, financial institution, transaction details, transaction date, and acceptance/rejection status. including. The identification information and the management information are linked and stored in the management database DB.

Specifically, for identification numbers 1 to 6, obligee X1 to X6, obligee financial institution a1 to a4, obligor Y1 to Y6, obligor financial institution a1, b1 to b3, response contents of acceptance/rejection transaction , the transaction date, and the acceptance/rejection status are linked and stored in the management database DB.

As the transaction details, information corresponding to the acceptance/rejection transaction is stored. In this example, information corresponding to an accrual record request is stored. As the acceptance/rejection response transaction, information corresponding to a warranty record request, a change record request, and a payment record request may be stored.

In the transaction date, information corresponding to the date and time of the acceptance/rejection transaction is stored. In this example, the transaction date stores information corresponding to the date of the acceptance/rejection transaction.

The consent/refusal response status stores information corresponding to the consent/refusal response status of the user to the consent/refusal response transaction. The acceptance/rejection status includes acceptance, rejection, deemed rejection, and unanswered.

Returning to FIG. 2, the description continues. Control unit 106 has specifying unit 108 , rewriting unit 110 , reading unit 112 and list display information generating unit 114 . The functions of the identifying unit 108 , the rewriting unit 110 , the reading unit 112 and the list display information generating unit 114 are implemented by the programs of the storage unit 104 .

The identification unit 108 is a functional unit that identifies electronically recorded monetary claims that meet predetermined conditions.

For example, the identification unit 108 refers to the identification information received by the communication unit 102 and the identification information stored in the management database DB, and identifies an electronically recorded bond that satisfies the condition that both pieces of identification information match.

Also, for example, the identification unit 108 identifies electronically recorded monetary claims that satisfy the condition that a predetermined time has passed since the transaction date. The predetermined time can be set as appropriate. In this example, the predetermined time is set to 5 business days.

Also, for example, the identifying unit 108 identifies electronically recorded monetary claims that satisfy the condition that the acceptance/rejection status is unanswered.

Further, for example, the identification unit 108 identifies electronically recorded monetary claims that satisfy the condition that the information received by the communication unit 102 is establishment information, which will be described later.

The rewriting unit 110 is a functional unit that rewrites the management information stored in the management database DB into the management information of the electronically recorded monetary bond specified by the specifying unit 108 .

The reading unit 112 is a functional unit that reads identification information and management information of electronically recorded monetary claims stored in the management database DB. The reading unit 112 may read all items of the management information corresponding to the obligee, the debtor, the financial institution, the transaction details, the transaction date, and the acceptance/rejection status, or may read some items. In this example, the reading unit 112 reads all items of the management information.

The list display information generation unit 114 is a functional unit that generates list display information for displaying a list of identification information and management information read by the reading unit 112 from the management database DB.

In this example, the communication unit 102 transmits the generated list display information to the obligee terminal C1, and the obligee terminal C1 displays a list of the identification information and the management information on the obligee terminal C1 based on the list display information. .

FIG. 4 is a flow diagram showing a processing method for electronically recorded monetary claims according to one embodiment of the present invention. Specifically, FIG. 4 is a flow chart showing a processing method of electronically recorded monetary claims until obligee c1 notifies obligee d1 that he has made a request for record of the occurrence of electronically recorded monetary claims.

When the obligee's terminal C1 transmits recording request information for requesting recording of electronically recorded monetary claims to the first financial institution server A1, the flow of FIG. 4 starts (step S102). The record request information includes identification information and management information of electronically recorded monetary claims.

When receiving the record request information, the first financial institution server A1 stores the record request information in the management database DB (step S104). Specifically, the financial institution server A1 stores the identification information corresponding to the identification number 1, the obligee c1, the debtor d1, the financial institution b1, the occurrence record request as the acceptance/rejection transaction, and 2018 as the transaction date in the management database DB. January 11, 2011 and management information corresponding to unanswered as a yes/no answer status are stored.

After storing the recording request information in the management database DB, the financial institution server A1 transmits the recording request information to the recording institution server DN (step S106).

When receiving the recording request information, the recording institution server DN records the recording request information in the request receipt book (step S108).

When the recording request information is recorded in the request receipt book, the recording institution server DN transmits the recording request information to the second financial institution server B1 (step S110).

When the second financial institution server B1 receives the recording request information, it transmits the recording request information to the debtor terminal D1 (step S112), and inquires of the debtor d1 about acceptance or rejection, and the flow shown in FIG. 4 ends. .

Similarly to the electronically recorded monetary bond with identification number 1 described above, the flow shown in FIG.

FIG. 5 is a diagram showing the management database DB of the storage unit 104 of the management device MD according to one embodiment of the present invention. Specifically, FIG. 5 is a diagram showing the management database DB at the time when the first financial institution server A1 receives the record request information regarding the electronically recorded monetary claim with the identification number 4 from the creditor terminal C1.

As for the electronically recorded monetary claim with identification number 1, since the obligor d1 has neither consented nor denied the occurrence of the electronically recorded monetary claim, the status of acceptance or disapproval has not yet been answered. Electronically recorded monetary claims with identification numbers 2 to 4 are similarly unanswered as to acceptance/rejection status.

FIG. 6 is a flow chart showing an electronically recorded monetary bond processing method according to an embodiment of the present invention. Specifically, FIG. 6 is a flow chart showing an electronically recorded monetary bond processing method in which the first financial institution server A1 rewrites the acceptance/rejection response status of the management database DB to deemed rejection after the flow of FIG.

In this example, the specifying unit 108 automatically starts the flow once a day at a specified time. Note that the conditions for automatically starting the flow can be set as appropriate.

When the flow starts, the identifying unit 108 identifies electronically recorded monetary claims stored in the management database DB for which five business days have passed since the transaction date and for which the acceptance/rejection status has not yet been answered ( step S12).

When the identifying unit 108 identifies the electronically recorded monetary bond, the rewriting unit 110 rewrites the response status of the identified electronically recorded monetary bond from unanswered to deemed denied (step S14), and the flow shown in FIG. 6 ends.

FIG. 7 is a flow chart showing an electronically recorded monetary bond processing method according to an embodiment of the present invention. Specifically, FIG. 7 is a flow chart showing an electronically recorded monetary bond processing method in which the first financial institution server A1 rewrites the acceptance/rejection status of the management database DB to acceptance or rejection after the flow of FIG.

The flow shown in FIG. 7 starts when the first financial institution server A1 receives the successful information or the unsuccessful information from the recording institution server DN.

The establishment information is information corresponding to the fact that the obligor d1 has consented to the establishment of recording of the electronically recorded monetary claim. Further, the non-establishment information is information corresponding to the fact that the obligor d1 has denied the establishment of the recording of the electronically recorded monetary claim.

When the flow shown in FIG. 7 starts, the identification unit 108 identifies electronically recorded monetary claims identified based on the identification information included in the received establishment information or failure information (step S22).

Of the electronically recorded monetary claims identified by the identifying unit 108, for the electronically recorded monetary claims for which the acceptance/disapproval response status of the identified electronically recorded monetary claims has not yet been answered and the received information is establishment information (step S24: Yes, step S26: Yes), the rewriting unit 110 rewrites the acceptance/rejection status of the electronically recorded monetary claim from unanswered to accepted (step S28).

When the rewriting unit 110 rewrites the response status of the electronically recorded monetary claim from unanswered to accepted, the communication unit 102 transmits information on establishment of the electronically recorded monetary bond to the obligee terminal C1 (step S30), and the flow shown in FIG. finish.

Among the electronically recorded monetary claims identified by the identification unit 108, for the electronically recorded monetary claims for which the acceptance/disapproval response status of the identified electronically recorded monetary claims has not yet been answered and the received information is failure information (step S24: Yes , Step S26: No), the rewriting section 110 rewrites the acceptance/rejection status of the electronically recorded monetary claim from unanswered to rejection (step S32).

When the rewriting unit 110 rewrites the acceptance/rejection status of the electronically recorded monetary claim from unanswered to denied, the communication unit 102 transmits the electronically recorded monetary claim failure information to the obligee terminal C1 (step S34), and the flow shown in FIG. finish.

On the other hand, among the electronically recorded monetary claims specified by the specifying unit 108, for the electronically recorded monetary claims for which the acceptance/rejection response status of the specified electronically recorded monetary claims has not yet been answered (step S24: No), the acceptance/rejection response status is determined according to the flow shown in FIG. A deemed denial has been recorded as Therefore, the communication section 102 transmits the electronically recorded claim failure information to the obligee's terminal C1 (step S36), and the flow shown in FIG. 7 ends.

Below, the flow shown in FIGS. 6 and 7 will be described in more detail with reference to the flow charts of FIGS. 8 to 17 and the diagram showing the management database DB.

FIG. 8 is a flow diagram showing a processing method for electronically recorded monetary claims according to one embodiment of the present invention. Specifically, FIG. 8 shows the processing method for electronically recorded claims after the flow shown in FIG. It is a flow diagram showing .

When the debtor terminal D1 transmits to the second financial institution server B1 consent information for consenting to the content of the claim for recording the occurrence of the electronically recorded monetary claim identified by the identification number 1 (step S202), as shown in FIG. the flow to start.

Upon receiving the consent information, the second financial institution server B1 transmits the consent information to the recording institution server DN (step S204).

When the second financial institution server B1 transmits the approval information to the recording institution server DN, the recording institution server DN establishes the occurrence record (step S206).

After establishing the occurrence record, the recording institution server DN transmits establishment information for notifying the obligee c1 that the occurrence record has been established to the first financial institution server A1 (step S208).

When the first financial institution server A1 receives the establishment information from the recording institution server DN, it specifies the electronically recorded monetary claims related to the establishment information (step S210).

When the first financial institution server A1 identifies the electronically recorded monetary claim related to the establishment information, it rewrites the acceptance/rejection status of the identified electronically recorded monetary claim from unanswered to accepted (step S212).

The first financial institution server A1 rewrites the acceptance/rejection status of the identified electronically recorded monetary claim from unanswered to accepted, and then transmits establishment information to the obligee terminal C1 (step S214).

On the other hand, when the occurrence record is established, the recording institution server DN transmits establishment information for notifying the debtor d1 that the occurrence record is established to the second financial institution server B1 (step S216).

When receiving the establishment information from the recording institution server DN, the second financial institution server B1 transmits the establishment information to the debtor terminal D1 (step S218).

FIG. 9 is a diagram showing the management database of the storage unit of the management device according to one embodiment of the present invention. Specifically, FIG. 9 is a diagram showing the management database DB when the first financial institution server A1 receives establishment information from the recording institution server DN.

The acceptance/rejection status of the electronically recorded monetary claim identified by identification number 1 is rewritten from unanswered shown in FIG. 5 to accepted shown in FIG.

FIG. 10 is a flow diagram showing a processing method for electronically recorded monetary claims according to one embodiment of the present invention. Specifically, FIG. 10 shows, after the flow shown in FIG. 5, the electronic FIG. 4 is a flow diagram showing a method of processing recorded bonds.

When the obligor d1 transmits, from the obligor terminal D1 to the second financial institution server B1, denial information for denying the content of the request for recording the occurrence of the electronically recorded monetary claim identified by the identification number 2 (step S302), The flow shown in FIG. 10 begins.

When receiving the denial information, the second financial institution server B1 transmits the denial information to the recording institution server DN (step S304).

When receiving the denial information from the second financial institution server B1, the recording institution server DN does not establish the occurrence record (step S306).

If the recording institution server DN does not establish the occurrence record, it transmits to the first financial institution server A1 failure information for notifying the obligee c1 that the occurrence record has not been established (step S308).

When the first financial institution server A1 receives the unsuccessful information from the recording institution server DN, it identifies the electronically recorded monetary claim related to the unsuccessful information (step S310).

When the first financial institution server A1 identifies the electronically recorded monetary claim related to the failure information, it rewrites the acceptance/rejection status of the identified electronically recorded monetary claim from unanswered to rejected (step S312).

When the first financial institution server A1 rewrites the acceptance/rejection status of the specified electronically recorded monetary claim from non-response to rejection, it transmits failure information to the obligee terminal C1 (step S314).

On the other hand, if the recording institution server DN does not establish the occurrence record, it transmits non-establishment information for notifying the debtor d1 that the occurrence record has not been established in the second financial institution server B1 (step S316).

When the second financial institution server B1 receives the failure information from the recording institution server DN, it transmits the failure information to the debtor terminal D1 (step S318), and the flow shown in FIG. 10 ends.

FIG. 11 is a diagram showing the management database of the storage unit of the management device according to the embodiment of the present invention; Specifically, FIG. 11 is a diagram showing the management database DB when the first financial institution server A1 receives the failure information from the recording institution server DN.

The acceptance/rejection status of the electronically recorded monetary claim identified by the identification number 2 is rewritten from unanswered shown in FIG. 5 to denied as shown in FIG.

FIG. 12 is a flow diagram showing a processing method for electronically recorded monetary claims according to one embodiment of the present invention. Specifically, FIG. 12 shows that after the flow shown in FIG. 5, five business days have passed without the obligee d1 giving consent or denial to the obligee c1 about the contents of the request for recording the occurrence of electronically recorded monetary claims. FIG. 3 is a flowchart showing a method of processing electronically recorded monetary claims;

If five business days have passed without the obligee d1 agreeing or denying the content of the request for recording the occurrence of the electronically recorded claim to the obligee c1, the recording institution server DN does not establish the occurrence record (step S402). The flow shown in FIG. 12 begins.

If the recording institution server DN does not establish the accrual record, it transmits to the first financial institution server A1 failure information for notifying the obligee c1 that the accrual record of the electronically recorded monetary claim has not been established (step S404). .

When the first financial institution server A1 receives the unsuccessful information from the recording institution server DN, it identifies the electronically recorded monetary claim related to the unsuccessful information (step S406).

When the first financial institution server A1 specifies the electronically recorded monetary claim related to the failure information, it rewrites the acceptance/rejection status of the specified electronically recorded monetary claim from unanswered to deeming rejection (step S408).

When the first financial institution server A1 rewrites the approval/disapproval response status of the specified electronically recorded monetary claim from unanswered to deemed denial, it transmits failure information to the obligee terminal C1 (step S410).

On the other hand, the recording institution server DN, if the occurrence record is not established, transmits failure information for notifying the debtor d1 that the occurrence record was not established in the second financial institution server B1 (step S412).

When the second financial institution server B1 receives the failure information from the recording institution server DN, it transmits the failure information to the debtor terminal D1 (step S414), and the flow shown in FIG. 12 ends.

FIG. 13 is a diagram showing the management database of the storage unit of the management device according to the embodiment of the present invention; Specifically, FIG. 13 is a diagram showing the management database DB when the first financial institution server A1 receives the failure information from the recording institution server DN.

The approval/disapproval reply status of the electronically recorded monetary claim identified by the identification number 3 has been rewritten from unanswered shown in FIG. 5 to presumed denial according to the flow shown in FIG.

FIG. 14 is a flow diagram showing a processing method for electronically recorded monetary claims according to one embodiment of the present invention. Unlike FIG. 4, in FIG. 14 c1 is the debtor and d1 is the creditor. Specifically, FIG. 14 is a flow chart showing a method of processing an electronically recorded monetary bond until the obligee d1 notifies the obligee c1 that the obligee d1 has requested the recording of the occurrence of the electronically recorded monetary bond to the obligee c1.

When the obligee terminal D1 transmits record request information for requesting the record of occurrence to the second financial institution server B1 (step S502), the flow of FIG. 14 starts.

When the second financial institution server B1 receives the record request information, it transmits the record request information to the recording institution server DN (step S504).

Upon receiving the recording request information, the recording institution server DN records the recording request information in the request receipt book (step S506).

When the recording request information is recorded in the request receipt book, the recording institution server DN transmits the recording request information to the first financial institution server A1 (step S508).

When receiving the recording request information from the recording institution server DN, the first financial institution server A1 stores the recording request information in the management database DB (step S510). Specifically, the financial institution server A1 stores the identification information corresponding to the identification number 5, the creditor d1, the debtor c1, the financial institution b1, the occurrence record request as the acceptance/rejection transaction, and 2018 as the transaction date in the management database DB. January 11, 2011 and management information corresponding to unanswered as a yes/no answer status are stored.

After storing the record request information in the management database DB, the financial institution server A1 transmits the record request information to the debtor terminal C1 (step S512), and the flow shown in FIG. 14 ends.

As with the electronically recorded monetary bond with identification number 5 described above, the flow shown in FIG. 14 is sequentially performed for the electronically recorded monetary bond with identification number 6 as well.

FIG. 15 is a diagram showing the management database of the storage unit of the management device according to the embodiment of the present invention; Specifically, FIG. 15 is a diagram showing the management database DB at the time when the first financial institution server A1 receives the record request information for the electronically recorded monetary bond related to the identification number 6 from the recording institution server DN.

Regarding the electronically recorded monetary claim with identification number 5, since the obligor c1 has neither accepted nor denied the occurrence of the electronically recorded monetary claim, the status of acceptance/rejection has not yet been answered. Electronically recorded monetary claims with identification number 6 are similarly unanswered as to acceptance or rejection.

FIG. 16 is a flow chart showing an electronically recorded monetary bond processing method according to an embodiment of the present invention. Specifically, FIG. 16 is a flow chart showing an electronically recorded monetary claim processing method in which, after the flow of FIG. 14, the first financial institution server A1 rewrites the acceptance/rejection status of the management database DB to acceptance or rejection.

The flow shown in FIG. 16 starts when the first financial institution server A1 receives approval information or denial information from the debtor terminal C1.

The consent information is information corresponding to the fact that the obligor c1 has consented to the recording of the electronically recorded monetary claim. The denial information is information corresponding to the fact that the obligor c1 has denied the recording establishment of the electronically recorded monetary claim.

When the flow shown in FIG. 16 starts, the identification unit 108 identifies electronically recorded monetary claims identified based on the identification information included in the received consent information or denial information (step S42).

Of the electronically recorded monetary claims identified by the identifying unit 108, for the electronically recorded monetary claims for which the received information is acceptance information (step S44: Yes), the rewriting unit 110 rewrites the acceptance/rejection status of the electronically recorded monetary claims from unanswered to accepted. (Step S46).

When the rewriting unit 110 rewrites the response status of the electronically recorded monetary claim from unanswered to accepted, the communication unit 102 transmits the acceptance information of the electronically recorded monetary claim to the obligee terminal C1 (step S48), and the flow shown in FIG. finish.

Further, among the electronically recorded monetary claims specified by the specifying unit 108, for the electronically recorded monetary claims for which the received information is the denial information (step S44: No), the rewriting unit 110 changes the response status of the electronically recorded monetary claims from unanswered to denial. (step S50).

When the rewriting unit 110 rewrites the acceptance/rejection status of the electronically recorded monetary claim from unanswered to denial, the communication unit 102 transmits the electronically recorded monetary claim denial information to the obligee terminal C1 (step S52), and the flow shown in FIG. finish.

FIG. 17 is a flow diagram showing a processing method for electronically recorded monetary claims according to one embodiment of the present invention. Specifically, FIG. 16 shows, after the flow shown in FIG. 14, the electronic FIG. 4 is a flow diagram showing a method of processing recorded bonds.

When the debtor terminal C1 transmits to the first financial institution server A1 consent information for consenting to a claim for recording the occurrence of the electronically recorded monetary claim identified by the identification number 5 (step S602), the flow of FIG. 17 starts. .

When the first financial institution server A1 receives the consent information, it identifies the electronically recorded monetary claims related to the consent information (step S604).

When the first financial institution server A1 specifies the electronically recorded monetary claim related to the acceptance information, it changes the response status of the specified electronically recorded monetary claim from unanswered to accepted (step S606).

When the first financial institution server A1 rewrites the acceptance/rejection status of the specified electronically recorded monetary claim from unanswered to accepted, it transmits the acceptance information to the recording institution server DN (step S608).

When receiving the approval information from the first financial institution server A1, the recording institution server DN establishes the occurrence record (step S610).

After establishing the occurrence record, the recording institution server DN transmits establishment information for notifying the debtor c1 that the occurrence record has been established in the first financial institution server A1 (step S612).

When the first financial institution server A1 receives the establishment information, it transmits the establishment information to the debtor terminal C1 (step S614).

When the recording institution server DN establishes the occurrence record, it transmits establishment information for notifying the obligee d1 that the occurrence record has been established in the second financial institution server B1 (step S616).

Upon receiving the establishment information, the second financial institution server B1 transmits the establishment information to the creditor terminal D1 (step S618), and the flow shown in FIG. 17 ends.

FIG. 18 is a diagram showing the management database of the storage unit of the management device according to the embodiment of the present invention; Specifically, FIG. 18 shows the management database DB when the first financial institution server A1 receives the consent information from the debtor terminal C1.

The acceptance/rejection status of the electronically recorded monetary claim identified by the identification number 5 is rewritten from unanswered as shown in FIG. 5 to accepted as shown in FIG.

(Request for listing)
FIG. 19 is a flow diagram showing a processing method for electronically recorded monetary claims according to one embodiment of the present invention. Specifically, in FIG. 19, the obligee c1 requests the first financial institution server A1 to display a list of electronically recorded monetary claims for which the acceptance/rejection status has not yet been answered, and receives the list display information from the first financial institution server A1. FIG. 10 is a flow chart showing a method of processing electronically recorded monetary claims up to and including;

When the obligee terminal C1 transmits to the financial institution server A1 the list display request information for displaying a list of only the electronically recorded monetary claims for which the reply status of the electronically recorded monetary claims has not yet been answered (step S702), the flow of FIG. starts.

When receiving the list display request information, the first financial institution server A1 refers to the acceptance/rejection response status of the management database DB, and reads out only the electronically recorded monetary claims for which responses have not been completed (step S704).

When the first financial institution server A1 reads out only the electronically recorded monetary claims in the unanswered state, it generates list display information for displaying a list of only the electronically recorded monetary claims in the unanswered state (step S706).

After generating the list display information, the first financial institution server A1 transmits the list display information to the creditor terminal C1 (step S708), and the flow shown in FIG. 19 ends.

(List display screen)
FIG. 20 is a diagram showing a list of electronically recorded monetary claims displayed on the terminal C1 of the user c1 according to one embodiment of the present invention. Specifically, FIG. 20 is a diagram showing a list display screen EX on the terminal C1 after the flow of FIG. 19, displaying a list of electronically recorded monetary claims that have not yet been answered.

In this example, the electronically recorded monetary claims relating to the identification numbers 4 and 6 in the management database DB have not yet been responded to, so the terminal C1 of the user c1 sends the identification information and management information relating to the electronically recorded monetary claims with the identification numbers 4 and 6. are listed.

Therefore, the user c1 can easily confirm the electronically recorded monetary claims for which the reply has not yet been made. User c1 can prevent omission of acceptance/rejection of electronically recorded monetary claims related to acceptance/rejection transactions by requesting acceptance/rejection from counterparty user d1 or by replying acceptance/rejection.

FIG. 21 is a diagram showing a list of electronically recorded monetary claims displayed on terminal C1 of user c1 according to an embodiment of the present invention. Specifically, FIG. 21 is a view showing a list display screen EX on the terminal C1, after the flow of FIG. 19, displaying a list of electronically recorded monetary claims for which the user c1 is the obligee.

In this example, the user c1 is the obligee of the electronically recorded monetary claims related to the identification numbers 1 to 4 in the management database DB. and management information are listed.

Therefore, the user c1 can easily confirm the electronically recorded monetary claims for which he/she is the obligee. User c1 can prevent omission of acceptance/rejection of electronically recorded monetary claims related to acceptance/rejection transactions by requesting acceptance/rejection from counterparty user d1. Further, the user c1 can easily confirm whether or not the debt is collected.

FIG. 22 is a diagram showing a list of electronically recorded monetary claims displayed on the terminal C1 of the user c1 according to one embodiment of the present invention. Specifically, FIG. 22 is a view showing a list display screen EX displaying a list of electronically recorded monetary claims for which the user c1 is the obligor on the terminal C1 after the flow of FIG.

In this example, the user c1 is the obligor of the electronically recorded monetary claims related to the identification numbers 5 and 6 in the management database DB. and management information are listed.

Therefore, the user c1 can easily confirm the electronically recorded monetary claims for which he/she is the obligor. By replying yes or no to the counterpart user d1, the user c1 can prevent omission of yes or no reply of the electronically recorded monetary claims related to the yes or no reply transaction. Moreover, the user c1 can easily confirm whether or not payment has been made.

FIG. 23 is a diagram showing a list of electronically recorded monetary claims displayed on terminal C1 of user c1 according to an embodiment of the present invention. Specifically, FIG. 20 is a diagram showing a list display screen EX displayed for the user c1 after the flow of FIG. 19 .

In this example, the user c1 is the obligor of the electronically recorded monetary claims related to the identification numbers 1 to 6 in the management database DB. and management information are listed.

Therefore, the user c1 can easily confirm the electronically recorded monetary claims for which he or she is the obligee or obligor. User c1 can prevent omission of acceptance/rejection of electronically recorded monetary claims related to acceptance/rejection transactions by requesting acceptance/rejection from counterparty user d1 or by replying acceptance/rejection. Further, the user c1 can easily confirm whether or not the debt is collected and paid.

As described above, according to one embodiment of the present invention, the identification number, the obligee, the obligor, the transaction, the date of the transaction, and the acceptance/rejection status of a specific electronically recorded monetary claim are linked, and the management information is stored on the obligee's terminal. Can be listed. Therefore, the user can easily confirm the acceptance/rejection status for each electronically recorded monetary claim.

(Modification)
FIG. 24 is a flow chart showing an electronically recorded monetary bond processing method according to an embodiment of the present invention. Specifically, FIG. 24 shows an electronic record in which the first financial institution server A1 rewrites the approval/disapproval response status of the management database DB to approval, denial, or deemed denial instead of FIGS. 6 and 7 after the flow of FIG. It is a flowchart which shows the processing method of a claim.

The flow of FIG. 24 starts when the first financial institution server A1 receives establishment information or non-establishment information from the recording institution server DN.

When the flow of FIG. 24 starts, the identification unit 108 identifies the electronically recorded monetary claim identified by the received establishment information or failure information (step S62).

Of the electronically recorded monetary claims identified by the identification unit 108, for the electronically recorded monetary claims for which the received information is establishment information (step S64: Yes), the rewriting unit 110 rewrites the acceptance/rejection status of the electronically recorded monetary claims from unanswered to accepted. (Step S66).

When rewriting unit 110 rewrites the acceptance/rejection status of the electronically recorded monetary claim from unanswered to accepted, it transmits electronically recorded monetary claim establishment information to obligee terminal C1 (step S68), and the flow shown in FIG. 21 ends.

Among the electronically recorded monetary claims identified by the identification unit 108, for the electronically recorded monetary claims for which the received information is non-formation information and five business days have not passed since the transaction date of the identified electronically recorded monetary claims (step S64: No, step S70: No), the rewriting unit 110 rewrites the acceptance/rejection status of the electronically recorded monetary bond from unanswered to rejection (step S72).

When the response status of the electronically recorded monetary claim is changed from unanswered to rejected, the rewriting unit 110 transmits electronically recorded monetary claim failure information to the obligee's terminal C1 (step S74), and the flow shown in FIG. 24 ends.

On the other hand, among the electronically recorded monetary claims identified by the identifying unit 108, for the electronically recorded monetary claims for which the received information is information about failure to establish and five business days have passed since the transaction date of the identified electronically recorded monetary claims (step S64: No, step S70: Yes), the rewriting unit 110 rewrites the acceptance/rejection status of the electronically recorded monetary bond from unanswered to deemed rejection (step S76).

When the rewrite unit 110 rewrites the acceptance/rejection status from unanswered to deemed rejection, it transmits electronically recorded monetary claim failure information to the obligee terminal C1 (step S78), and the flow of FIG. 24 ends.

In this way, unlike the above-described embodiment, in which the elapse of five business days is determined based on the reception of information from the recording institution server DN, in the modified example, the first financial institution server A1 The progress of 5 business days is determined once a day.

According to this modification, it is also possible to link the identification number, the obligee, the obligor, the transaction, the date of the transaction, and the acceptance/rejection status for a specific electronically recorded monetary bond, and display a list of management information on the obligee's terminal. Therefore, the user can easily confirm the acceptance/rejection status for each electronically recorded monetary claim.

As described above, according to the method of processing electronically recorded monetary claims according to the present embodiment, the user can easily confirm the status of the acceptance or rejection of each electronically recorded monetary claim, thereby providing a highly convenient management method for electronically recorded monetary claims. , a management device and a management program can be provided.

A1: first financial institution server, a1: first financial institution, B1: second financial institution server, b1: second financial institution, C1, D1: user terminal, c1, d1: user, DN: recording institution server , NW: network, 102: communication unit, 104: storage unit, 106: control unit, 108: identification unit, 110: rewrite unit, 112: reading unit, 114: list display information generation unit, MD: management device, DB: Management database, EX: list display screen

Claims (7)

a rewriting unit that rewrites the response status information stored in the database in association with the electronically recorded monetary claim upon receiving acceptance or rejection response information for the electronically recorded monetary bond;
a list display information generating unit that refers to the database and generates list display information of the answer status information that satisfies a predetermined condition;
The list display information generation unit generates list display information of electronically recorded monetary claims for which the reply status information has not yet been answered in response to a request from the terminal ,
The management server, wherein the electronically recorded monetary claims included in the list display information are electronically recorded monetary claims for which the user of the terminal is the obligee or obligor. 2. The management server according to claim 1, wherein said response status information corresponds to one of non-response, acceptance and denial for acceptance/rejection response transactions of said electronically recorded monetary claims. 3. The management server according to claim 1, wherein the rewriting unit rewrites the reply status information from unanswered to accepted or rejected. 4. The rewriting unit according to any one of claims 1 to 3, wherein when a predetermined period of time has passed since the electronically recorded monetary claim was stored in the database, the rewriting unit rewrites the response status information from non-response to deemed denial. Management server listed. When receiving acceptance/rejection response information for acceptance/rejection response transactions of the electronically recorded monetary claims, the rewriting unit updates the response status information if a predetermined time has passed since the electronically recorded monetary claims were stored in the database. 4. The management server according to any one of claims 1 to 3, which rewrites non-response to deemed denial. A method executed by a management server connected to a database that associates and stores electronically recorded monetary claims and response status information corresponding to either non-response, acceptance, or denial of acceptance or rejection transactions for electronically recorded monetary claims, comprising:
Upon receiving the acceptance/rejection reply information for the acceptance/rejection reply transaction of the electronically recorded monetary claim, rewriting the reply status information of the electronically recorded monetary claim from unanswered to acceptance or rejection according to the acceptance/rejection reply information,
Referencing the database to generate list display information for displaying a list of the electronically recorded monetary claims satisfying a predetermined condition and the response status information associated with the electronically recorded monetary claims, the request from the terminal. according to, generating list display information of electronically recorded monetary claims for which the reply status information has not yet been answered;
The management method, wherein the electronically recorded monetary claims included in the list display information are electronically recorded monetary claims for which a user of the terminal is an obligee or an obligor. the computer,
A rewriting unit that rewrites the response status information in a database that stores electronically recorded monetary claims and response status information that corresponds to either unanswered, approval, or denial of the acceptance/rejection transaction of the electronically recorded monetary claims in association with each other, wherein the electronic record a rewriting unit that, upon receiving acceptance/rejection response information for an acceptance/rejection response transaction of a claim, rewrites the response status information of the electronically recorded monetary claim from unanswered to acceptance or rejection in accordance with the acceptance/rejection response information;
A list display information generating unit that refers to the database and generates list display information for displaying a list of the electronically recorded monetary claims satisfying a predetermined condition and the response status information associated with the electronically recorded monetary claims, A program for functioning as a list display information generation unit that generates list display information of electronically recorded monetary claims for which the reply status information has not yet been answered in response to a request from a terminal,
The program, wherein the electronically recorded monetary claims included in the list display information are electronically recorded monetary claims for which the user of the terminal is the obligee or obligor.

Images