JP5579249B2 - System and method for lump-sum application of transfer and electronically recorded receivables using a dedicated account for transfer - Google Patents

Description

  The present invention relates to a system and method for batch transfer of a transfer and an electronically recorded bond using a dedicated account for transfer. More specifically, for a bill sent by a creditor (billing data), regardless of whether the debtor uses a transfer-only account or an electronically recorded receivable, a single system is used. Further, the present invention relates to a system and method that can smoothly perform the billing data erase operation.

  2. Description of the Related Art Conventionally, with regard to payment verification work such as accounts receivable, a system for preparing a separate account number for a dedicated bank account for each billing destination and making payment verification work more efficient is known (see Patent Document 1). According to this system, when a debtor (transferr) makes a transfer to a dedicated deposit account assigned to himself / herself, the creditor confirms the payment details with the account number, and The erase operation can be performed more easily.

  In addition, in recent years, it is known that an electronic record receivable system has been established, and an electronic receivable record institution (commonly known as Densai Net (registered trademark)) was established by the National Bank Association (JBA). “Densai Net” will provide a new settlement infrastructure that records and distributes electronically-recorded receivables, which financial institutions participate in. More specifically, “Densai Net” records the occurrence record, transfer record, payment, etc. of electronic record receivables (also referred to as “Densai”) in the record base.

  Electronically recorded receivables are generated when the obligor identifies the creditor and requests the “Densai Net” through the transaction financial institution to record the occurrence, and then the prescribed payment indicated in the electronically recorded receivable When the due date arrives, inter-bank remittance settlement from the debtor account to the creditor account is automatically performed without requesting a transfer procedure as in the past, and payment records in the record ledger are also automatically recorded. It is known (see Non-Patent Document 1). It is known that the clearing operation for the electronic record receivable is performed by the record number added to the electronic record receivable. It is known that even if the electronic record receivable is divided and transferred, the divided electronic record receivable (child) is indicated by the record number of the parent electronic record receivable and can be linked.

Patent No. 3029421

The Bank of Japan National Bank Association Electronic Credit Recorder Establishment Preparatory Office, “Practical Q & A on Electronic Record Credits-Illustrated by Zenginkyo Electronic Credit Recorder“ Densai Net ””

  However, companies (creditors) who collect funds by both means of transfer using a dedicated account for transfer and electronically recorded receivables need to use the two types of application systems described above separately. was there. For this reason, even if the creditor company assigns the same account number for bank transfer to the debtor in both cases of deposits and electronically recorded receivables, it handles any receivable as long as it does not refer to each system. I was unable to determine whether the payment was made.

  The present invention has been made in view of such a problem, and an object of the present invention is to provide a system and method capable of performing a transfer using a bank account dedicated for transfer and a collective cancellation of an electronically recorded bond.

In order to solve the above problems, a system according to the present invention is a system for confirming payment for a claim, wherein the system uses a dedicated account for transfer to make a payment for the claim by a debtor. This is a single system that can confirm the payment for the billing regardless of the selected transfer or payment by electronically recorded receivable, receives billing data from the creditor server, and generates bond management data The claim management data is stored in a management database and includes at least a debtor identifier, a due date for payment, a billing amount, and a dedicated account for transfer assigned to the debtor, and an electronic claim Receives the generated record data transmitted from the recording organization and associates it with the generated record data through the identification number of the account for exclusive use of transfer The right management data is read from the management database, and the means for updating the receivable management data by adding the information of the face value and the record number of the electronically recorded receivable to the read receivable management data and transmitted from the bank system Receiving deposit / withdrawal data, and reading and reading the claim management data associated with the deposit / withdrawal data through at least one of the identification number of the bank account dedicated for transfer and the record number of the electronically recorded claim Means for adding settlement date and settlement amount information to the receivable management data and updating the receivable management data; reading the receivable management data; and the billing amount and the settlement amount included in the receivable management data Judgment is made on whether or not they match, and when the predetermined condition is satisfied, data indicating completion of application confirmation is included in the bond management data. Pressurized to is characterized in that a means for updating the credit management data.

Further, the method according to the present invention is a method executed by a system for confirming payment for a claim, wherein the system uses a bank account dedicated for transfer in order for a debtor to make a payment for the claim. And a single system capable of confirming payment for the claim regardless of whether payment is made by electronically recorded receivables, wherein the method receives claim data from a creditor server, The bond management data is stored in a management database, and includes at least a debtor identifier, a due date for payment, a billing amount, and a transfer-dedicated account assigned to the debtor; Receives the occurrence record data transmitted from the electronic bond recording institution and relates to the occurrence record data via the identification number of the account dedicated for transfer. A receivable management data to be attached is read from the management database, and the receivable management data is added to the read receivable management data with information on the face value and record number of the electronically recorded receivable, and the receivable management data is transmitted from the bank system Receiving the received deposit / withdrawal data, and reading out the claim management data associated with the deposit / withdrawal data through at least one of the identification number of the bank account dedicated for transfer and the record number of the electronically recorded claim from the management database, Updating the claim management data by adding settlement date and settlement amount information to the read claim management data; and reading the claim management data to read the claim amount and the settlement included in the claim management data It is determined whether the amounts match, and if the specified conditions are met, In addition to the serial loan management data, characterized in that it comprises the step of updating the credit management data.

  In the case where both the transfer and the collection of electronic receivables are performed, the present invention performs a collective application for the collection of receivables by transfer and the collection of receivables by electronically recorded receivables in a single system. Can be obtained.

It is a figure which shows the outline | summary of the whole system containing the extinguishing system which concerns on this invention. It is a system block diagram of the eraser system which concerns on this invention. It is a figure which shows an example of the claim data transmitted to a cancellation system. It is a figure which shows an example of the generation | occurrence | production record data transmitted to a deletion system. It is a figure which shows an example of payment etc. recording data transmitted to a cancellation system. It is a figure which shows an example of the deposit / withdrawal data transmitted to an application system. It is a figure which shows an example of the credit management data stored in management DB. It is a flowchart explaining the data processing (A)-(D) performed in the elimination system which concerns on this invention.

  Hereinafter, embodiments of the present invention will be described in detail. In the following description, the embodiment will be described in which the deposit from the debtor is made to the account dedicated to the transfer, but the application system according to the present invention is limited to the account dedicated to the transfer as a use account. No, you may use a general account.

  FIG. 1 is a diagram showing an outline of a system including an erasing system 100 according to the present invention. The application system 100 is connected to the creditor's own system 110, the relay system 115, and the EB system 120 so as to be able to communicate with each other.

  The company system 110 generates billing data 130 to be sent to the debtor, and transmits the generated billing data 130 to the consumption system 100. In addition, before transmission, it is natural that the in-house system 110 must be authenticated by a well-known authentication unit so that the revocation system 100 can be accessed. The billing data 130 may be transmitted to a system on the debtor side, but a bill form may be sent by means such as mail, and is not particularly limited.

  The relay system 115 is connected so as to be able to communicate with the Densai net 125, receives data such as the electronic record bond occurrence record data 135 and the payment record data 140 from the Densai net 125, and the occurrence record. The data 135 and the record data 140 such as payment are transmitted to the application system 100. The relay system 115 is a system owned by all financial institutions connected to the Densai net 125.

  The EB system 120 is a system coupled so as to be communicable with an accounting system, and is a host computer for EB (electronic banking) such as online banking and Internet banking used by financial institutions. The EB system 120 transmits the deposit / withdrawal data 145 generated when the account is deposited to the application system 100.

  The revocation system 100 performs predetermined processing on the billing data 130 received from the company system 110 and stores it in the management DB 105. Further, the revocation system 100 updates the data stored in the management DB 105 using the generated record data 135 and the payment record data 140 received from the relay system 115. Further, the application system 100 updates the data stored in the management DB 105 using the deposit / withdrawal data 145 received from the EB system 120. These data processing performed in the erasing system 100 will be described in detail below.

  FIG. 2 is a system configuration diagram of the extinguishing system 100 according to the present invention. The deletion system 100 includes a control unit 201, a main storage unit 202, an auxiliary storage unit 203, an interface (I / F) unit 204, an output unit 205, and a management DB 105. These components 105 and 201 to 205 are connected to each other via a bus 210, and the components 105 and 202 to 205 are collectively controlled by the control unit 201.

  The control unit 201 is also called a central processing unit (CPU), controls the components 105 and 202 to 205 and calculates data as described above, and executes various programs stored in the auxiliary storage unit 203. Read to the main storage unit 202 and execute. The main storage unit 202 is also called a main memory, and stores various received data, computer-executable instructions, data after arithmetic processing by the instructions, and the like.

  The auxiliary storage unit 203 is a storage device typified by a hard disk (HDD) and is used when data and programs are stored for a long period of time. Since the main storage unit 202 has a relatively smaller storage capacity than the auxiliary storage unit 203, it is used for temporary data storage, arithmetic processing, and the like, whereas the auxiliary storage unit 203 uses necessary data and information. Used for long-term storage and storage. That is, when the control unit 201 executes a program to perform data calculation, the necessary data and program are read from the auxiliary storage unit 203 to the main storage unit 202, and calculation result data is stored and stored for a long time. In this case, the control unit 201 writes the calculation result data in the auxiliary storage unit 203.

  An interface (I / F) unit 204 plays a role of an interface when data is transmitted / received to / from another client device or server device. Data received from the outside is temporarily stored in the main storage unit 202. The interface unit 204 also provides an interface (application program such as an input screen) for receiving various commands and input data (such as various masters and tables) from the system operator. The output unit 205 displays the processed data on a display screen or prints the processed data on a sheet.

  Before describing the data processing performed in the application system 100, various data used in the data processing, that is, billing data 130, generation record data 135, payment record data 140, and deposit / withdrawal data 145 are described. Will be described.

  FIG. 3 is a diagram illustrating an example of billing data 130 transmitted from the company system 110 to the revocation system 100. The billing data 130 includes at least a billing destination 301, a payment due date 302, a billing amount 303, and a transfer destination 304. The billing destination 301 is information for identifying the debtor, and may be an identification code or a name. The payment due date 302 and the invoiced amount 303 indicate the due date and the invoiced amount when payment is made from the debtor to the creditor. The transfer destination 304 is an individual account dedicated to transfer assigned by the creditor to each debtor. As shown in Patent Document 1, when payment is made to the account shown in the transfer destination 304, the transfer is made to the creditor's actual account. As another embodiment, the transfer destination 304 can be a general account instead of a transfer-dedicated account.

  FIG. 4 is a diagram illustrating an example of the generated record data 135 transmitted from the relay system 115 to the revocation system 100. The occurrence record data 135 includes at least obligor information 401, creditor information 402, face value 403, payment date 404, and record number 405. The obligor information 401 and the creditor information 402 include name and settlement account information, respectively. The face value 403 and the due date 404 indicate the face value of the electronically recorded receivable and the due date for repaying the debt, respectively. The record number 405 is an identification number of the electronic record bond.

  FIG. 5 is a diagram illustrating an example of payment record data 140 transmitted from the relay system 115 to the application system 100. The payment record data 140 includes at least creditor information 501, a payment amount 502, a payment date 503, and a record number 504. The creditor information 501 includes name and settlement account information. The payment amount 502 and the payment date 503 indicate the actual payment amount and payment date. The record number 504 is an identification number of the electronic record bond. The payment record data 140 may include debtor information including name and settlement account information.

  FIG. 6 is a diagram illustrating an example of deposit / withdrawal data 145 transmitted from the EB system 120 to the application system 100. The deposit / withdrawal data 145 includes a header record 601, a data record 602, a trailer record 603, and an end record 604. The header record 601 includes withdrawal account information, for example, information on a settlement account of the debtor. The data record 602 includes the date of deposit made for the creditor's account, transaction amount, deposit account information (account number, etc.), and EDI information (eg, record number of electronically recorded receivable). The trailer record 603 indicates the total number and total amount of the data records 602, and the end record 604 indicates the total number of records.

  FIG. 7 is a diagram illustrating an example of bond management data 700 stored in the management DB 105. The claim management data 700 includes a billing destination 701, a payment due date 702, a billing amount 703, a transfer destination 704, a face amount 705, a settlement date 706, a settlement amount 707, and a record number 708. The billing address 701 is information for identifying the debtor, and may be an identification code or a name. The payment due date 702 and the billing amount 703 indicate the (planned) due date and the billing amount at which payment is made from the debtor to the creditor. The transfer destination 704 is an individual account dedicated for transfer assigned by the creditor to each debtor, and indicates a settlement account of the creditor. The face value 705 indicates the face value of the electronically recorded receivable. The settlement date 706 and the settlement amount 707 indicate the date and amount when the creditor's account was actually deposited. The record number 708 indicates the record number of the electronic record bond.

  Further, as shown in FIG. 7, the bond management data 700 includes a confirmation flag 709 and an application flag 710. The confirmation flag 709 is an item that is flagged when the corresponding data in the bond management data 700 selects an electronically recorded bond as a settlement means. Further, the consumption flag 710 is an item in which a flag is set for data that has finally been confirmed for consumption. The flag value may be any value and is not particularly limited.

  FIG. 8 is a flowchart for explaining data processing (A) to (D) performed in the erasing system 100 according to the present invention. Below, each data processing (A)-(D) is explained in full detail.

<Data processing (A)>
Data processing (A) is processing for receiving claim data 130 from the company system 110 and generating bond management data 700.

  In step S <b> 801, the erasing system 100 receives the billing data 130 from the company system 110. The received billing data 130 is temporarily stored in the main storage unit 202.

  In step S <b> 802, the application system 100 reads the data of the billing destination 301, the payment due date 302, the billing amount 303, and the transfer destination 304 from the billing data 130 stored in the main storage unit 202. Thereafter, the application system 100 generates bond management data 700 based on the read data. The generated bond management data 700 is stored in the management DB 105. The billing destination 701, payment due date 702, billing amount 703, and transfer destination 704 of the claim management data 700 correspond to the billing destination 301, payment due date 302, billing amount 303, and transfer destination 304 of the billing data 130, respectively.

<Data processing (B)>
Data processing (B) is processing for receiving the occurrence record data 135 from the relay system 115 and updating the relevant bond management data 700.

  In step S811, the revocation system 100 receives the generated record data 135 from the relay system 115. The received generation record data 135 is temporarily stored in the main storage unit 202.

  In step S812, the application system 100 uses the occurrence record data 135 stored in the main storage unit 202 to obtain the debtor information 401, creditor information 402, face amount 403, payment date 404, and record number 405. Is read. Thereafter, the clearing system 100 identifies the settlement account information included in the read creditor information 402, and determines whether or not the transfer destination 704 of the credit management data 700 matches the identified settlement account. . If it is determined that they match, the application system 100 specifies the bond management data 700 including the data of the detected transfer destination 704.

  In step S813, the application system 100 updates the face value 705 and the record number 708 of the specified bond management data 700 based on the read occurrence record data 135. The updated bond management data 700 is stored in the management DB 705.

<Data processing (C)>
The data processing (C) is processing for receiving deposit / withdrawal data 145 from the EB system 120 and updating the corresponding bond management data 700.

  In step S <b> 821, the application system 100 receives the deposit / withdrawal data 145 from the EB system 120. The received deposit / withdrawal data 145 is temporarily stored in the main storage unit 202.

  In step S822, the application system 100 reads at least the data record 602 from the deposit / withdrawal data 145 stored in the main storage unit 202. The application system 100 determines whether there is data matching the transfer destination 704 of the bond management data 700 based on the deposit account information included in the read data record 602. In response to the determination that there is matching data, the cancellation system 100 specifies the bond management data 700 including the data of the detected transfer destination 704.

  In step S823, the application system 100 sets the settlement date 706 and settlement amount 707 of the specified bond management data 700 based on the deposit date and transaction amount of the data record 602 of the read deposit / withdrawal data 145, respectively. Update. The updated bond management data 700 is stored in the management DB 705.

  In one embodiment of the present invention, the record number of the electronically recorded bond may be stored in the EDI information of the data record 602 of the read / withdrawal data 145 that has been read. This means that the deposit / withdrawal data has reached the due date for the subject electronic record receivable, the inter-account remittance settlement has been performed, and the record data such as payment has occurred.

  In step S824, the application system 100 reads the updated bond management data 700, and determines whether or not the charged amount 703 and the settlement amount 707 match. If it is determined that they match, the erasure system 100 sets a flag such as a value indicating “confirmation of erasure” in the erasure flag 710 of the data.

  Further, in one embodiment of the present invention, the charge amount 703 and the payment amount 707 may not match. This is because the transfer deposit may be made after subtracting the amount corresponding to the fee. In such a case, the deposit / withdrawal data 145 can include information on the destination bank and the destination branch, so the application system 100 refers to a predetermined fee table (not shown) and settles the bill amount 703 and settlement. It can be determined that the difference from the amount 707 is within a predetermined fee amount range. As a result, when it is determined that it is within the predetermined range, the erasure system 100 sets a flag such as a value indicating “confirmation of erasure” in the erasure flag 710 of the data.

  On the other hand, if the charge amount 703 and the settlement amount 707 do not match and the difference is not within the predetermined fee amount range, the application system 100 sets the application application flag “710” to the “application confirmation error”. A flag such as a value indicating "is set.

<Data processing (D)>
Data processing (D) is processing for receiving the payment record data 140 from the relay system 115 and updating the corresponding bond management data 700. It should be understood that this data processing (D) is processing that is not performed when there is no corresponding electronic record receivable.

  In step S831, the revocation system 100 receives the payment record data 140 from the relay system 115. The received payment record data 140 is temporarily stored in the main storage unit 202.

  In step S832, the application system 100 reads creditor information 501, payment amount 502, payment date 503, and record number 504 from the payment record data 140 stored in the main storage unit 202. The application system 100 determines whether there is data that matches the transfer destination 704 of the bond management data 700 based on the read creditor information 501. In this determination, it may be determined whether or not the recording number 504 and the recording number 708 match. In response to the determination that there is matching data, the cancellation system 100 specifies the bond management data 700 including the data of the detected transfer destination 704.

  In step S833, the application system 100 updates the confirmation flag 709 of the specified bond management data 700. The updated bond management data 700 is stored in the management DB 705.

(Other embodiments)
Electronically recorded receivables are known to be divided and transferred (see Non-Patent Document 1). Even if the divisional assignment has been made, the record number 405 included in the generated record data 135 is included in the record number of the electronic record receivable after the division. For this reason, the revocation system 100 according to the present invention may receive transfer record data of an electronically recorded bond from the relay system 115 and recreate the corresponding bond management data 700 according to the transfer record data.

  The application system 100 according to the present invention compares the due date 702 included in the claim management data 700 with the current date and time, identifies the claim management data for which the due date has passed, and warns the user. It can also be shown.

  Although the principle of the present invention has been described above with reference to exemplary embodiments, those skilled in the art will appreciate that various embodiments that change in configuration and details can be realized without departing from the spirit of the present invention. Will understand. That is, the present invention can take an embodiment as, for example, a system, apparatus, method, program, or storage medium.

100 Erase system 105 Management DB (database)
110 In-house system 115 Relay system 120 EB system 125 Densai net 130 Billing data 135 Occurrence record data 140 Payment record data 145 Deposit / withdrawal data 700 Claim management data

Claims (6)

A system for confirming payment for a claim,
The system, a single even obligor selects one payment by funds transfer and electronic recording receivables using the transfer-only account in order to perform a payment with respect to the claims, which can confirm the payment with respect to the claims System ,
A means for receiving claim data from a creditor server and generating claim management data, wherein the claim management data is stored in a management database and includes an identifier of a debtor, a scheduled payment date, a billing amount, and the debtor. Means including at least an assigned pay-only account;
Receiving record data transmitted from an electronic bond recording institution is received, the claim management data associated with the generated record data is read from the management database via the identification number of the account dedicated for transfer, and the read claims management Means for updating the claim management data by adding information on the face value and record number of the electronically recorded claim to the data;
Receiving deposit / withdrawal data transmitted from the bank system, and managing the claim management data associated with the deposit / withdrawal data via at least one of the identification number of the bank account for transfer and the record number of the electronically recorded loan Means for updating the claim management data by reading information from the database and adding the information of the settlement date and the settlement amount to the read claim management data;
Read the claim management data, determine whether or not the billing amount and the settlement amount included in the claim management data match, and if the predetermined condition is met, data indicating completion of application confirmation is received as the claim management data system, characterized in that in addition to the data and means for updating the credit management data.   The payment record data transmitted from the electronic bond record organization is received, and the claim management data associated with the payment record data is read from the management database via the identification number of the account dedicated for transfer, and read. 2. The system according to claim 1, further comprising means for further adding data indicating that settlement by an electronically recorded loan is completed to the bond management data to update the bond management data.   The apparatus further comprises means for reading from the management database, claim management data associated with the payment record data via a record number of the electronic record claim included in the received payment record data. 2. The system according to 2. A method performed in a system for confirming payment for a claim,
The system, a single even obligor selects one payment by funds transfer and electronic recording receivables using the transfer-only account in order to perform a payment with respect to the claims, which can confirm the payment with respect to the claims System ,
The method
Receiving claim data from a creditor server and generating claim management data, wherein the claim management data is stored in a management database and includes an identifier of a debtor, a scheduled payment date, a billing amount, and the debtor. Including at least an assigned pay-only account; and
Receiving record data transmitted from an electronic bond recording institution is received, the claim management data associated with the generated record data is read from the management database via the identification number of the account dedicated for transfer, and the read claims management Updating the claim management data by adding information on the face value and record number of the electronically recorded claim to the data;
Receiving deposit / withdrawal data transmitted from the bank system, and managing the claim management data associated with the deposit / withdrawal data via at least one of the identification number of the bank account for transfer and the record number of the electronically recorded loan Reading from the database, adding the payment date and payment amount information to the read bond management data and updating the bond management data;
Read the claim management data, determine whether or not the billing amount and the settlement amount included in the claim management data match, and if the predetermined condition is met, data indicating completion of application confirmation is received as the claim management data method characterized in that in addition to the data and a step of updating said credit management data.   The payment record data transmitted from the electronic bond record organization is received, and the claim management data associated with the payment record data is read from the management database via the identification number of the account dedicated for transfer, and read. 5. The method according to claim 4, further comprising the step of updating the bond management data by further adding data indicating that the settlement by the electronically recorded bond is completed to the bond management data.   6. The method according to claim 5, further comprising a step of reading from the management database, claim management data associated with the payment record data via a record number of an electronic record claim included in the received payment record data. The method described in 1.

Images