JP6568547B2 - Information processing apparatus, information processing method, and program - Google Patents

Description

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

  Electronically-recorded receivables are known as a means of settlement that achieves efficient funding for companies. Electronically recorded receivables are subject to requirements for the generation and transfer of receivables, etc. by electronically recording them in the record book of an electronic receivables recording organization (hereinafter also referred to as “recording organization”). Electronically recorded receivables not only digitize traditional paper bill transactions, but also include nominated receivables such as accounts receivable.

  In addition, a service called collective factoring for accounts receivable in companies is known. In batch factoring, for example, a company (delivery company) that sells or provides products or services, etc., transfers accounts receivable to a factoring company (hereinafter also referred to as “collection agency”), so that the factoring company delivers the company. Receivable collection on behalf of On the other hand, the delivery company can also quickly convert the trade receivables into cash by transferring the trade receivables to a factoring company.

  Furthermore, a technique for performing batch factoring using an electronically recorded bond recorded in a database of a recording organization is known (see, for example, Patent Document 1).

Japanese Patent No. 5142228

  Here, the format of the data used when requesting the recording organization to generate an electronically recorded bond is defined by “Densai Net” (registered trademark). However, this data format is not scheduled to set information (for example, user number, account number, etc.) of both the delivery company and the collection agent.

  For this reason, for example, the person in charge of the collection agent, etc., transfers money to the payment account of the supplier (payment of payment) when the supplier transfers the receivables to the collection agent or when the collection agent collects the claims. Processing) was necessary.

  One embodiment of the present invention has been made in view of the above points, and an object thereof is to efficiently perform settlement in batch factoring using an electronically recorded bond.

  In order to achieve the above object, in one embodiment of the present invention, a factoring contract is concluded between a first receiving unit that receives bond application data and at least two of a payment company, a delivery company, and a factoring company. A determination unit that determines whether or not the factoring contract is concluded by the determination unit, the identification information of the delivery company included in the claim application data is set in a predetermined data item A first transmission unit that transmits the generated record request data to the electronic bond recording organization.

  According to the embodiment of the present invention, it is possible to efficiently perform settlement in collective factoring using an electronically recorded bond.

It is a figure which shows the system configuration | structure of an example of the electronic record loan processing system which concerns on 1st embodiment. It is a figure which shows the hardware constitutions of an example of the electronic record loan processing apparatus which concerns on 1st embodiment. It is a figure which shows the function structure of an example of the electronic record loan processing apparatus which concerns on 1st embodiment. It is a flowchart which shows an example of the generation | occurrence | production recording process of the electronic record loan concerning 1st embodiment. It is a figure which shows an example of generation | occurrence | production record request data. It is a figure of an example for demonstrating the due date settlement of an electronic record loan. It is a flowchart which shows an example of the due date settlement process of the electronic record loan which concerns on 1st embodiment. It is a figure of an example for demonstrating discount transfer of an electronic record receivable. It is a flowchart which shows an example of the discount transfer process of the electronic record receivable concerning 1st embodiment. It is a flowchart which shows the other example of the discount transfer process of the electronic record loan which concerns on 1st embodiment. It is a figure which shows the system configuration | structure of an example of the electronic record loan processing system which concerns on 2nd embodiment. It is a figure which shows the function structure of an example of the electronic record loan processing apparatus which concerns on 2nd embodiment. It is a flowchart which shows an example of the generation | occurrence | production recording process (1/2) of the electronic record loan which concerns on 2nd embodiment. It is a figure which shows an example of the loan application data stored in bond application data DB. It is a flowchart which shows an example of generation | occurrence | production recording processing (2/2) of the electronic record receivable concerning 2nd embodiment.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

[First embodiment]
<System configuration>
First, the system configuration of the electronically recorded bond processing system 1 according to the present embodiment will be described with reference to FIG. FIG. 1 is a diagram showing a system configuration of an example of an electronic record bond processing system 1 according to the present embodiment.

  As shown in FIG. 1, an electronic record receivable processing system 1 according to the present embodiment includes a bank system 10, a debtor terminal 20, a creditor terminal 30, and a recording institution system 40. Communication is established through a wide area network N1 such as a line network.

  The bank system 10 is a computer system (information processing system) possessed by a financial institution handling deposits and savings such as a bank. The bank system 10 includes an electronic record receivable processing apparatus 100 and a billing system 200. The electronically recorded bond processing apparatus 100 and the billing system 200 are communicably connected via a network N2 such as a LAN (Local Area Network).

  The electronic record receivable processing apparatus 100 is an information processing apparatus or information processing system that provides a service related to an electronic record receivable.

  For example, in response to a request from the debtor terminal 20, the electronic record receivable processing apparatus 100 requests the recording organization system 40 to record the occurrence of an electronic record receivable. In addition, the electronic record receivable processing apparatus 100 makes a request for the transfer record of the electronic record receivable to the recording institution system 40 in response to a request from the debtor terminal 20, for example. Furthermore, the electronic record receivable processing apparatus 100 discounts the settlement account of the creditor (“authentic creditor” described later) when the electronic record receivable is discounted or when the due date of the electronic record receivable comes. Process to transfer the amount and payment amount.

  The accounting system 200 is information that performs various processes for realizing banking operations such as, for example, management of settlement accounts for electronically recorded receivables, deposits / withdrawals and transfers, remittances, exchange transactions, and fund settlement with other financial institutions. It is a processing device or an information processing system.

  Note that the banking system 10 includes various systems such as an EB (Electronic Banking) system that provides services such as Internet banking or online banking, and a system that performs processing for supporting the above-described banking operations. Also good.

  The debtor terminal 20 is an information processing apparatus used by a paying company or the like who becomes a debtor of an electronic record receivable. A person in charge such as a paying company can use the debtor terminal 20 to perform an operation for requesting an occurrence record of an electronically recorded bond. The debtor terminal 20 may be a PC (personal computer), a smartphone, a tablet terminal, or the like.

  The creditor terminal 30 is an information processing apparatus that is used by a delivery company having a claim such as a trade receivable. The person in charge of the supplier company, etc. may perform a discount transfer request operation for electronically recorded receivables using the creditor terminal 30 when a collective factoring contract is concluded with the paying company, etc. and the collection agent. it can. The creditor terminal 30 may be a PC (personal computer), a smartphone, a tablet terminal, or the like, for example.

  Here, the collective factoring contract is a contract in which the collection agent collects the receivable by the delivery company or the like by transferring the receivable to the collection agent. When the payment date arrives, the delivery company etc. can receive a full payment or an amount close to the full payment. In addition, when a supplier, etc. discounts a claim before the due date, a request to transfer the claim to a back finance (for example, a financial institution such as a bank) that provides a discount price (ie discount transfer of an electronically recorded claim) ), It is possible to receive payment of an amount obtained by discounting a predetermined rate from the full amount.

  When a collective factoring contract is concluded between the paying company, the delivery company, etc. and the collection agent, the debtor in the electronically recorded receivables such as the above receivables is the paying company, etc. . In addition, the creditor in the electronic record receivable becomes a collection agent. On the other hand, the delivery company, etc. is in a position to request the collection agency by transferring the receivables to the collection agency.

  Therefore, hereinafter, when a collective factoring contract is concluded between the paying company, the delivery company, etc. and the collection agent, the delivery company is also referred to as a “genuine creditor”. At this time, the paying company is a debtor, and the collection agent is a creditor. On the other hand, when a collective factoring contract is not concluded between the paying company, the delivery company, etc. and the collection agent, the paying company, etc. is the debtor and the delivery company, etc. is the creditor.

  The recording institution system 40 is an information processing apparatus or information processing system included in the recording institution. The recording institution system 40 manages the records such as generation and transfer of electronic record receivables.

  The configuration of the electronic record bond processing system 1 shown in FIG. 1 is an example, and another configuration may be used. For example, a plurality of debtor terminals 20 may be included in the electronically recorded bond processing system 1 according to the present embodiment. Similarly, for example, a plurality of creditor terminals 30 may be included in the electronically recorded claim processing system 1 according to the present embodiment. Further, for example, the electronic record receivable processing system 1 according to the present embodiment may be configured such that the recording institution system 40 is included in the bank system 10.

<Hardware configuration>
Next, the hardware configuration of the electronically recorded bond processing apparatus 100 according to the present embodiment will be described with reference to FIG. FIG. 2 is a diagram illustrating a hardware configuration of an example of the electronic record bond processing device 100 according to the present embodiment.

  As shown in FIG. 2, the electronic record bond processing apparatus 100 according to the present embodiment includes an input device 11, a display device 12, an external I / F 13, a communication I / F 14, a ROM (Read Only Memory) 15, and the like. Have In addition, the electronic record bond processing apparatus 100 according to the present embodiment includes a RAM (Random Access Memory) 16, a CPU (Central Processing Unit) 17, and an HDD (Hard Disk Drive) 18. These hardware are connected to each other by a bus B.

  The input device 11 is, for example, a keyboard, a mouse, a touch panel, or the like, and is used by a user to input various operation signals. The display device 12 is, for example, an LCD (Liquid Crystal Display) or the like, and displays a processing result. The electronic record bond processing apparatus 100 may be configured to connect the input device 11 and / or the display device 12 to the bus B when necessary.

  The external I / F 13 is an interface with an external device. The external device includes a recording medium 13a. The electronic record bond processing apparatus 100 can read and / or write to the recording medium 13a via the external I / F 13. Examples of the recording medium 13a include a flexible disk, a CD, a DVD, an SD memory card, and a USB memory. The recording medium 13a may store a program that realizes the present embodiment.

  The communication I / F 14 is an interface for connecting the electronic record bond processing apparatus 100 to the network N1 or the network N2. The electronically recorded bond processing apparatus 100 can perform data communication with the debtor terminal 20, the creditor terminal 30, the recording organization system 40, and the billing system 200 via the communication I / F 14.

  The ROM 15 is a non-volatile semiconductor memory that can retain programs and data even when the power is turned off. The ROM 15 stores programs such as BIOS (Basic Input / Output System) executed when the electronic record bond processing apparatus 100 is started up, and data such as OS (Operating System) settings and network settings.

  The RAM 16 is a volatile semiconductor memory that temporarily stores programs and data. The CPU 17 reads out a program or data from a storage device such as the ROM 15 or the HDD 18 onto the RAM 16 and executes processing based on the program or data, thereby executing control for the entire electronic record bond processing device 100 and other functions. Device.

  The HDD 18 is a non-volatile memory that stores programs and data. The programs and data stored in the HDD 18 include a program that realizes the present embodiment, an OS that is basic software for controlling the entire electronic record bond processing apparatus 100, and application software that provides various functions on the OS. The HDD 18 manages stored programs and data by a predetermined file system and / or DB (database).

  The electronically recorded bond processing apparatus 100 may include a storage device such as an SSD (Solid State Drive) instead of the HDD 18 or in combination with the HDD 18.

  The electronic record bond processing apparatus 100 according to the present embodiment has the hardware configuration shown in FIG.

<Functional configuration>
Next, a functional configuration of the electronic record bond processing device 100 according to the present embodiment will be described with reference to FIG. FIG. 3 is a diagram illustrating a functional configuration of an example of the electronic record bond processing device 100 according to the present embodiment.

  As shown in FIG. 3, the electronic record receivable processing apparatus 100 according to the present embodiment includes a reception unit 101, an occurrence record request processing unit 102, a due date settlement processing unit 103, a discount transfer processing unit 104, and a settlement processing unit. 105. Each of these functional units is realized by a process that the CPU 17 causes one or more programs installed in the electronic record bond processing apparatus 100 to execute.

  The electronically recorded bond processing apparatus 100 according to the present embodiment includes a user data DB 106, a contract data DB 107, a bond data DB 108, and a settlement data DB 109. Each of these storage units can be realized using, for example, the HDD 18. Note that at least one of these storage units may be realized using a storage device connected to the electronic record bond processing device 100 via the network N1 or the network N2.

  The receiving unit 101 receives various data from the debtor terminal 20, the creditor terminal 30, and the recording institution system 40. For example, the accepting unit 101 receives from the debtor terminal 20 the claim application data for requesting the occurrence record of the electronic record claim. For example, the reception unit 101 receives discount application data from the creditor terminal 30 for requesting discount transfer of an electronically recorded bond. Further, for example, the accepting unit 101 receives from the recording institution system 40 settlement notification data for performing settlement of the due date of the electronically recorded receivable (that is, settlement when the due date of the electronically recorded receivable has arrived).

  When the receiving unit 101 receives the claim application data, the generation record request processing unit 102 performs a process for recording the occurrence of the electronic record bond in the recording organization. That is, the generation record request processing unit 102 generates generation record request data based on the claim application data, and transmits the generated generation record request data to the recording organization system 40, thereby requesting the generation record request for the electronic record receivable. I do.

  At this time, the occurrence record request processing unit 102 refers to the contract data DB 107 and determines whether or not a collective factoring contract has been concluded among the three parties of the payment company, the delivery company, and the collection agent. Then, when the collective factoring contract is not concluded between the three parties, the occurrence record request processing unit 102 creates occurrence record request data in which the paying company is a debtor and the delivery company is a creditor. On the other hand, when the collective factoring contract is concluded among the three parties, the occurrence record request processing unit 102 uses the paying company as the debtor and the collection agent as the creditor, and the information (user number) ) Is generated as a predetermined data item. Details of the generated record request data will be described later.

  The due date settlement processing unit 103 performs processing related to due date settlement of the electronically recorded receivable when the accepting unit 101 receives the settlement notification data. In other words, the due date settlement processing unit 103 requests the settlement processing unit 105 to create transfer data based on the settlement notification data.

  At this time, the due date settlement processing unit 103 determines whether or not the creditor specified in the settlement notification data is a collection agent. If the creditor specified in the settlement notification data is not a collection agent, the due date settlement processing unit 103 requests the settlement processing unit 105 to create transfer data with the creditor as the recipient. On the other hand, when the creditor specified in the settlement notification data is a collection agent, the due date settlement processing unit 103 settles the creation of transfer data with a genuine creditor (that is, a delivery company, etc.) as the recipient. Request to the processing unit 105.

  The discount transfer processing unit 104 performs processing related to discount transfer of electronically recorded receivables when the receiving unit 101 receives discount application data. In other words, the discount transfer processing unit 104 requests the settlement processing unit 105 to create transfer data for a discount amount with a genuine creditor as the recipient based on the discount application data, and transfers the electronically recorded credit to back finance. The recording institution system 40 is billed to do so.

  The settlement processing unit 105 creates transfer data in response to requests from the due date settlement processing unit 103 and the discount transfer processing unit 104. Then, the settlement processing unit 105 transmits the created transfer data to the billing system 200.

  The user data DB 106 stores user data including various types of information related to the user of the electronic record bond processing device 100. In the user data, for example, a user number for identifying a user and user's payment information (such as an account number for identifying a user's payment account) are associated with each other. In the user data, for example, a user number is associated with information indicating whether or not the user with this user number is a collection agent.

  The contract data DB 107 stores contract data including various types of information related to a batch factoring contract between users of the electronic record receivable processing apparatus 100. In the contract data, for example, the user number is associated with the user number of the user who has concluded a collective factoring contract with the user of this user number.

  The bond data DB 108 stores bond data including various types of information related to electronically recorded bonds recorded in the recording organization. In the bond data, for example, a record number for identifying an electronic record loan recorded in the recording institution, an electronic record date recorded in the recording institution, an amount of the claim, a due date, a requester Ref. No. And are associated.

  The settlement data DB 109 stores settlement data including various information related to genuine creditors. In the payment data, for example, a record number for identifying an electronically recorded receivable recorded in a recording institution, and payment information for specifying a settlement account of a genuine creditor (an account number for identifying a settlement account of a genuine creditor, etc. ).

<Details of processing>
Next, the details of the processing of the electronic record bond processing device 100 according to the present embodiment will be described.

≪Record of occurrence of electronic record receivables≫
In the following, processing when a paying company or the like records occurrence of an electronically recorded bond using the debtor terminal 20 will be described with reference to FIG. FIG. 4 is a flowchart showing an example of an electronic record bond occurrence recording process according to the present embodiment.

  The accepting unit 101 of the electronically recorded claim processing apparatus 100 receives the claim application data for requesting the occurrence record of the electronically recorded claim from the debtor terminal 20 (step S401). The credit application data includes, for example, a user number for identifying a paying company, biller information, debtor information, creditor information, biller Ref. No. , Receivable amount, due date, electronic record date, etc.

  Here, the claimant information is information relating to a person (requester) who requests the occurrence record of the electronic record receivable. For example, the account number of the claimant, the financial institution code of this account, the branch code, and the account type The code and the name of the requester's agent, the address of the agent, and the name of the representative such as the agent are included. The debtor information is information relating to the debtor of the receivable (that is, the paying company), and includes, for example, the account number of the debtor, the financial institution code of this account, the branch code, and the account type code. Creditor information is information related to the creditor of the claim (that is, the delivery company, etc.), for example, a user number identifying the creditor, an account number of the creditor, a financial institution code of this account, a branch code, and Account type code etc. are included. Requester Ref. No. Is information input as a remarks column or an optional input column. The amount of receivable, the due date, and the date of electronic recording are the amount of receivable, the due date, and the date of recording in the recording organization, respectively.

  In addition, the paying company, etc., processes the claim application data electronically by executing the operation of requesting the record of the occurrence of the electronically recorded receivable using the debtor terminal 20 when the receivable is incurred with the supplier company, etc. Can be transmitted to the device 100.

  Next, when the receiving unit 101 receives the claim application data, the generation record request processing unit 102 of the electronic record claim processing device 100 creates the generation record request data based on the claim application data (step S402).

  Here, the generated record request data will be described with reference to FIG. FIG. 5 is a diagram showing an example of the generated record request data.

  As shown in FIG. 5, the occurrence record request data is data for requesting the recording record of the occurrence of electronic record receivables to the recording organization system 40, and includes request number, claimant information, debtor information, creditor. Information, claimant Ref. No. , Receivable amount, due date, electronic record date, transfer restriction flag, etc.

  In the request number, information for identifying the generated record request data is set. In addition, the claimant information, the debtor information, the creditor information, the amount of the claim, the payment date, and the electronic record date include the claimant information, the debtor information included in the claim application data received in step S401, Creditor information, credit amount, payment date, and electronic record date are set. Furthermore, the claimant Ref. No. If the collective factoring contract is concluded between the three parties according to the determination result in step S403, which will be described later, the user number of the genuine creditor (that is, the paying company or the like) is set.

  Next, the occurrence record request processing unit 102 of the electronic record bond processing device 100 refers to the contract data DB 107 and has concluded a collective factoring among the paying company, the delivery company, etc. and the collection agent. It is determined whether or not (step S403).

  That is, the occurrence record request processing unit 102 refers to the contract data DB 107, for example, the user number of the paying company or the like included in the claim application data received in step S401 and the claim included in the claim application data. Based on the user number set in the person information, it is determined whether or not collective factoring is concluded among the three parties of the payment company, the delivery company, etc., and the collection agent.

  In step S403 described above, it is determined whether or not a collective factoring is concluded between the paying company, the delivering company, and the collection agent. However, the present invention is not limited thereto. It may be determined whether collective factoring is concluded between at least two of the delivery company and the collection agent.

  In step S403, if it is determined that the collective factoring contract is not concluded between the three parties, the occurrence record request processing unit 102 of the electronic record bond processing apparatus 100 records the occurrence record request data created in step S402 above. It transmits to the engine system 40 (step S404).

  In this way, when the collective factoring contract is not concluded between the three parties, the electronic record receivable processing apparatus 100 generates the occurrence record request data in which the debtor is “paying company, etc.” and the creditor is “delivery company, etc.”. Transmit to the recording institution system 40. As a result, the electronically recorded claim processing apparatus 100 can request an occurrence record of a claim whose debtor is “paying company etc.” and whose creditor is “delivery company etc.”.

  Next, the occurrence record request processing unit 102 of the electronic record claim processing apparatus 100 determines whether or not an electronic record claim has been established (step S405). That is, after the generated record request processing unit 102 transmits the generated record request data in the above step S404 to the recording institution system 40, the response returned from the recording institution system 40 is a response indicating the establishment of the electronic record bond. It is determined whether or not there is. The response indicating the establishment of the electronic record receivable includes a record number for identifying the electronic record receivable recorded in the recording organization.

  If it is determined in step S405 that the electronic record receivable has not been established, the generated record request processing unit 102 of the electronic record receivable processing apparatus 100 generates an error indicating that the electronic record receivable has not been established, as described in the above step. The debtor terminal 20 that is the transmission source of the claim application data in S401 is notified (step S406). On the other hand, when it is determined that the electronic record receivable has been established, the generated record claim processing unit 102 of the electronic record receivable processing apparatus 100 proceeds to the process of step S412 described later.

  If it is determined in step S403 that the three party has concluded a collective factoring contract, the generated record claim processing unit 102 of the electronic record claim processing apparatus 100 generates the claim for the generated record request data created in step S402 above. Each information set in the operator information is overwritten on the information of the collection agent (step S407).

  That is, the occurrence record request processing unit 102 uses the financial institution code, branch code, account type code, and account number set in the creditor information of the occurrence record request data as the collection agency financial institution code, branch code. Overwrite the account type code and account number.

  Next, the generated record request processing unit 102 of the electronic record claim processing apparatus 100 receives the requester Ref. No. A user number of a genuine creditor (that is, a delivery company, etc.) is set in (step S408).

  Next, the generated record request processing unit 102 of the electronic record bond processing apparatus 100 transmits the generated record request data to the recording institution system 40 (step S409).

  In this way, when the collective factoring contract is concluded between the three parties, the electronically recorded receivable processing apparatus 100 sets the obligor as “payment company, etc.”, the creditor as “collection agent”, and the authentic receivable. The user number of the subscriber (that is, the delivery company, etc.) No. The generated record request data set in (2) is transmitted to the recording institution system 40.

  Thereby, the electronically recorded claim processing apparatus 100 can request the occurrence record of the claim whose debtor is “payment company etc.” and whose creditor is “collection agent”. At this time, the requester Ref. No. Authentic creditors can be identified by the user number set in.

  Next, the generated record claim processing unit 102 of the electronic record claim processing apparatus 100 determines whether or not an electronic record claim has been established (step S410). That is, the generated record request processing unit 102 determines whether the response returned from the recording institution system 40 with respect to the transmission of the generated record request data is a response indicating the establishment of the electronic record bond, as in step S405 above. Determine whether. The response indicating the establishment of the electronic record receivable includes a record number for identifying the electronic record receivable recorded in the recording organization.

  If it is determined in step S410 that an electronically recorded claim is established, the generated record request processing unit 102 of the electronically recorded claim processing apparatus 100 authenticates the creditor's settlement information (account number, financial institution code, branch code). , And account type code) are created in association with the record number and request number, and stored in the settlement data DB 109 (step S411).

  That is, the generation record request processing unit 102 stores the requester Ref. No. The payment information stored in association with the user number set in is associated with the recording number and the request number, and payment data is created and stored in the payment data DB 109. The generation record request processing unit 102 may create settlement data by associating either the request number or the recording number with the settlement information.

  As a result, the claimant Ref. No. The payment information of the genuine creditor set in the payment data DB 109 is managed as the payment data.

  Next, the occurrence record request processing unit 102 of the electronic record receivable processing apparatus 100 creates receivable data having the same contents as the electronic record receivable recorded in the recording organization and stores it in the receivable data DB 108 (step S412). . Since the electronic record receivable is recorded in the recording institution, the electronic record receivable processing apparatus 100 does not necessarily need to create the receivable data (that is, the electronic record receivable processing apparatus 100 has the receivable data DB 108. It is not necessary.)

  If it is determined in step S410 that the electronic record receivable has not been established, the generated record request processing unit 102 of the electronic record receivable processing apparatus 100 determines that the electronic record receivable has not been established, as in step S406. Is notified to the debtor terminal 20 that is the transmission source of the claim application data (step S413).

  As described above, the electronic record receivable processing apparatus 100 according to the present embodiment requests the record organization system 40 to record the occurrence of the electronic record receivable in response to a request from the debtor terminal 20, thereby allowing the record organization to Recorded receivables can be recorded.

  At this time, the electronically recorded receivable processing apparatus 100 according to the present embodiment, when a collective factoring contract is concluded between the paying company, the delivering company, etc. and the collection agent, the collection agent in the creditor information And the user number of the delivery company etc. are set in the requester Ref. No. And request the record of occurrence of electronically recorded receivables.

  Thereby, in the electronically recorded receivable processing apparatus 100 according to the present embodiment, as will be described later, when the settlement date of the electronically recorded receivable arrives or when a discount transfer is requested, the authentic creditor settlement account is set up. It becomes possible to identify and transfer the payment amount.

≪Settlement of electronic record receivables≫
In the following, a case will be described in which due date payment is performed when the due date of the electronically recorded receivable comes.

  First, with reference to FIG. 6, explanation will be given on the due date settlement due to the payment due date of electronic record receivables when a lump sum factoring contract is concluded between the paying company, the delivery company, etc. and the collection agent. To do. FIG. 6 is a diagram illustrating an example for explaining due date settlement of electronically recorded receivables.

  As shown in FIG. 6, when a collective factoring contract is concluded between a paying company, a delivery company, etc., and a collection agent, the paying company, etc. is a debtor, and the collection agent is a creditor. At this time, when the due date of the electronically recorded receivable arrives, the settlement amount of this electronically recorded receivable is transferred from the settlement account of the debtor to the settlement account of the genuine creditor (delivery company, etc.).

  This is because the collection agent that is a creditor merely collects the debt on behalf of the delivery company that is a genuine creditor. The collection agent can obtain a fee for collection of receivables.

  Next, the due date settlement processing when the due date of the electronically recorded receivable arrives will be described with reference to FIG. FIG. 7 is a flowchart showing an example of the due date settlement processing for the electronically recorded bond according to the present embodiment.

  The accepting unit 101 of the electronic record receivable processing apparatus 100 receives settlement notification data for performing due settlement of the electronic record receivable from the recording institution system 40 (step S701). The settlement notification data includes, for example, a record number, debtor information, creditor information, credit amount, payment date, and the like.

  Note that the recording institution system 40, when an electronic record receivable whose payment due date comes after a predetermined number of days is recorded, the record number of the electronic record receivable, debtor information, creditor information, claim amount, payment due date, etc. Is sent to the electronically recorded bond processing apparatus 100.

  Next, the due date settlement processing unit 103 of the electronically recorded claim processing apparatus 100 determines whether or not the creditor of the electronically recorded claim for which due date settlement is performed is a collection agent (step S702). That is, the due date settlement processing unit 103 refers to the user data DB 106, and the user number set in the bond information included in the settlement notification data and that the user of this user number is a collection agent. It is determined whether or not it is associated with information indicating.

  If it is determined in step S702 that the creditor of the electronically recorded receivable for which settlement is due is not a collection agent, the settlement processing unit 105 of the electronically recorded receivable processing apparatus 100 creates transfer data according to the settlement notification data (step S702). S703).

  In other words, the settlement processing unit 105 creates transfer data for transferring a credit amount (settlement amount) from a debtor settlement account to a creditor settlement account on the due date. Here, the settlement account of the debtor is specified from the financial institution code, the branch code, the branch code, the account type code, the account number, and the like set in the debtor information included in the settlement notification data. The creditor's settlement account is specified from the financial institution code, branch code, branch code, account type code, account number, etc. set in the creditor information included in the settlement notification data.

  On the other hand, if it is determined in step S702 that the creditor of the electronically recorded receivable for which the due date settlement is performed is a collection agent, the due date settlement processing unit 103 of the electronically recorded receivable processing apparatus 100 performs the authentic creditor (that is, A settlement account of a delivery company or the like is specified (step S704).

  In other words, the due date settlement processing unit 103 refers to the settlement data DB 109 and sets settlement information (financial institution code, branch code, branch code, account type code, account number, etc.) associated with the record number included in the settlement notification data. ) To identify the settlement account of the genuine creditor.

  Next, the payment processing unit 105 of the electronically recorded bond processing apparatus 100 creates transfer data for transferring the amount of the bond to the payment account specified in the above step S702 on the payment date (step S705). In other words, the settlement processing unit 105 creates transfer data for transferring a credit amount from a debtor's settlement account to a genuine creditor's settlement account on the due date.

  Next, the settlement processing unit 105 of the electronic record receivable processing apparatus 100 determines the receivables of the collection agent from the transfer amount of the transfer data created in step S702 (that is, the receivable amount of the electronic record receivable that is due). A predetermined fee for collection is subtracted (step S706). That is, the transfer amount of the transfer data is an amount obtained by subtracting a predetermined fee from the amount of receivable of the electronically recorded receivable that is due for payment.

  Next, the settlement processing unit 105 of the electronically recorded bond processing apparatus 100 transmits the created transfer data to the billing system 200 (step S707). As a result, the settlement amount (the amount of the receivable or the amount obtained by subtracting the predetermined fee from the amount of the receivable) is transferred to the settlement account designated by the transfer data.

  As described above, when the electronic record receivable processing apparatus 100 according to the present embodiment receives payment notification data from the recording institution system 40, the electronic record receivable processing apparatus 100 can create transfer data of the electronic record receivable that is due for payment.

  At this time, when the creditor of the electronic record receivable that is due for payment is the collection agent, the electronic record receivable processing apparatus 100 according to the present embodiment specifies the settlement account of the genuine creditor and then performs the settlement Transfer data is created to transfer the settlement amount (the amount of receivables or the amount obtained by subtracting a predetermined fee from the amount of receivables) to the account.

  As a result, in the electronic record receivable processing apparatus 100 according to the present embodiment, when a collective factoring contract is concluded between the paying company, the delivering company, etc. and the collection agent, a genuine creditor (delivering company) Etc.) can be transferred to the settlement account (the amount obtained by subtracting a predetermined fee from the amount of receivables).

≪Discount transfer of electronic record receivables≫
Hereinafter, a case where discount transfer of electronically recorded receivables is performed by a genuine creditor will be described.

  First, in the case where a collective factoring contract is concluded between a paying company, a delivery company, etc. and a collection agent, a genuine creditor (delivery company, etc.) makes a discounted transfer of electronically recorded receivables. This will be described with reference to FIG. FIG. 8 is a diagram for explaining an example of discount transfer of electronic record receivables.

  As shown in FIG. 8, when a collective factoring contract is concluded between a paying company, a delivery company, etc. and a collection agent, the paying company, etc. is a debtor, and the collection agent is a creditor. At this time, if a genuine creditor (delivery company, etc.) has applied for discount transfer of electronically recorded receivables, the discount amount from the settlement account of the purchaser who purchases this electronically recorded receivable to the settlement account of the genuine creditor Is transferred. Thereby, the genuine creditor can obtain an amount (discount amount) obtained by discounting a predetermined amount from the amount of the receivable before the due date of the electronically recorded receivable.

  On the other hand, the electronic record receivable is transferred from a collection agent to a purchaser, and then transferred to back finance (for example, a financial institution such as a bank) that provides the purchaser with a discounted amount of money. In the example illustrated in FIG. 8, the case where the collection agent and the purchaser are different from each other has been described. However, the collection agent and the purchaser may be the same company.

  Next, processing when a genuine creditor performs discount transfer of an electronically recorded credit using the creditor terminal 30 will be described with reference to FIG. FIG. 9 is a flowchart showing an example of discount transfer processing of electronic record receivables according to the present embodiment.

  It should be noted that the processing in steps S901 and S902 of the discount transfer process for electronically recorded receivables, which will be described later, is performed three business days before the desired discount date (the date on which the genuine creditor wishes to transfer the discount amount). In addition, the processing in steps S903 to S906 and step S911 in the discount transfer process for electronically recorded bonds is performed two business days before the desired discount date. Further, the processing of step S907 to step S910 of discount transfer processing of electronic record receivables is performed on the discount desired date.

  The accepting unit 101 of the electronically recorded bond processing apparatus 100 receives discount application data for making a request for discount transfer of the electronically recorded bond from the creditor terminal 30 (step S901). The discount application data includes, for example, the record number of the electronically recorded receivable subject to discount transfer, the discount amount, the date on which the discount amount is desired to be transferred (discount date), and the like.

  A genuine creditor (delivery company, etc.) can send discount application data to the electronically recorded claim processing apparatus 100 by performing a discount transfer request operation for the electronically recorded claim using the creditor terminal 30. .

  Next, the discount transfer processing unit 104 of the electronic record receivable processing apparatus 100 refers to the receivable data DB 108 and determines whether the electronic record receivable can be discounted (step S902). That is, for example, the discount transfer processing unit 104 determines that the discount amount included in the discount application data is the credit amount of the electronic record receivable subject to discount transfer (or the discount amount from the receivable amount if a discount has already been performed). It is determined whether or not (amount obtained by subtracting the amount).

  If it is determined in step S902 that the discount can be made, the discount transfer processing unit 104 of the electronically recorded bond processing apparatus 100 refers to the payment data DB 109 and sets the payment account of a genuine creditor (ie, a delivery company). Is identified (step S903).

  That is, the discount transfer processing unit 104 refers to the payment data DB 109 and sets the payment information (financial institution code, branch code, branch code, account type code, account number, etc.) associated with the record number included in the discount application data. ) To identify the settlement account of the genuine creditor.

  Next, the settlement processing unit 105 of the electronically recorded bond processing apparatus 100 creates transfer data for transferring a discount amount to the settlement account specified in the above step S903 on the discount date (step S904). That is, the settlement processing unit 105 creates transfer data for transferring a discount amount from a settlement account of a purchasing company to a settlement account of a genuine creditor on a discount date.

  Next, the settlement processing unit 105 of the electronically recorded bond processing apparatus 100 transmits the transfer data created in step S904 to the billing system 200 (step S904). As a result, the discount amount is transferred to the discount account on the settlement account designated by the transfer data.

  Next, the discount transfer processing unit 104 of the electronic record receivable processing apparatus 100 determines that the electronic record receivable subject to discount transfer has been confirmed after confirming the electronic record receivable subject to discount transfer. The creditor terminal 30 that is the transmission source of the discount application data in S901 is notified (step S906).

  Next, the discount transfer processing unit 104 of the electronic record receivable processing apparatus 100 creates transfer record request data for transferring the electronic record receivable subject to discount transfer from the collection agent to the purchaser (step S907). . The transfer record request data includes the record number of the electronically recorded receivable that is subject to discount transfer, the user number of the collection agent that is the old creditor, and the creditor information of the purchaser that is the new creditor (user number, financial Institution code, branch code, account type code, account number, etc.).

  Next, the discount transfer processing unit 104 of the electronic record receivable processing apparatus 100 transmits the transfer record request data created in step S907 to the recording institution system 40 (step S908). As a result, the electronic record receivable subject to discount transfer is transferred from the collection agent to the purchaser.

  Next, the discount transfer processing unit 104 of the electronic record receivable processing apparatus 100 creates transfer record request data for transferring the electronic record receivable subject to discount transfer from the purchaser to the back finance (step S909). The transfer record request data includes the record number of the electronically recorded receivables subject to discount transfer, the user number of the purchaser who is the old creditor, and the backfinance creditor information of the new creditor (user number, financial institution) Code, branch code, account type code, account number, etc.).

  Next, the discount transfer processing unit 104 of the electronic record receivable processing apparatus 100 transmits the transfer record request data created in step S909 to the recording institution system 40 (step S910). As a result, electronic record receivables subject to discount transfer are transferred from the purchaser to back finance.

  If it is determined in step S902 that the discount is not possible, the discount transfer processing unit 104 of the electronically recorded bond processing apparatus 100 cannot perform the discounted transfer of the electronically recorded bond, and the discount application data in step S901 above. Is notified to the creditor terminal 30 of the sender (step S911).

  As described above, when a request for discount transfer of an electronic record receivable is requested, the electronic record receivable processing apparatus 100 according to the present embodiment specifies a genuine creditor settlement account and then discounts the settlement account. Create transfer data to transfer the amount.

  As a result, in the electronic record receivable processing apparatus 100 according to the present embodiment, when a collective factoring contract is concluded between the paying company, the delivering company, etc. and the collection agent, a genuine creditor (delivering company) Etc.) can be transferred to the settlement account.

  Here, for example, a discount between a genuine creditor and a debtor, for example, a contract for discount transfer at the same time as the occurrence of a claim or a contract for discount transfer on a specified date, etc. The transfer process will be described with reference to FIG. FIG. 10 is a flowchart showing another example of discount transfer processing for electronically recorded bonds according to this embodiment. Note that the processing in steps S902 to S911 in FIG. 10 is the same as the processing in steps S903 to S911 in FIG.

  The discount transfer processing unit 104 of the electronic record receivable processing apparatus 100 refers to the contract data DB 107 and the receivable data DB 108, and specifies the electronic record receivable to be discounted transfer (step S1001).

  That is, first, the discount transfer processing unit 104 refers to the contract data DB 107 for a contract for performing split day transfer at the same time as the occurrence of the above-described receivable, a contract for performing discount transfer on a predetermined date, and the like. The user number of the user who has concluded is specified. Next, the discount transfer processing unit 104 determines that the identified user number is the claimant Ref. No. Among the receivable data set in, receivable data whose discount date comes is specified. Then, the discount transfer processing unit 104 specifies the electronic record receivable having the record number set in the specified receivable data as the electronic record receivable to be discounted.

  Receivable data with a discount date refers to receivable data in which the user number of this user is set in the case of a user who has signed a contract to perform a split day transfer at the same time as the occurrence of the receivable It is. On the other hand, in the case of a user who has entered into a contract to make a discount transfer on a specified date, it will be three business days before the specified date in the receivable data for which the user number of this user is set. It is the bond data.

  Next, the discount transfer processing unit 104 of the electronically recorded bond processing apparatus 100 refers to the bond data DB 108 and determines whether or not the electronically recorded bond specified in step S1001 can be discounted (step S1001). S1002). As the discount amount, for example, an amount determined in advance by the above contract or the like is used.

  As described above, the electronically recorded receivable processing apparatus 100 according to the present embodiment enables the settlement of a genuine creditor even when a contract for discount transfer is previously concluded between the paying company and the delivery company. After specifying the account, transfer data for transferring the discount amount to the settlement account can be created.

[Second Embodiment]
Next, a second embodiment will be described. In the second embodiment, a case will be described in which a debtor such as a paying company does not have a settlement account of a bank having a bank system 10 (deposit and savings handling financial institution). In other words, in the second embodiment, the settlement financial institution of the payment account held by the obligor of the paying company or the like is not a bank having the bank system 10 but another bank (another deposit / savings financial institution). explain.

  In the second embodiment, the difference from the first embodiment will be mainly described, and a portion having substantially the same function as the first embodiment and a portion performing substantially the same processing. Are denoted by the same reference numerals, and the description thereof is omitted.

<System configuration>
First, the system configuration of the electronic record bond processing system 1 according to the present embodiment will be described with reference to FIG. FIG. 11 is a diagram showing a system configuration of an example of the electronic record bond processing system 1 according to the present embodiment.

  As shown in FIG. 11, the electronic record receivable processing system 1 according to the present embodiment includes a bank system 50 that is a computer system of a counter financial institution for a settlement account held by a debtor such as a paying company. The bank system 50 is a bank computer system different from the bank system 10. Hereinafter, for convenience, the bank having the bank system 50 is also referred to as “other bank”.

  The bank system 50 is communicably connected to the debtor terminal 20 and the recording institution system 40 via the network N1. Further, the bank system 50 can perform various processes relating to electronic record receivables. For example, the bank system 50 can make a request for the generation of an electronically recorded bond to the recording institution system 40 in response to a request from the debtor terminal 20.

<Functional configuration>
Next, a functional configuration of the electronic record bond processing device 100 according to the present embodiment will be described with reference to FIG. FIG. 12 is a diagram showing a functional configuration of an example of the electronic record bond processing device 100 according to the present embodiment.

  As shown in FIG. 12, the electronic record bond processing apparatus 100 according to the present embodiment includes an occurrence record request processing unit 102A. Moreover, the electronically recorded bond processing apparatus 100 according to the present embodiment has a bond application data DB 110. The bond application data DB 110 can be realized using, for example, the HDD 18. Note that the claim application data DB 110 may be realized by using a storage device or the like connected to the electronic record bond processing device 100 via the network N1 or the network N2.

  When the reception unit 101 receives the claim application data from the debtor terminal 20 of the debtor having a settlement account of another bank, the occurrence record request processing unit 102A receives the creditor information and the claimant Ref. No. Is overwritten and stored in the claim application data DB 110. Then, the occurrence record request processing unit 102A transmits the overwritten bond application data to the debtor terminal 20.

  Thereafter, a debtor such as a paying company can use the debtor terminal 20 to request the record of occurrence of electronically recorded claims by transmitting the overwritten claim application data to the bank system 50.

  Further, when the occurrence record request processing unit 102A receives the occurrence record notification data from the recording institution system 40 in response to the request for the occurrence record by the debtor terminal 20, the occurrence record request processing unit 102A performs a process for creating settlement data and bond data. . That is, the occurrence record request processing unit 102A determines, for example, whether or not the claim application data whose occurrence record notification data matches a predetermined data item is stored in the claim application data DB, and responds to the determination result. To create settlement data and bond data.

  The claim application data DB 110 is sent to the credit record request processing unit 102A by the creditor information and the claimant Ref. No. Stores credit application data that has been overwritten.

<Details of processing>
Next, the details of the processing of the electronic record bond processing device 100 according to the present embodiment will be described.

≪Record of occurrence of electronic record receivables≫
Hereinafter, processing when a paying company having a settlement account of another bank records the occurrence of an electronically recorded bond using the debtor terminal 20 will be described. First, the processing of the electronically recorded bond processing device 100 when receiving bond application data from the debtor terminal 20 will be described with reference to FIG. FIG. 13 is a flowchart showing an example of the electronic record bond occurrence recording process (1/2) according to the second embodiment.

  The accepting unit 101 of the electronically recorded claim processing apparatus 100 receives the claim application data from the debtor terminal 20 (step S1301).

  In addition, a payment company having a settlement account of another bank, when a claim is generated with a delivery company, etc., the claim application data is obtained by performing an electronically recorded claim request operation using the debtor terminal 20. It can be transmitted to the electronically recorded bond processing apparatus 100.

  Next, the occurrence record request processing unit 102A of the electronic record receivable processing apparatus 100 refers to the contract data DB 107 and concludes a collective factoring between the paying company, the delivery company, etc. and the collection agent. It is determined whether or not (step S1302).

  That is, the generation record request processing unit 102A refers to the contract data DB 107 in the same manner as in step S403 of FIG. 4, for example, the user number of the paying company etc. included in the claim application data received in step S1301 above. Based on the user number set in the creditor information included in the claim application data, whether or not a collective factoring is concluded between the paying company, the delivering company, etc. and the collection agent judge.

  If it is determined in step S1302 that the collective factoring contract is not concluded between the three parties, the generated record request processing unit 102A of the electronic record bond processing apparatus 100 ends the process.

  On the other hand, if it is determined in step S1302 that a collective factoring contract is concluded between the three parties, the generated record claim processing unit 102A of the electronic record loan processing apparatus 100 receives the loan application data received in step S1301 above. Each of the information set in the creditor information is overwritten on the information of the collection agent (step S1303).

  That is, the occurrence record request processing unit 102A obtains the financial institution code, branch code, account type code, and account number set in the creditor information of the claim application data, the collection agency's financial institution code, branch code, Overwrite the account type code and account number.

  Next, the generated record request processing unit 102A of the electronic record claim processing apparatus 100 receives the claimant Ref. No. A user number of a genuine creditor (ie, a delivery company) is set in (Step S1304). The generation record request processing unit 102A receives the claimant Ref. No. In addition to the user number of the genuine creditor, predetermined identification information that is unique in the electronic record bond processing apparatus 100 may be set.

  Next, the occurrence record request processing unit 102A of the electronically recorded claim processing apparatus 100 stores the claim application data overwritten in step S1304 in the claim application data DB 110 (step S1305).

  Here, the claim application data stored in the claim application data DB 110 will be described with reference to FIG. FIG. 14 is a diagram showing an example of the claim application data stored in the claim application data DB 110.

  As shown in FIG. 14, the creditor information of the claim application data stored in the claim application data DB 110 includes information on the collection agent (that is, the user number of the collection agent, financial institution code, branch code, Account type code and account number) are set. In addition, the claimant Ref. No. Is set with the user number of the genuine creditor.

  The claimant Ref. No. In addition to the user number of the genuine creditor, predetermined identification information that is unique in the electronic record credit processing apparatus 100 may be set.

  Next, the occurrence record request processing unit 102A of the electronically recorded claim processing apparatus 100 transmits the claim application data overwritten in step S1304 to the debtor terminal 20 (step S1306).

  Thereby, a debtor such as a paying company can subsequently request the occurrence record of the electronic record receivable by transmitting the overwritten receivable application data to the bank system 50 using the debtor terminal 20. it can.

  Hereinafter, the processing of the electronic record bond processing apparatus 100 when the occurrence record notification data is received from the recording organization system 40 in response to the request for the occurrence record of the electronic record bond will be described with reference to FIG. FIG. 15 is a flowchart showing an example of an electronic record bond occurrence recording process (2/2) according to the second embodiment.

  The accepting unit 101 of the electronically recorded bond processing apparatus 100 receives the occurrence record notification data from the recording organization system 40 (step S1501). The occurrence record notification data includes, for example, request number, record number, creditor information, debtor information, claimant Ref. No. , Receivable amount, due date, electronic record date, etc.

  Next, the occurrence record request processing unit 102A of the electronic record receivable processing apparatus 100 determines whether or not the creditor information of the occurrence record notification data received in step S1501 is information of a collection agent (see FIG. Step S1502). That is, the occurrence record request processing unit 102A refers to the user data DB 106, and the user number set in the creditor information of the occurrence record notification data and the user of this user number is a collection agent. It is determined whether or not the information indicating the presence is associated.

  If it is determined in step S1502 that the creditor information of the occurrence record notification data is not the collection agent information, the occurrence record request processing unit 102A of the electronic record bond processing apparatus 100 ends the process.

  On the other hand, if it is determined in step S1502 that the creditor information of the occurrence record notification data is information of a collection agent, the occurrence record request processing unit 102A of the electronic record claim processing apparatus 100 stores the claim application data DB 110. Referring to it, it is determined whether or not there is claim application data whose occurrence record notification data matches a predetermined data item (step S1503).

  Here, the predetermined data items include, for example, creditor information, debtor information, claimant Ref. No. , Receivable amount, due date, electronic record date, etc. Therefore, the occurrence record request processing unit 102A includes creditor information, debtor information, claimant Ref. No. Then, it is determined whether or not the claim application data DB 110 has a claim application data whose deposit amount, payment date, electronic record date and the like coincide with the occurrence record notification data.

  If it is determined in step S1503 that there is a claim application data whose occurrence record notification data and the predetermined data item match, the occurrence record request processing unit 102A of the electronic record claim processing apparatus 100 displays the settlement information of the genuine creditor. Then, settlement data associated with the recording number and the request number is created and stored in the settlement data DB 109 (step S1504).

  That is, the generation record request processing unit 102A performs the requester Ref. In the user data DB 106 in the same manner as in step S411 of FIG. No. The payment information stored in association with the user number set in is associated with the recording number and the request number, and payment data is created and stored in the payment data DB 109. The generation record request processing unit 102 may create settlement data by associating either the request number or the recording number with the settlement information.

  Next, the generated record request processing unit 102A of the electronic record claim processing apparatus 100 creates claim data having the same contents as the electronic record claim recorded in the recording institution as in step S412 of FIG. The data is stored in the data DB 108 (step S1505).

  As a result, even when the obligor of the paying company does not have a settlement account of the bank having the bank system 10, the obligor, the authentic creditor, and the collection agent are collectively Factoring can be performed.

  On the other hand, if it is determined in step S1503 that there is no claim application data that matches the occurrence record notification data with the predetermined data item, the occurrence record request processing unit 102A of the electronic record claim processing apparatus 100 rejects the occurrence record. The change record request data shown is created and transmitted to the recording institution system 40 (step S1506).

<Summary>
As described above, the electronically recorded receivable processing apparatus 100 according to the first embodiment has the creditor information when the collective factoring contract is concluded between the paying company, the delivering company, and the collection agent. Information on the collection agent and the user number of the delivery company etc. are set in the requester Ref. No. And request the record of occurrence of electronically recorded receivables.

  In addition, the electronically recorded claim processing apparatus 100 according to the first embodiment specifies a genuine creditor settlement account when the payment date of the electronically recorded claim for which the collective factoring contract is concluded is reached. The settlement amount (the amount of receivable or the amount obtained by subtracting a predetermined fee from the amount of receivable) can be transferred to this settlement account.

  Furthermore, the electronic record receivable processing apparatus 100 according to the first embodiment specifies the settlement account of the genuine creditor when the discount transfer of the electronic record receivable for which the collective factoring contract is concluded is performed. Then, you can transfer the discount amount to this settlement account.

  Further, the electronic record receivable processing apparatus 100 according to the second embodiment can perform batch factoring based on the batch factoring contract described above even for a paying company having a settlement account of another bank. For this reason, the bank etc. which have the bank system 10 can provide said collective factoring also to the payment company etc. which have only the settlement account of another bank.

  Note that the present invention is not limited to the specifically disclosed embodiments, and various modifications and changes can be made without departing from the scope of the claims.

DESCRIPTION OF SYMBOLS 1 Electronic record receivable processing system 10 Bank system 20 Debtor terminal 30 Creditor terminal 40 Recording organization system 100 Electronic record receivable processing apparatus 101 Reception part 102 Occurrence record request processing part 103 Due date settlement processing part 104 Discount transfer processing part 105 Payment processing part 106 User data DB
107 Contract data DB
108 Bond Data DB
109 Settlement data DB
200 Account system N1, N2 network

Claims (9)

A first receiving unit for receiving bond application data;
A determination unit that determines whether or not a factoring contract is concluded between at least two of a payment company, a delivery company, and a factoring company;
When the determination unit determines that the factoring contract is concluded, the occurrence record request data in which the identification information of the delivery company included in the claim application data is set in a predetermined data item, A first transmitter for transmitting to
An information processing apparatus. The first transmitter is
When the determination unit determines that the factoring contract is not concluded, the payment company and the delivery company transmit occurrence record request data set to the debtor and the creditor to the electronic bond recording organization, respectively. The information processing apparatus according to claim 1. A second receiving unit for receiving due date settlement data for performing due date settlement of a claim whose payment due date comes after a predetermined number of days;
Based on the due date settlement data, a specific unit that identifies the settlement account of the delivery company;
Based on the due date settlement data, a creation unit that creates transfer data for the settlement account identified by the identification unit;
The information processing apparatus according to claim 1, further comprising: A third receiving unit for receiving discount application data for discount transfer of bonds;
The specific part is:
Based on the discount application data, the settlement account of the delivery company is identified,
The creating unit
The information processing apparatus according to claim 3, wherein transfer data for the payment account specified by the specifying unit is created based on the discount application data.   The information processing apparatus according to claim 4, further comprising: a second transmission unit configured to transmit transfer record request data for transferring a bond to back finance based on the discount application data to the electronic bond recording organization. The transfer record request data includes a first transfer record request data for transferring the claim from the factoring agent to a purchaser of the claim, and a second for transferring the claim from the purchaser to the back finance. Transfer record request data,
The second transmitter is
6. The information processing apparatus according to claim 5, wherein the second assignment record request data is transmitted to the electronic bond recording organization after the first assignment record request data is transmitted to the electronic bond recording organization. When the first receiving unit receives the claim application data from the terminal of the paying company having a predetermined settlement account, and the determination unit determines that the factoring contract is concluded, the claim application A first data item and a second data item included in the data, respectively, set in information relating to the factoring supplier and identification information of the delivery company, and a storage unit for storing in a database;
A third transmission unit for transmitting the claim application data stored by the storage unit to the terminal of the payment company connected to the information processing device;
The information processing apparatus according to any one of claims 1 to 6. A first receiving procedure for receiving bond application data;
A determination procedure for determining whether a factoring contract is concluded between at least two of a paying company, a delivery company, and a factoring company;
When it is determined by the determination procedure that the factoring contract is concluded, the occurrence record request data in which the identification information of the delivery company included in the claim application data is set in a predetermined data item A first transmission procedure to transmit to
An information processing method in which a computer executes . Computer
A first receiving means for receiving bond application data;
A determination means for determining whether or not a factoring contract is concluded between at least two of a payment company, a delivery company, and a factoring company;
When it is determined by the determination means that the factoring contract is concluded, the occurrence record request data in which the identification information of the delivery company included in the claim application data is set in a predetermined data item First transmitting means for transmitting to
Program to function as.

Images