JP6131133B2 - Electronically recorded bond information processing apparatus, electronically recorded bond information processing method, and program - Google Patents

Description

  The present invention relates to an electronically recorded bond information processing apparatus, an electronically recorded bond information processing method, and a program.

Electronically recorded receivables that manage receivables electronically are used (see Patent Document 1). With electronically recorded receivables, there is no need to manage paper receivables such as bills, which can reduce the burden on administrators and reduce receivable management costs.
In addition, Densai Net, which handles electronically recorded receivables, can make a collective record request for a collective record of bond occurrence records, transfer records, or split records.

JP 2012-14300 A

In each recording request included in the collective recording request, a previous date can be specified as a recording date, and a different recording date can be specified for each recording request. Therefore, the notification of the result of occurrence record, transfer record, or division record transmitted by the electronic bond net on the recording date is transmitted for each recording request (for each electronically recorded bond).
For this reason, Densai Net users need to check the result every time a result notification is sent. In particular, the user needs to count the number of result notifications received in order to determine whether or not all the result notifications to be sent on that day have been received, which is troublesome for the user.

  The present invention has been made in consideration of such circumstances, and an object of the present invention is to provide an electronic record loan information processing apparatus and electronic record bond information processing that can make it easier for a user to grasp the result of a collective record request. It is to provide a method and program.

  SUMMARY OF THE INVENTION The present invention has been made to solve the above-described problems, and an electronic record loan information processing apparatus according to an aspect of the present invention specifies a record date of a previous date, A collective billing information storage unit for storing information relating to a collective record request for a plurality of electronic record receivables, and a recording date for recording requests to be recorded in a record ledger of the electronic record receivables managed by An aggregation unit that generates aggregated information that is aggregated for each batch recording request stored in the batch billing information storage unit, for each recording date, and sent to the electronic bills from the recording organization for the recording bill. It is characterized by that.

  An electronic record loan information processing apparatus according to an aspect of the present invention is the above-described electronic record bond information processing apparatus, wherein when a recording request is canceled before a recording date, the information indicating the canceled recording request is A cancellation processing unit is provided for adding information related to the batch recording request stored in the batch billing information storage unit, and the aggregation unit generates the aggregate information reflecting the canceled recording request.

  An electronically recorded bond information processing apparatus according to an aspect of the present invention is the above-described electronically recorded bond information processing apparatus that stores at least one of information relating to insolvency that has occurred and information relating to forced execution that has been performed. A non-successful factor information storage unit, and the aggregating unit relates to information on an unrecorded electronic record receivable due to inability to pay, or an unrecorded electronic record receivable due to forced execution The aggregate information including at least one of the information is generated.

  The electronic record receivable information processing method according to one aspect of the present invention records a record relating to an electronic record receivable in a record ledger of an electronic record receivable managed by a recording organization of the electronic record receivable by specifying a recording date of the previous date. An electronic record receivable information processing method for an electronic record receivable information processing apparatus comprising a collective claim information storage unit for storing information related to collective record requests collectively for a plurality of electronic record receivables, An aggregation step of generating aggregated information that is aggregated for each batch recording request stored in the collective billing information storage unit, for each recording date, with respect to a recording request transmitted from the recording institution for each electronically recorded bond when the day arrives It is characterized by comprising.

  Further, the program according to one aspect of the present invention specifies a recording date of the previous date, and records to request to record a record relating to the electronic record receivable in a record ledger of the electronic record receivable managed by the recording authority of the electronic record receivable When the recording date arrives at the computer that controls the electronic record claim information processing apparatus having the collective claim information storage unit that stores information related to the collective record request for a plurality of electronic record claims, the record authority records the electronic records. This is a program for executing an aggregation step for generating aggregated information that is aggregated for each collective recording request stored in the collective billing information storage unit, for each recording date, and for the recording request transmitted for each bond.

  According to this invention, it is possible to make it easier for the user to grasp the result of the batch recording request.

It is a schematic block diagram which shows the apparatus structure of the electronic record loan system in one Embodiment of this invention. It is a schematic block diagram which shows the function structure of the electronic record bond information processing apparatus in the embodiment. It is explanatory drawing which shows the example of the data structure of the collective billing record information which the collective billing information storage part in the same embodiment memorize | stores. It is explanatory drawing which shows the example of the data structure of the collective reservation notification management information which the collective billing information storage part in the embodiment memorize | stores. It is explanatory drawing which shows the example of the data structure of the payment failure notification management information which the failure cause information storage part in the embodiment memorize | stores. It is explanatory drawing which shows the example of the data structure of the forced execution notification management information which the failure cause information storage part in the embodiment memorize | stores. In the embodiment, it is explanatory drawing which shows the example of the process which an electronic record bond information processing apparatus performs in the case of collective recording request and cancellation request. In the embodiment, it is explanatory drawing which shows the example of the process which an electronically recorded bond information processing apparatus performs in the case of the recording notification of compulsory execution, the notification of non-payment, and the notification of the arrival of the previous date. It is explanatory drawing which shows the example of the notification information list which the client apparatus in the same embodiment displays. It is explanatory drawing which shows the example of the billing information which the client apparatus in the same embodiment displays. It is explanatory drawing which shows the example of the collective billing destination date notification result detailed list which the client apparatus in the same embodiment displays. It is a flowchart which shows the example of the process sequence of the electronic record loan information processing apparatus at the time of the message reception from a client apparatus in the embodiment. It is a flowchart which shows the example of the process sequence of the electronic record loan information processing apparatus at the time of the message | telegram reception relevant to the generation | occurrence | production record request other than a creditor claim system in the same embodiment. In the same embodiment, it is a flowchart which shows the example of the process sequence when an aggregation part produces | generates aggregation information. It is a flowchart which shows the example of the process sequence of the electronic record loan information processing apparatus at the time of the message reception relevant to the generation | occurrence | production record request | requirement of a creditor claim system from the server apparatus in the embodiment.

Embodiments of the present invention will be described below with reference to the drawings.
FIG. 1 is a schematic configuration diagram showing an apparatus configuration of an electronic record bond system according to an embodiment of the present invention. In FIG. 1, the electronic record bond system 1 includes an electronic record bond information processing apparatus 10, a client apparatus 20, and a server apparatus 30. The electronically recorded bond information processing apparatus 10 includes a client communication circuit 11, a server communication circuit 12, a storage device 13, and a CPU 14.

The client device 20 is installed in a user company of the electronic record credit system 1 and transmits a recording request in accordance with an operation of a person in charge of use of the electronic record credit system 1 (hereinafter simply referred to as “user in charge”). In addition, the client device 20 receives the notification result of the recording request and displays the result.
The client device 20 is a terminal device and may have a function of receiving an operation input and transmitting it to the electronic record bond information processing apparatus 10 and a function of displaying information in accordance with an instruction from the electronic record bond information processing apparatus 10. . As the client device 20, for example, a personal computer (PC) can be used.

The server device 30 is installed in a recording organization for electronic record receivables and manages a record book of electronic record receivables. In particular, the server device 30 updates the record original book based on the recording request from the client device 20, notification of acceptance or rejection, and the like. In response to a recording request from the client device 20, the server device 30 transmits a reception result notification or a recording result notification such as success or failure of recording on the recording date when the previous date is designated as the recording date.
An example of the server device 30 is a densai net, but is not limited thereto.

The electronically recorded bond information processing apparatus 10 is installed in a relay service provider, is connected to the client apparatus 20 and the server apparatus 30, and relays the recording request process performed between the client apparatus 20 and the server apparatus 30. In particular, the electronically recorded bond information processing apparatus 10 generates aggregated information obtained by aggregating recording result notifications from the server apparatus 30 and transmits the aggregated information to the client apparatus 20.
In the example of FIG. 1, the electronically recorded bond information processing apparatus 10 is configured by a computer.

  The client communication circuit 11 communicates with the client device 20. In particular, the client communication circuit 11 receives a recording request or cancellation request (request for canceling a recording request) transmitted by the client device 20, a result notification transmitted by the server device 30, or a result from the server device 30. The aggregate information in which the electronic record bond information processing apparatus 10 aggregates the notification is transmitted to the client apparatus 20.

The server communication circuit 12 communicates with the server device 30. In particular, the server-to-server communication circuit 12 transmits (transfers) a recording request or cancellation request transmitted by the client device 20 to the server device 30. Further, the server communication circuit 12 receives various notifications transmitted by the server device 30 such as notifications transmitted by the server device 30 in response to the recording request.
The storage device 13 stores various data.
A CPU (Central Processing Unit) 14 reads out and executes a program stored in the storage device 13 to control each unit of the electronic record bond information processing apparatus 10 and perform various processes.

The communication path W11 between the client device 20 and the electronic record bond information processing apparatus 10 and the communication path W12 between the electronic record bond information processing apparatus 10 and the server apparatus 30 may be configured by a dedicated communication line. In addition, a general-purpose communication network such as the Internet or a telephone line may be used.
In addition, a plurality of client devices 20 may be connected to the electronic record bond information processing device 10.

FIG. 2 is a schematic block diagram showing a functional configuration of the electronically recorded bond information processing apparatus 10. In the figure, an electronically recorded bond information processing apparatus 10 includes a bill reception / analysis unit 111, an approval confirmation unit 112, a bill transmission unit 113, a notification reception / analysis unit 121, an aggregation unit 122, and a notification transmission unit 123. And a collective billing information storage unit 131 and a failure factor information storage unit 132.
The request reception / analysis unit 111 receives a recording request and a cancellation request transmitted by the client device 20. The claim receiving / analyzing unit 111 analyzes the received recording request or cancellation request and extracts information to be stored in the collective billing information storage unit 131. The claim reception / analysis unit 111 is configured by the CPU 14 controlling the communication circuit 11 with respect to the client.

The approval confirmation unit 112 confirms whether or not the recording request or cancellation request received by the bill reception / analysis unit 111 has been approved by the approval authority holder of the user company. If the confirmation of approval is successful, the approval confirmation unit 112 stores the information extracted by the bill reception / analysis unit 111 in the collective billing information storage unit 131. The approval confirmation unit 112 is configured by the CPU 14.
The claim sending unit 113 sends (transfers) the recording request or cancellation request received by the claim receiving / analyzing unit 111 to the server device 30. The bill transmitter 113 is configured by the CPU 14 controlling the server communication circuit 12.

The notification reception / analysis unit 121 receives various notifications transmitted by the server device 30. The notification receiving / analyzing unit 121 analyzes the received notification, extracts information to be stored in the collective billing information storage unit 131 and the failure factor information storage unit 132, and stores the information.
In particular, the notification receiving / analyzing unit 121 corresponds to an example of a cancellation processing unit, and when the recording request is canceled before the recording date, information indicating the canceled recording request is stored in the batch recording information storage unit 131. Give to billing information. More specifically, the notification reception / analysis unit 121 updates the collective billing information stored in the collective billing information storage unit 131 based on the cancellation notice transmitted by the server device 30.
The notification receiving / analyzing unit 121 is configured by the CPU 14 controlling the server communication circuit 12.

The aggregating unit 122 aggregates the notification for the recording request transmitted for each electronic recording bond from the recording organization when the recording date arrives, for each collective recording request stored by the collective billing information storage unit for each recording date. Is generated. More specifically, the aggregating unit 122 refers to information stored in the collective billing information storage unit 131 and the failure factor information storage unit 132, and generates aggregated information in which notifications from the server device 30 are aggregated.
In particular, when the individual recording request included in the collective recording request is canceled before the recording date, the aggregation unit 122 generates aggregated information reflecting information on the canceled recording request.

Further, the aggregating unit 122 includes at least one of information on an electronic record receivable whose record is not established due to inability to pay or information on an electronic record receivable whose record is not established due to forced execution among the electronic record receivables whose record is not established Generate information. The aggregation unit 122 is configured by the CPU 14.
The notification transmission unit 123 transmits various notifications received by the notification reception / analysis unit 121 and the aggregation information generated by the aggregation unit 122 to the client device 20. The notification transmission unit 123 is realized by the CPU 14 controlling the client communication circuit 11.

  The collective billing information storage unit 131 specifies a recording date of the previous date, and records a request for recording to record a record relating to the electronic record receivable in a record ledger of the electronic record receivable managed by the recording authority of the electronic record receivable, Information related to a batch recording request for a plurality of electronically recorded claims is stored. Specifically, the collective billing information storage unit 131 stores collective billing information that is information related to collective recording bills transmitted by the client device 20.

More specifically, the collective billing information storage unit 131 stores collective billing record information and collective reservation notification management information as collective billing information. The collective billing record information is information for managing collective record billing. The batch reservation notification management information is information for managing the result notification state of the reservation (record reservation on the recording date) requested by the batch recording request.
The collective billing information storage unit 131 is configured by the storage device 13.

The failure factor information storage unit 132 stores failure factor information, which is information relating to a factor that causes the recording request to be failed. Specifically, the failure factor information storage unit 132 stores non-payment notification management information and forced execution notification management information as failure factor information. The non-payment notification management information is information for managing the non-payment notification transmitted by the server device 30. The forced execution notification management information is information for managing a forced execution notification transmitted by the server device 30. As described above, the failure factor information storage unit 132 stores at least one of the information on the insolvency that has occurred and the information on the forced execution that has been performed.
The failure factor information storage unit 132 is configured by the storage device 13.

Next, information stored in the collective billing information storage unit 131 and the failure factor information storage unit 132 will be described with reference to FIGS.
FIG. 3 is an explanatory diagram showing an example of the data structure of the collective billing record information stored in the collective billing information storage unit 131. In the drawing, the collective billing record information is configured as tabular data, and one line corresponds to one collective billing request.

Each line of the batch record request information includes a key for uniquely specifying the batch record request and account information of the biller.
Specifically, each line of the batch recording billing information has a batch billing number item as a key for uniquely specifying the batch recording billing. The collective billing number is an identification number for a collective recording request.
In addition, each line of the collective recording request information includes items of a financial institution code, a branch code, an account type, and an account number of the requester's account as the account information of the requester.

FIG. 4 is an explanatory diagram showing an example of the data structure of the collective reservation notification management information stored in the collective billing information storage unit 131. In the figure, the collective reservation notification management information is configured as tabular data, and one line corresponds to one individual recording request.
Each row of the bulk reservation notification management information includes a key for uniquely identifying a record, a status, information for uniquely identifying a bulk recording request, and a bulk reservation notification status (reservation requested in bulk recording request (record reservation) Information indicating the notification state) and the previous date (recording date).

Specifically, each row of the collective reservation notification management information has items of a collective billing number, a financial institution code, and an individual billing number as a key for uniquely identifying the row (record). The individual request number is an identification number of each record request (hereinafter referred to as “individual record request”).
In addition, each line of the collective reservation notification management information includes items of a financial institution code, a recording type, and a recording number as information for uniquely specifying a charge.

The contents of the status (data value) include billing, billing error, reservation, waiting for acceptance, acceptance, cancellation, denial, establishment, non-establishment, non-registration, and deemed denial.
Further, the contents of the partial reservation notification status include uncompleted, completed, and individual notification.
In the example of FIG. 4, each row of the collective reservation notification management information further includes items of a non-payable code and a forced execution code. The non-payable code is identification information that uniquely identifies the non-payable notification transmitted by the server device 30, and is managed by non-payable notification management information. The forced execution code is identification information that uniquely specifies the forced execution notification transmitted by the server device 30 and is managed by the forced execution notification management information.

FIG. 5 is an explanatory diagram showing an example of the data structure of the payment failure notification management information stored in the failure factor information storage unit 132. In the figure, the payment failure notification management information is configured as tabular data, and one line corresponds to one payment failure notification.
Each row of the non-payment notification management information includes a non-payment code that uniquely identifies the non-payment notification and a user number of the user who is the subject of the payment notification.

FIG. 6 is an explanatory diagram illustrating an example of a data structure of forced execution notification management information stored in the failure factor information storage unit 132. In the figure, the forced execution notification management information is configured as tabular data, and one line corresponds to one forced execution notification.
Each row of the forced execution notification management information includes a non-payable code that uniquely identifies the forced execution notification and a record number of the electronic record receivable subject to forced execution.

Next, with reference to FIG. 7 and FIG. 8, the flow of processing performed by the electronically recorded bond information processing apparatus 10 will be described.
FIG. 7 is an explanatory diagram showing an example of processing performed by the electronically recorded bond information processing apparatus 10 at the time of batch recording request and cancellation request.

<Bulk recording request>
When the person in charge of the user company transmits the collective recording request from the client device 20 as a single file (collective recording request file), the bill reception / analysis unit 111 receives the collective recording request. In the example of FIG. 7, the client device 20 bills the records for the occurrence of 100 electronic record receivables collectively by designating the same recording date.

  Next, the approval confirmation unit 112 confirms whether or not the batch recording request is approved. When the approval authority holder of the user company approves the collective record request, the approval confirmation unit 112 confirms that the approval has been performed, and collects information related to the collective record request (collective charge information). 131 is stored. Specifically, the bill reception / analysis unit 111 analyzes the batch recording request and outputs the obtained information to the approval confirmation unit 112 together with the batch recording request.

Then, the approval confirmation unit 112 registers the information acquired by the bill reception / analysis unit 111 in the collective billing record information and the collective reservation notification management information stored in the collective billing information storage unit 131. At the time of registration in the collective reservation notification management information, the approval confirmation unit 112 sets the status to billing and sets the collective reservation notification state to not yet set.
Further, the approval confirmation unit 112 outputs the batch recording request to the billing transmission unit 113, and the billing transmission unit 113 transmits (transfers) the batch recording request file to the server device 30.

<Notification of acceptance results>
When the server apparatus 30 transmits a reception result notification for each individual recording request included in the batch recording request in one notification and one file, the notification reception / analysis unit 121 receives the reception result notification.
The notification receiving / analyzing unit 121 specifies an individual recording request corresponding to the reception result notification based on the financial institution code, the recording type, and the recording number included in the received reception result notification. Then, the notification receiving / analyzing unit 121 updates the status of the row corresponding to the specified individual recording request among the rows of the collective reservation notification management information to “Waiting for approval / disapproval” or “Billing error”.

Specifically, when the method of requesting individual records corresponding to the notification of acceptance results is a creditor billing method, it is updated to wait for approval / disapproval. If an error notification is received, it is updated to a billing error. Otherwise, update during booking.
Further, the aggregating unit 122 refers to the collective billing information storage unit 131 and generates aggregated information that aggregates all the reception result notifications corresponding to the collective recording billing. Then, the notification transmission unit 123 transmits the aggregation information generated by the aggregation unit 122 to the client device 20 by one result notification (that is, one file).
The electronically recorded bond information processing apparatus 10 performs each process for the notification from the server apparatus 30.

<Request for cancellation>
If the person in charge of use wants to cancel the individual recording request before the recording date designated by the previous date, the client device 20 transmits a cancellation request. When the request reception / analysis unit 111 receives the cancellation request, the approval confirmation unit 112 checks whether the cancellation request is approved. Upon confirming that the approval has been made, the approval confirmation unit 112 outputs the cancellation request to the claim transmission unit 113, and the request transmission unit 113 transmits (transfers) the cancellation request to the server device 30.

<Notification of cancellation request result>
When the server apparatus 30 transmits a result notification for the cancellation request (hereinafter referred to as “cancellation request result notification”), the notification reception / analysis unit 121 receives the cancellation request result notification.
The notification reception / analysis unit 121 identifies an individual recording request corresponding to the cancellation request result notification based on the financial institution code, the recording type, and the recording number included in the received cancellation request result notification. Then, the notification reception / analysis unit 121 updates the status of the row corresponding to the specified individual recording request among the rows of the collective reservation notification management information to cancel.

In addition, the notification receiving / analyzing unit 121 cancels or updates the batch reservation notification state of the corresponding row of the batch reservation notification management information to the individual notification. Specifically, when the method of requesting individual records corresponding to the notification of cancellation request result notification is a request for recording of the creditor request method and received after the recording date, it is updated to individual notification. Otherwise, update to Cancel. Both the individual notification and the cancellation are excluded from aggregation of the result notification (hereinafter referred to as “advance date arrival notification”) when the previous date (recording date) arrives.
Further, the notification transmission unit 123 transmits a cancellation request result notification to the client device 20.

When a notification of acceptance for the occurrence record request of the creditor claim method is received from the server device 30, the notification reception / analysis unit 121 includes the financial institution code, the record type, and the record number included in the received occurrence record notification. To identify the individual record request that corresponds to the notification of consent. Then, the notification reception / analysis unit 121 updates the status of the row corresponding to the specified individual recording request among the rows of the batch reservation notification management information to approval.
When the notification of acceptance is received after the recording date, the notification reception / analysis unit 121 updates the collective reservation notification state of the corresponding row of the collective reservation notification management information to the individual notification.

In addition, when a notice of denial of the credit record request generation record request is received from the server device 30, the notification reception / analysis unit 121 includes the financial institution code, the record type, and the record number included in the received record notification Based on the above, the individual record request corresponding to the rejection notice is specified. Then, the notification reception / analysis unit 121 updates the status of the row corresponding to the specified individual recording request among the rows of the collective reservation notification management information to be denied.
In addition, when a denial notification is received after the recording date, the notification receiving / analyzing unit 121 updates the batch reservation notification state of the corresponding row of the batch reservation notification management information to the individual notification.

FIG. 8 is an explanatory diagram illustrating an example of processing performed by the electronically recorded bond information processing apparatus 10 in the case of a forced execution record notification, a payment failure notification, and a future date arrival notification.
<Record notification of forced execution>
When the forced execution is performed and the server device 30 transmits the forced execution record notification, the notification reception / analysis unit 121 receives the forced execution record notification.

The notification reception / analysis unit 121 reads the record number from the received forced execution record notification and registers it in the forced execution notification management information.
Further, the notification reception / analysis unit 121 searches the read recording number in the collective reservation notification management information. When the record number is found, the forced execution code of the corresponding row is registered in the forced execution code of the corresponding row in the batch reservation notification management information.

<Notice of insolvency>
When payment failure occurs and the server device 30 transmits a payment failure notification, the notification reception / analysis unit 121 receives the payment failure notification.
The notification receiving / analyzing unit 121 reads the user number from the received payment failure notification and registers it in the payment failure management information.
Further, the notification receiving / analyzing unit 121 acquires the account number of the corresponding user from the read user number, and searches for the account number in the collective reservation notification management information. When the account number is found, the non-payable code of the corresponding line of the non-payment notification management information is registered in the non-payable code of the corresponding line of the collective reservation notification management information.

<Notice of future arrival>
When the recording date specified by the previous date arrives and the server device 30 transmits the previous date arrival notification in one notification 1 file, the notification reception / analysis unit 121 receives the previous date arrival notification.
The notification reception / analysis unit 121 specifies an individual recording request corresponding to the notification of the arrival of the future date based on the financial institution code, the recording type, and the recording number included in the received notification of the arrival of the previous date. Then, the notification receiving / analyzing unit 121 sets the status of the row corresponding to the specified individual recording request among the rows of the batch reservation notification management information to be established, not established, or not registered according to the content of the notification of the arrival of the previous date. Update to Note that the notification receiving / analyzing unit 121 updates the status to unregistered in the case of denial of a creditor billing method occurrence record request.

Then, the aggregating unit 122 includes records for which the collective reservation notification status of the collective reservation notification management information is not yet recorded (line in FIG. 4), and the status is any of billing / reserved / accepted / denied. If there is not, an aggregate notification in which the notification of arrival of the previous date is aggregated is generated and output to the notification transmission unit 123. The notification transmission unit 123 transmits the aggregation notification to the client device 20.
The aggregating unit 122 determines whether all the previous date arrival notifications have been obtained based on the status of the collective reservation notification management information. Specifically, if there is no status being reserved in the corresponding row of the collective reservation notification management information, it is determined that all previous date arrival notifications have been obtained.

For example, the aggregation unit 122 calculates the number of notifications and the total amount as the aggregation information of the notification of the arrival of the previous date for each of established and not established.
It should be noted that notification of failure or cancellation before the arrival of the previous date is made individually, and the aggregation unit 122 is excluded from aggregation. When all the individual recording requests corresponding to the scheduled date are not established or canceled, the aggregation unit 122 does not generate an aggregation notification.

In the case where the batch recording request method is other than the creditor billing generation request, the aggregating unit 122 extracts the row whose scheduled date corresponds to the processing date from the batch reservation notification management information. Then, the aggregating unit 122 sets, as an aggregation target, a row in which the status is established or not established among the extracted rows.
In the example of FIG. 8, the aggregation unit 122 refers to the status of 100 cases (100 lines) whose scheduled date is the processing execution date in the collective reservation notification management information, and 91 successful, 8 unsuccessful, and cancelled. Extract one item.

Further, the aggregation unit 122 refers to the items of the forced execution code and the non-payable code for the 8 cases that are not established, and acquires the code if the code is registered.
In the case of the example in FIG. 8, the aggregation unit 122 includes 91 cases of establishment, 8 cases of failure (4 cases of forced execution, 4 cases of non-payment notification), and 1 case of non-consolidation. Aggregation and aggregate information including the aggregation results are generated as an aggregation notification. The electronically recorded bond information processing apparatus 10 presents the aggregation result to the user company by the aggregation notification.

Further, when the collective record request method is a creditor billing generation record request, the aggregating unit 122 extracts a row whose scheduled date corresponds to the processing execution date from the collective reservation notification management information. Then, the aggregating unit 122 sets, as an aggregation target, a row in which the status is established, not established, or not registered among the extracted rows.
For example, the aggregation unit 122 refers to a combination of (status, batch reservation notification state) for 100 cases whose scheduled date is the processing execution date in the batch reservation notification management information, and 80 (established, not yet), (Non-registered, not yet) 10 cases, (Not established, not yet) 4 cases, (Cancelled, canceled) 3 cases, (Established, individual notification) 2 cases, (Waiting for approval / disapproval, Not yet) 1 case is extracted.

Further, the aggregation unit 122 refers to the items of the forced execution code and the non-payable code for the four cases that are not established, and acquires the code if the code is registered.
For example, the aggregation unit 122 includes 80 cases of establishment, 14 cases of failure, 10 cases of failure, 2 cases of forced execution, 2 cases of non-payment notification, and 6 cases that are not subject to aggregation. Aggregation and aggregate information including the aggregation results are generated as an aggregation notification. The electronically recorded bond information processing apparatus 10 presents the aggregation result to the user company by the aggregation notification.

  Here, the aggregating unit 122 aggregates individual recording requests whose status is unregistered as failure due to denial. Further, the aggregation unit 122 counts the individual record requests whose status is not established as being unsatisfied due to forced execution or non-payment notification depending on the registration status of the forced execution code or non-payable code. The aggregation unit 122 also cancels the individual recording request whose status is canceled, the individual recording request whose status is established and the batch reservation notification state is the individual notification, and the individual recording request whose status is waiting for approval / disapproval and whose batch reservation notification state is not yet received. Are counted as non-aggregation targets. An individual record request whose status is waiting for acceptance or rejection and whose collective reservation notification state is not yet is an individual record request that has not been accepted or denied on the recording date.

  Note that, in order to deal with a case where aggregated information can be generated by a cancellation notification, the aggregation unit 122 determines whether or not aggregated information can be generated even when the notification reception / analysis unit 121 receives a cancellation notification. . Also, when a cancellation notice is received on the recording date, the notice receiving / analyzing unit 121 updates the status of the collective reservation notice management information.

Here, for comparison, the processing of the electronically recorded bond information processing apparatus 10 in the case of not consolidating notifications of arrival of future dates will be described. In this case, the collective billing information storage unit 131 does not need to store the collective reservation notification management information, and the notification reception / analysis unit 121 does not need to update the status of the collective reservation notification management information and the collective reservation notification state.
That is, the aggregating unit 122 can aggregate the notification of the arrival of the previous date by referring to the collective reservation notification management information.

Next, a display example of aggregate information will be described with reference to FIGS. 9 and 10.
FIG. 9 is an explanatory diagram illustrating an example of a notification information list displayed by the client device 20. The client device 20 displays a list of notifications received from the electronic record bond information processing device 10 as a notification information list.
In the example shown in the figure, the client device 20 displays a list of notification information in a table format, and one line corresponds to one notification.

  A line L11 indicates information of the aggregation notification in which the electronic record bond information processing apparatus 10 aggregates the arrival notification of the previous date. As described above, the electronic record bond information processing apparatus 10 aggregates the notifications of the arrival of the future dates, so that the client device 20 can display the notifications corresponding to the notifications of the arrival of the future dates in one line. As a result, the number of notifications displayed on the notification information list by the client device 20 can be reduced, and the risk that the person in charge of referring to the notification information list misses the notification can be reduced.

  The “details” button displayed in each row is an operation button for causing the client device 20 to display more detailed information about the notification information displayed in the corresponding row. For example, when the selection operation (mouse click or touch operation) of the button B11 is received, the client device 20 displays more detailed information about the aggregation notification displayed in the row L11. Specifically, the client device 20 displays billing information described with reference to FIG. 10 and a collective billing date notification result detailed list described with reference to FIG.

  FIG. 10 is an explanatory diagram illustrating an example of billing information displayed by the client device 20. The client device 20 displays the aggregation result of the electronically recorded bond information processing device 10 (aggregation unit 122) with the billing information. In particular, the client device 20 determines the number of records and the total amount for each type of record request for which the record has been established and record request for which the record has not been established, for each type such as a record request for a debtor claim method or a record request for a creditor claim method. Is displayed. Furthermore, the client device 20 displays the total number of record requests that are not subject to aggregation, such as a record request canceled before the due date, as the number of non-target cases.

  By referring to the billing information, the person in charge of use can grasp the result of the batch recording request quickly and without omission. For example, the person in charge of use can refer to the number of non-target cases to confirm whether or not there is a non-targeted recording request out of expectation among the recording requests requested for batch recording. By grasping the record request that is not subject to the prediction, the person in charge of use can investigate the cause of the exclusion and take measures.

FIG. 11 is an explanatory diagram illustrating an example of a list of billing date notification result details displayed by the client device 20. The client device 20 displays a list of notification results of individual recording requests as a list of detailed billing date notification result details.
In the example shown in the figure, the client apparatus 20 displays a list of billing date notification result details in a table format, and one line corresponds to one notification. More specifically, one line shows an outline of one previous date arrival notification.

  The person in charge of use can refer to the collective billing date notification result detailed list to specifically grasp the individual record request that has been established and the individual record request that has not been established. By performing a selection operation of a “details” button (for example, button B21) displayed in the list of detailed billing date notification results, the user in charge grasps the information of the corresponding future date arrival notification in more detail. be able to.

Next, the operation of the electronically recorded bond information processing apparatus 10 will be described with reference to FIGS.
FIG. 12 is a flowchart illustrating an example of a processing procedure of the electronically recorded bond information processing apparatus 10 when a message (record request) is received from the client apparatus 20.
When the bill reception / analysis unit 111 receives a message from the client device 20 (step S101), the bill reception / analysis unit 111 analyzes the message and extracts information to be stored in the collective billing information storage unit 131 (step S101). S102).

Next, after confirming that the message has been approved (step S103), the approval confirmation unit 112 stores the information extracted by the claim reception / analysis unit 111 in step S102 in the collective billing information storage unit 131 ( Step S104). Specifically, the approval confirmation unit 112 registers or updates the information extracted by the bill reception / analysis unit 111 in the collective billing record information and the collective reservation notification management information stored in the collective billing information storage unit 131.
The claim transmitter 113 transmits (transfers) the message from the client device 20 to the server device 30 (step S105).
Thereafter, the process of FIG.

FIG. 13 is a flowchart illustrating an example of a processing procedure of the electronically-recorded bond information processing apparatus 10 when receiving a message (notification) related to an occurrence record request other than the creditor claim method from the server apparatus 30.
In the process of FIG. 5, first, the notification receiving / analyzing unit 121 receives a notification message from the client device 20 (step S201). The notifications received by the notification receiving / analyzing unit 121 in step S201 include a reception result notification, a cancellation request result notification, a forced execution recording notification, a non-payable notification, and a future date notification.

Next, the notification reception / analysis unit 121 updates the collective billing information and the collective reservation notice management information stored in the collective billing information storage unit 131 based on the contents of the message (step S202).
Further, the notification reception / analysis unit 121 determines the type of the notification (step S211). In both cases of determining that the notification is a reception result notification (step S211: reception result notification) and determining that the notification is a cancellation request result notification (step S211: cancellation request result notification), the processing in FIG. finish.

  On the other hand, when it is determined in step S211 that the type of notification is a record notification of forced execution (step S211: notification of forced execution) and when it is determined that the notification is non-payable (step S211: non-payment notification). In any case, the notification reception / analysis unit 121 updates the failure factor information stored in the failure factor information storage unit 132 based on the contents of the message (step S241). After step S241, the process in FIG.

  On the other hand, when it is determined in step S211 that the type of notification is the notification of arrival of the previous date (step S211: notification of arrival of the previous date), the aggregating unit 122 determines whether it is possible to aggregate the notification of arrival of the previous date (step S211). S221). Specifically, the aggregating unit 122 determines that aggregation is possible when the status of the recording request for each piece of corresponding batch reservation notification recording information is either established or not established.

If it is determined that aggregation is possible (step S221: YES), the aggregation unit 122 generates aggregation information (step S231).
Then, the notification transmission unit 123 transmits the aggregate information and the notification to the client device 20 (Step S232).
After step S232, the process of FIG.
On the other hand, if it is determined in step S221 that aggregation is not possible (step S221: NO), the processing in FIG.
Note that FIG. 13 is a diagram for explaining the processing for particularly collecting the notification of the arrival of the previous date, and the detailed description of the processing for other notification messages is omitted. The electronically recorded bond information processing apparatus 10 performs processes other than those illustrated in accordance with the type of notification message.

FIG. 14 is a flowchart illustrating an example of a processing procedure when the aggregation unit 122 generates aggregate information. The aggregation unit 122 performs the process of FIG. 14 in step S221 of FIG.
The aggregation unit 122 first determines, from the collective reservation notification management information stored in the collective billing information storage unit 131, the individual record request on the processing day of the processing date among the individual record requests included in the collective record request to be aggregated. All the information corresponding to is extracted (step S301).

  Next, the aggregation unit 122 adds up the number of cases and the amount of money for the information extracted in step S301 (step S302). Specifically, the aggregating unit 122 counts the number of records for each type, such as a record request for a debtor billing method and a record request for a creditor billing method, for each of a record request for which a record is established and a record request for which a record is not established. And total amount. Furthermore, the aggregating unit 122 aggregates the number of record requests that are not subject to aggregation, such as a record request canceled before the due date, as the number of non-target cases.

Next, the aggregation unit 122 reflects the failure factor information stored in the failure factor information storage unit 132 in the aggregation information (step S303).
Specifically, the aggregation unit 122 refers to the forced execution code and non-payable code items of the collective reservation notification management information with respect to the individual registration request that has not been established, and is applicable when the code is registered. Aggregate the reasons for failure (caused by forced execution or nonpayment notification).
After step S303, the process of FIG.

FIG. 15 is a flowchart illustrating an example of a processing procedure of the electronically-recorded bond information processing apparatus 10 when a message (notification) is received from the server apparatus 30 relating to a creditor billing generation record request.
In the process of FIG. 9, first, the notification receiving / analyzing unit 121 receives a notification message from the client device 20 (step S401). As notifications received by the notification reception / analysis unit 121 in step S401, in addition to the acceptance result notification, the cancellation request result notification, the forced execution record notification, the non-payment notification, and the future date arrival notification, an acceptance notification and a denial notification There is.

Step S402 is the same as step S202 of FIG.
Further, the notification receiving / analyzing unit 121 determines the type of the notification (step S411). When it is determined that it is a notification of acceptance (step S411: notification of acceptance), when it is determined that it is a notification of rejection (step S411: Notification of rejection), and when it is determined that it is a notification of acceptance result (step S411) : The reception result notification) and the case where it is determined that the request is a cancellation request result notification (step S411: cancellation request result notification), the process of FIG.

On the other hand, when it is determined in step S411 that the notification type is a forced execution record notification (step S411: forced execution record notification), and when the notification type is determined to be non-payable notification (step S411: step S411). In either case, the process proceeds to step S441.
Step S441 is the same as step S241 in FIG. After step S441, the processing in FIG.

  On the other hand, if it is determined in step S411 that the type of notification is the notification of the arrival of the previous date (step S411: notification of the arrival of the previous date), the aggregating unit 122 determines whether the notification of the arrival of the previous date can be aggregated (step S411). S421). Specifically, the aggregating unit 122 determines that the aggregation is possible when the status of the request for recording of the corresponding batch reservation notification record information is either established / not established / not registered.

If it is determined that aggregation is possible (step S421: YES), the process proceeds to step S431. Steps S431 to S432 are the same as steps S231 to S232 in FIG.
After step S432, the process of FIG.
On the other hand, if it is determined in step S421 that aggregation is not possible (step S421: NO), the processing in FIG.
Note that FIG. 15 is a diagram for explaining the processing for collecting the notifications for arrival of the future date in particular, and a detailed description of the processing for other notification messages is omitted. The electronically recorded bond information processing apparatus 10 performs processes other than those illustrated in accordance with the type of notification message.

As described above, the aggregating unit 122 generates aggregated information obtained by aggregating the previous date arrival notification for each recording date and for each batch recording request.
Thereby, the electronically recorded bond information processing apparatus 10 can make it easier for a user (for example, a person in charge of use) to grasp the result of the batch recording request.
For example, the person in charge of use can grasp the result of the batch recording request quickly and without omission by referring to the billing information described with reference to FIG. Further, for example, the person in charge of use can refer to the number of non-target cases, and can confirm whether or not there is a non-targeted recording request out of expectations among the recording requests requested for batch recording. By grasping the record request that is not subject to the prediction, the person in charge of use can investigate the cause of the exclusion and take measures.

Further, when the recording request is canceled before the recording date, the notification receiving / analyzing unit 121 adds information indicating the canceled recording request to the collective billing information stored in the collective billing information storage unit 131. Then, the aggregating unit 122 generates aggregated information that reflects information related to the canceled recording request.
Thereby, the aggregating unit 122 can distinguish between the canceled recording request and the unsatisfied recording request, and can generate more accurate aggregated information.

Further, the failure factor information storage unit 132 stores at least one of information on the insolvency that has occurred and information on the forced execution that has been performed. Then, the aggregating unit 122 includes at least one of information on the electronic record receivable whose record is not established due to inability to pay among the electronic record receivable whose record is not established, or information on the electronic record claim whose record is not established due to forced execution Generate information.
In this way, the aggregation unit 122 can generate more detailed aggregation information indicating the cause of record failure.

In addition, a program for realizing all or part of the functions of the electronic record bond information processing apparatus 10 is recorded on a computer-readable recording medium, and the program recorded on the recording medium is read by a computer system. The processing of each unit may be performed by executing. Here, the “computer system” includes an OS and hardware such as peripheral devices.
Further, the “computer system” includes a homepage providing environment (or display environment) if a WWW system is used.
The “computer-readable recording medium” refers to a portable medium such as a flexible disk, a magneto-optical disk, and a compact disk, and a storage device such as a hard disk built in the computer system. Furthermore, the “computer-readable recording medium” dynamically holds a program for a short time like a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line. In this case, a volatile memory in a computer system serving as a server or a client in that case, and a program that holds a program for a certain period of time are also included. The program may be a program for realizing a part of the functions described above, and may be a program capable of realizing the functions described above in combination with a program already recorded in a computer system.

  The embodiment of the present invention has been described in detail with reference to the drawings. However, the specific configuration is not limited to this embodiment, and includes design changes and the like within a scope not departing from the gist of the present invention.

DESCRIPTION OF SYMBOLS 10 Electronic record loan information processing apparatus 111 Claim reception / analysis part 112 Approval confirmation part 113 Request transmission part 121 Notification reception / analysis part 122 Aggregation part 123 Notification transmission part 131 Collective bill information storage part 132 Failure factor information storage part

Claims (5)

Record requests for electronic record receivables are recorded for multiple electronic record receivables by specifying a record date of the previous date and requesting that records relating to electronic record receivables be recorded in the record ledgers of electronic record receivables managed by the recording authority of electronic record receivables A collective billing information storage unit for storing information related to collective record billing;
An aggregation unit that generates aggregated information that is aggregated for each batch recording request stored in the collective billing information storage unit, for each recording date, with respect to a recording request transmitted from the recording organization for each electronically recorded bond when the recording date arrives When,
An electronic record loan information processing apparatus comprising: When the recording request is canceled before the recording date, the information processing unit includes a cancellation processing unit that gives information indicating the canceled recording request to information related to the collective recording request stored in the collective billing information storage unit,
The aggregation unit generates the aggregate information reflecting the canceled recording request;
The electronically recorded bond information processing apparatus according to claim 1. A failure factor information storage unit that stores at least one of information on insolvency that has occurred or information on forced execution that has been performed;
The aggregation unit includes the aggregated information including at least one of information on an unrecorded electronic record receivable due to inability to pay, or information on an unrecorded unrecordable electronic record receivable due to inability to pay among the unrecorded electronic record receivables Generate
The electronic record loan information processing apparatus according to claim 1 or 2, Record requests for electronic record receivables are recorded for multiple electronic record receivables by specifying a record date of the previous date and requesting that records relating to electronic record receivables be recorded in the record ledgers of electronic record receivables managed by the recording authority of electronic record receivables An electronic record receivable information processing method for an electronic record receivable information processing apparatus comprising a collective bill information storage unit for storing information related to a collective record request,
Recording date is transmitted from the recording engine and arriving at each electronic record claims, a notification to the recording claims, aggregation recorded daily and the billing information storage unit generates aggregated information obtained by aggregating each batch recording claims for storing An electronically recorded bond information processing method comprising steps. Record requests for electronic record receivables are recorded for multiple electronic record receivables by specifying a record date of the previous date and requesting that records relating to electronic record receivables be recorded in the record ledgers of electronic record receivables managed by the recording authority of electronic record receivables In a computer that controls an electronically recorded claim information processing apparatus including a collective billing information storage unit that stores information related to collective record billing,
Aggregation step of generating aggregated information that is aggregated for each recording date stored in the collective billing information storage unit, and for each recording date, the notification for the recording request transmitted from the recording institution for each electronically recorded bond when the recording date comes A program for running

Images