JP2017204234A - Settlement supporting system, method and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To generally reduce a payment work load of a payment company.SOLUTION: A settlement supporting system comprises: a number specification unit 12 for, when payment data 24 on a monetary claim is transmitted from a payment company, specifying a user number 56 of the payment company according to the payment data 24; a settlement account selection unit 14 for specifying a user number 58 of a supplier company according to the payment data 24 and selecting a settlement actual account number 52 as a settlement account number in the case where an advance payment section 60 shows no use of advance payment while selecting a settlement temporary account number 54 in the case where it shows use of advance payment; and a recording claim data generation unit 16 for, using the user number 56 of the payment company, the user number 58 of the supplier company and the selected settlement account number of the supplier company, generating recording claim data 26 for registering a monetary claim that the supplier company has for the payment company, as an electronically recorded monetary claim.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a payment support system, method, and program for supporting payment between a payment company and a supplier company.

<Accounts receivable settlement>
The payment company purchases goods and services from a number of suppliers, manufactures products for the customers of the payment company, and provides services.
The supplier company is a supplier company, and provides goods such as product parts and materials, services related to construction, etc., and charges the paying company for compensation. The supplier company generates accounts receivable from the paying company, and the paying company generates accounts payable from the supplier company.
The paying company sorts out the bills from a number of supplier companies and pays. This payment is conventionally made by handed cash, bank transfer (internal exchange), or bill transfer. By executing the payment, the accounts receivable and accounts payable are settled, and the accounts receivable become cash or deposits.

A financial institution that has a transaction with a paying company delivers cash by denomination, receives payment data for a number of suppliers, processes account transfers, issues bills, It also provides various services related to payment, such as discounting bills.
A promissory note is a bill of law security that promises future payments. By using the promissory note, the paying company can set the period (site) until the due date. On the other hand, if necessary, the supplier can discount the promissory note at a financial institution and cash it before the due date. The supplier company that received the promissory note can use the note received for its payment.

<Batch factoring>
There is collective factoring as a mechanism (scheme) that realizes rationalization of payment business of paying companies and diversification of fund procurement of supplier companies. In the batch factoring, a factor (broker) that mediates between the supplier company and the payment company is involved. The factoring company, which is an intermediary, collectively purchases accounts receivable held by the supplier company with respect to the paying company and pays the supplier company. Payment to the supplier company is made in advance or due.
With the introduction of collective factoring, the paying company only needs to make a collective payment to the factoring company, and there is no need to make separate payment operations for a large number of suppliers. On the other hand, a supplier company can receive a prepayment from a factoring company as needed.

Patent Document 1 discloses a mechanism for transferring a trade receivable held by a supplier company (supplier company) to a paying company to a factoring company. In this patent document 1, as a data structure for realizing collective factoring with a computer system, a table having a periodic discount date, designation of whether the discount amount is full or partial, and a discount amount for each combination of paying company and delivery company Is disclosed (FIG. 5 of Patent Document 1).
The data structure for each individual bond includes all, a part, and the amount as the presence / absence of payment in advance (FIG. 6 of Patent Document 1). In addition, for each advance payment (discount) by receivables, it manages items such as whether the designation of the claim is an amount or claim, whether the discount category is occasional or periodic, and whether the amount designation is full or partial (patent document) 1 of FIG. 7).
In this patent document 1, when specifying a claim by amount, the total of the discountable amount is calculated from two or more claims, and if the desired discount amount exceeds this possible amount, the claim is specified. A technique is disclosed (FIG. 16 of Patent Document 1, steps E5, E6, etc.).

<Electronic Record Credit Law>
In the payment (settlement) with the promissory note mentioned above, since the bill (securities) is a paper medium, there is a risk of theft or loss of the paper medium itself, and it also costs the preparation, delivery and storage of the bill There is a problem.
In addition, the collective factoring of accounts receivable is the transfer of nominated claims. It must be done, and it takes time and money to transfer. Furthermore, there are problems with nominated claims such as the risk that the same claim will be assigned twice or that the person's defense against the assignee is asserted against the assignee (Non-Patent Document 1, page 9). .
For this reason, collective factoring of nominated loans is expensive and expensive, and therefore, the user base is not expanded as much as bills. On the other hand, there is a limit to the rationalization of settlement affairs when using paper media called promissory notes.

In response to these problems, the introduction of credit transfer by electronic means has been promoted since 2003.
In 2005, the Ministry of Justice, the Financial Services Agency, and the Ministry of Economy, Trade and Industry compiled the “basic way of thinking about electronic claims”. In 2006, the Electronic Credit Law Subcommittee was established in the Legislative Council, public comments were made, and in 2007, a draft outline was presented. The Financial Council also put together ideas on how to manage electronically registered receivables.
In 2007, the “Electronic Record Claim Bill” was submitted to the 166th ordinary Diet session, and was enacted as Law No. 102 of 2007 (Non-Patent Document 1, pages 1 to 2).
Under this summary and legislation, electronically recorded claims under the Electronically Recorded Claims Act are not electronic digitization of nominated claims, but are money with a new type and unique properties that are not the elimination of promissory notes based on the Geneva Unified Bills Convention. It was arranged as a bond (Non-Patent Document 1, page 9).

<Characteristics of electronic receivables>
Designated receivables such as trade receivables are generated only by the agreement of the parties, while electronic record receivables are generated by electronic records in the record book of the electronic receivables recording organization (Articles 15 and 16 of the Electronic Record Receivables Act) ). The transfer of electronically recorded receivables will not take effect unless the transfer is recorded (Article 17).
Regarding the request and record of electronic records, when there are two or more electronic record requests for the same electronic record receivable, the electronic bond recording organization must make electronic records in accordance with the order of the requests (the Act No. 1). Article 8, Paragraph 1). This reduces the risk of double transfer in electronic record receivables.
If there are conflicting claims at the same time, none of the claims will be registered (Article 8, Paragraph 2 of the same law). The “order of billing” is the actual billing date and time, and is not before or after the previous date when recording is requested on the previous date (Article 8, Paragraph 3, Non-Patent Document 1, pages 51 to 52). page).
Electronically recorded receivables have been designed to ensure the safety of transactions by introducing good intentions (Article 19) and cutting off human defenses (Article 20).

After the enforcement of the Electronic Record Loan Law, major financial institutions have established their own electronic bond record institutions, using this self-contained record institution to provide services such as payment by electronic record receivables and advance payments to business partners. Yes.
In 2013, a fully-funded electronic bond recording organization was established by the National Bankers Association, and the service was started under the popular name of Densai Net (registered trademark). Densai Net (registered trademark) is an all-bank participation type and employs an automatic inter-account remittance settlement using an existing inter-bank settlement system.

<Batch factoring of electronically recorded receivables>
Patent Document 2 discloses a batch factoring technique using an electronically recorded bond. Referring to FIGS. 1 and 2 of Patent Document 2, the bank system 4 includes a collective factoring server, a recording institution system, an electronic record bond database, and a temporary recording unit 31.
Therefore, the method described in Patent Document 2 is not a bank participation type but a self-contained recording institution by a single financial institution. Billing data that can be recorded at the same time as the occurrence of electronic record receivables is specially devised as a self-contained type, and the billing data is stored in the temporary recording section until the date of occurrence is the date of occurrence ( Paragraph 0039) of Patent Document 2 discloses a technique for simultaneously generating and transferring a bond by simultaneously recording the generated record data and the transfer record data in an electronic record bond database (the same paragraph 0044).

Regarding the utilization of the self-owned electronic bond recording institution of Patent Document 2, Patent Document 3 describes that a payment company, a supplier company, and an SPC that purchases an electronic record loan all access the same banking system. The inconvenience that the company which can utilize is very limited is described (paragraph 0016 of patent document 3).
In Patent Document 3, a transfer record is provided on behalf of each party in order to make it possible to use a collective payment service using Densai Net (registered trademark) without starting a transaction with a new financial institution. A method of using a substitute agent is disclosed (paragraphs 0037 to 0038 of Patent Document 3). In the method described in Patent Document 3, the payment company and the supplier company need to start a transaction such as opening an account with a new financial institution in order to make a transaction with an agent who temporarily holds an electronic record receivable. (No. 0038, 0047, etc.).

<Use of Densai settlement account number>
Electronically recorded receivables are expected to diversify the financing of suppliers.
Patent Document 4 discloses a technique in which a settlement account number of an electronic record receivable subject to collateral is used as an account number for special settlement that is different from normal in order to realize funding using the electronic record receivable as collateral. Has been. The special settlement account is set with pledge, and if there is a transfer from the paying company to the special settlement account number, the deposit is subject to pledge (see paragraphs 0039 and 3 of Patent Document 4).・ Figure 6).
In the method described in Patent Document 4, the account number for payment is used for special settlement, thereby achieving funding that does not require a transfer record request with a financial institution as the transferee.

  In order to reduce the office burden, for example, Patent Document 5 discloses a technique for devising the numbering of a settlement account number of a supplier company. In the technique described in Patent Document 5, an account number dedicated to the transfer of the supplier company is prepared as a device for the settlement account number. And when there is a transfer to this transfer-dedicated account, by adding the account number of the transfer-dedicated account and depositing into the summary account, it is easy to identify the electronically recorded receivables that are subject to transfer (Paragraphs 0005, 0056).

Japanese Patent Laid-Open No. 2002-140528 (FIGS. 5, 6, etc.) JP 2011-175571 A (paragraph 0043, paragraph 0055, FIG. 1, FIG. 2, etc.) JP-A-2015-041165 (paragraph 0037, paragraph 0038, paragraph 0064, FIG. 6 etc.) JP-A-2015-141598 (paragraph 0028, paragraph 0034, FIG. 6 etc.) JP 2015-143928 (paragraph 0047, paragraph 0056, FIG. 5 etc.)

Osamu Enomoto, Hidetaka Nishina, “Summary of Electronic Record Credit Law: Generation, Transfer, Disappearance, etc. of Claims”, Shoji Homu, June 15, 2014, ISBN 978-4-785-72199-2

The factoring of nominated receivables (trade receivables) as disclosed in Patent Document 1 has the disadvantage that it is not a substitute for promissory bills because it requires costs to identify the receivables and avoid double transfer risks .
In a self-contained recording institution such as disclosed in Patent Document 2, “it is assumed that the same bank is used as a window financial institution, and therefore, companies that can use the collective payment service are extremely limited”. The inconvenience is described in paragraph 0016 of Patent Document 3.

  In the method by the agent disclosed in Patent Document 3, it is not necessary to open an account at a new financial institution in order to receive payment by electronic record receivables or advance payment by factoring, but a contract with the agent is required. However, there are inconveniences that the mechanism is complicated and difficult to understand because there are many players. For example, the agent itself does not make a prepayment, and when making a prepayment, the electronic record receivable itself must be further transferred to a purchase financial institution different from the agent (paragraph 0045 of Patent Document 3).

According to the method described in Patent Document 3, when prepayment is not made, an agent who is not a supplier company, but a creditor of an electronically recorded receivable is used at the time of occurrence. A procedure for assigning a bond must be executed (paragraph 0047 of Patent Document 3).
In this way, even if there is no use of prepayment, it is necessary to generate it on behalf of the agent and transfer it to the supplier company that is the original creditor. There was an inconvenience that the explanation cost was high and the operation cost was high.

In the method described in Patent Document 3, when the supplier company uses prepayment on the due date, the payment company uses the payment account of the purchased financial institution as the destination of the inter-account remittance settlement, and the supplier company When not using pre-payment, the destination is the payment account of the supplier company.
For this reason, unlike the case of the promissory note, the method described in Patent Document 3 has the disadvantage that the supplier company is made aware of whether or not individual advance payment is used.

  According to the method described in Patent Document 4, a supplier company can use an electronically recorded receivable to raise funds by utilizing a special account. However, this is a service limited to financial institutions with which the supplier company has an account. There was an inconvenience that it was difficult to implement in the participation type.

  In the method described in Patent Document 5, a supplier company can specify a payment company or an individual electronic record receivable by a settlement account number. However, a large number of settlement account numbers are set on the Densai Net (registered trademark). There was an inconvenience that a separate paperwork for registration would occur.

  Collective factoring is a mechanism that can both reduce the burden of payment work for paying companies and raise funds for suppliers, as shown in Patent Document 1. None of the methods disclosed in Patent Documents 1 to 5 and Non-Patent Document 1 disclose a method for reducing the burden of payment work and realizing easy-to-use prepayment while using an electronic bond recording organization.

In addition, the above-mentioned document does not disclose any ingenuity for having a supplier company using a promissory note adopt an electronic record receivable.
And although the proposal has been proposed to reduce the administrative burden of only electronically recorded receivables, the above-mentioned document describes the problem of how to reduce the total burden of payment by the paying company and how to solve it. Nothing is disclosed.

  As described above, Patent Documents 1 to 5, Non-Patent Document 1, and the technology combining them all reduce the payment business burden of the paying company and provide a prepaid mechanism that is easy for the supplier company to use. There was an inconvenience that it could not be prepared.

[Object of the Invention] An object of the present invention is to provide a settlement support system, its method, or its program capable of comprehensively reducing the payment office work of a paying company while introducing electronically recorded receivables. .
Another object of the present invention is to prepare a prepayment mechanism that is easy to use for a supplier company, and to improve the participation rate of the supplier company in electronic record receivables.

[Aspects] The inventor of the present invention, in order to reduce the payment administrative burden of the paying company, it is important to improve the participation rate that uses the electronically recorded receivables among the supplier companies with transactions, To that end, the idea came to the idea that all suppliers that are dealing with financial institutions nationwide must be able to participate in settlement with electronically recorded receivables, assuming the relationship between the paying company and the Bank.
And (1). The payment company is simple enough to explain to the supplier company, and (2). The payment company has the same administrative burden as the generation of existing batch factoring and transfer data, 3). For suppliers, it is possible to continue deposits or endorsement transfers to the account of the financial institution currently in use, and (4). did.

In order to achieve the above object, the settlement support system according to the present invention provides a payment company having a transaction with the Bank, a supplier company having a transaction with the Bank or another bank, and the supplier company to the payment company. And a database for managing data relating to monetary receivables, and an electronic record receivable controller for generating record request data for generating the monetary receivables for the supplier company of the paying company as electronic receivables.
The database uses the user number of the paying company used for recording the electronic record receivable with the paying company as a debtor and the electronic record receivable with the supplier company as a creditor. A prepaid classification that specifies the type of prepayment in advance when making a prepayment from the Bank to the supplier company, backed by the user number of the supplier company and the electronically recorded receivables of the supplier company; The settlement account number used by the supplier company to record the electronically recorded receivables, the provisional settlement provisional account number established at the Bank in relation to the prepayment, and the settlement account number established at the Bank or the other bank A settlement account number of the supplier company, and a settlement actual account number into which the settlement amount of the electronic record receivable is actually deposited.
Further, the electronic record receivable controller, when payment data related to the monetary receivable is transmitted from the payment company, a number specifying unit for specifying the user number of the payment company according to the payment data; and the payment data The user number of the supplier company is specified according to the above, and the settlement account number is selected as the settlement account number when the prepayment category is no prepayment use, while the prepayment use is present. Is a settlement account selection section for selecting the settlement provisional account number;
Using the user number of the paying company, the user number of the supplier company, and the settlement account number of the selected supplier company, the supplier company makes the payment company In addition, a recording request data generation unit that generates recording request data for registering a monetary claim held as the electronic record claim is employed.
This solved the above problem.

In the settlement support system of the present invention, the number specifying unit and the settlement account selection unit identify the user numbers of the payment company and the supplier company from the payment data, and the settlement account selection unit is the supplier company with prepaid use. Settlement temporary account number is selected for the electronically recorded receivable, and actual settlement account number is selected for the electronically recorded receivable of the supplier company that does not use prepaid. Then, the record request data generation unit includes the user number of the paying company, the user number of the supplier company, and the settlement account number (settlement temporary account number or settlement actual account number) of the selected supplier company. Is used to generate record request data for registering electronic record receivables.
For this reason, the payment company can use the electronically recorded receivable without managing the user number, and can generate unified payment data that is not affected by whether or not the supplier company uses prepayment. .
Then, the supplier company can use the prepaid electronic record receivable just by opening a temporary settlement temporary account number at the Bank, and the payment destination for the advance payment is the actual settlement account number used normally Therefore, the burden when starting to use the electronic record receivable is small, and therefore the participation rate of the supplier company to the electronic record receivable can be increased.
Payment methods for electronically recorded receivables are reduced by increasing the rate of participation in electronically recorded receivables by supplier companies, unifying payment methods for a large number of supplier companies, and reducing the use of bills using paper media. The data structure can be generated in substantially the same manner, and the management of user numbers, etc., and the office work when there is a mismatch can be eliminated. Thus, this invention can implement | achieve the outstanding payment assistance system of being able to reduce the payment office work burden of a payment company comprehensively.
Furthermore, the present invention is an all-bank participation type electronic receivables institution, and even if it is necessary to open an account at a bank financial institution, the settlement temporary account number is used for recording, while For example, the account of a financial institution (other bank) in the supplier's company can be used as the actual account number for settlement, and the already used account can be used continuously for electronically recorded receivables. it can.
As described above, the present invention only opens a temporary account number that is not actually deposited, and it is not necessary to manage the account of this settlement temporary account number for accounting purposes. It is simple and it is easy for a payment company to explain a new payment method to a large number of suppliers at once, and the burden of introduction is small.
From these points as well, the present invention provides a settlement support system that has a significantly different and superior effect compared to the conventional example that the payment office work burden of the paying company can be reduced comprehensively. be able to.
The same applies to the method and the program.

FIG. 1 is a block diagram illustrating a configuration example of the first embodiment. 2A and 2B are explanatory diagrams showing examples of a settlement actual account and a settlement temporary account. FIG. 3 is a block diagram illustrating a configuration example of hardware resources according to the first embodiment. FIG. 4 is a flowchart showing an example of a settlement account number selection process. FIG. 5 is a flowchart illustrating an example of processing for specifying a settlement provisional account number using a settlement actual account number of payment data. FIG. 6 is an explanatory diagram showing an example of assigning a settlement temporary account number. FIG. 7 is a block diagram illustrating a configuration example of the second and third embodiments. FIG. 8 is an ER diagram showing example items of various masters. FIG. 9 is an explanatory diagram showing an example of items of payment data and record request data. FIG. 10 is an ER diagram showing an example of items in the claim purchase details table and the claim payment details table. FIG. 11 is a flowchart illustrating an example of a prepayment execution process when a fixed amount prepayment is executed periodically. FIG. 12 is a flowchart showing an example of a prepayment execution process when a prepayment of the full amount is executed periodically. FIG. 13 is an explanatory diagram showing an example of payment data of a payment company. FIG. 14 is an explanatory diagram showing an example of the generated record reservation request data corresponding to the payment data shown in FIG. FIG. 15 is an explanatory diagram illustrating an example of a balance and the like when a part of the receivable of the supplier company β is paid in advance to the paying company. FIG. 16 is an explanatory diagram showing the correspondence between payment by a paying company and advance payment and due date of a supplier company. FIG. 17 is an explanatory diagram showing an example of the recorded account receivable statement in which the payment due date in this embodiment is 4/26. FIG. 18 is an explanatory diagram showing an example of the generated record receivable statement in which the payment due date in this embodiment is 5/2. FIG. 19 is an explanatory diagram showing an example of a confirmation of transferable receivables for batch factoring of electronically recorded receivables with respect to paying company A held by supplier company α. FIG. 20 is an explanatory diagram showing an example of an advance payment application confirmation document to the supplier company α as needed. FIG. 21 is an explanatory diagram showing an example of payment by prepayment to the supplier company α. FIG. 22 is an explanatory diagram showing an example of payment by a due date settlement to the supplier company α. FIG. 23 is an explanatory diagram showing an example of a confirmation of transfer receivables for batch factoring of electronically recorded receivables with respect to a paying company owned by supplier company β. FIG. 24 is an explanatory diagram showing an example of payment in advance to the supplier company β. FIG. 25 is an explanatory diagram showing an example of payment in due date settlement to the supplier company β. FIG. 26 is an explanatory diagram showing an example of automatic withdrawal for the payment company A for due date settlement.

The mode for carrying out the present invention includes the first embodiment using the settlement temporary account number 54, the second embodiment that realizes various prepayments based on the configuration of the first embodiment, and the first embodiment and the second embodiment. On the premise of the configuration, the third embodiment uses facsimile data.
Examples 1, 2, and 3 are referred to as “this embodiment”. In the present embodiment, “Bank” refers to a financial institution X that has a transaction with a paying company, and “Other Bank” refers to a financial institution Y in which a deposit account mainly used by some supplier companies has already been opened, Say Z.
The financial institution that introduces the settlement system according to the present embodiment is “the Bank” in the present embodiment.

<Configuration of payment system using temporary settlement account>
Referring to FIG. 1, the settlement support system 101 includes an electronic record bond controller 10 and a database 30.
The database 30 manages data relating to a paying company having a transaction with the Bank, data relating to a supplier company having a transaction with the Bank or another bank, and data relating to monetary claims held by the supplier company with respect to the paying company. To do.
In general, the number of paying companies is one or more orders of magnitude less than the number of suppliers. Although it is “company”, it may be a sole proprietor. Hereinafter, when individually referring to the relationship between the paying company and the supplier company, the paying companies A, B, C, etc., the supplier companies α, β, γ, π, etc., the Bank X, the other banks Y, Z, etc. The symbol is attached.

  The database 30 shown in FIG. 1 includes a user number 56 of a paying company used for recording an electronically recorded receivable with the paying company as a debtor, and a supplier company as a creditor in order to provide a settlement support service. And a user number 58 of the supplier company used for recording the electronic record receivable. The user numbers 56 and 58 may be used as numbers uniquely identifying the paying company and the supplier company in all bank participation type electronic bond recording institutions 82 (for example, Densai Net (registered trademark)). it can.

In addition, the database 30 has a prepayment section 60 for specifying in advance the type of prepayment when making a prepayment from the Bank to the supplier company in support of the electronic record receivable of the supplier company. The prepayment category 60 is an identification category of the contract contents regarding the presence / absence of prepayment, the timing of prepayment, how to determine the prepayment amount, and the like.
In order to support electronic record receivables, JBIC's method of transferring electronic record receivables from suppliers, the method of assigning a special purpose company (SPC) to which JBIC is affiliated, There is a method to set pledges.

Particularly in the present embodiment, the database 30 is a settlement account number 50 used by the supplier company for recording electronically recorded receivables, and a provisional settlement provisional account number 54 established at the Bank in relation to the advance payment. A settlement account number 50 of a supplier company established in the bank or another bank, and a settlement actual account number 52 into which the settlement amount of the electronic record receivable is actually deposited.
The actual settlement account number 52 is an account number of an account that has been used by a supplier company at another bank and has been used for some time. If the supplier company has a transaction with the bank, it can be the account number of the account that has been established before the bank.
Settlement temporary account number 54 is the account number of a new account established by the supplier company that uses prepayment, and was used for requesting the record of transfer of electronically recorded receivables. With regard to the supplier company, the bank can become a window financial institution for all bank participation-type electronic bond recording institutions by opening the temporary settlement account number 54 for the bank. Since the account of the settlement provisional account number 54 is not actually deposited, the management burden of the account does not increase for the accounting of the supplier company.

  The electronic record receivable controller 10 generates record request data 26 for generating a monetary receivable for the supplier company of the paying company as an electronic record receivable. For this purpose, the electronically recorded bond controller 10 includes a number specifying unit 12, a settlement account selecting unit 14, and a recording request data generating unit 16.

The number specifying unit 12 specifies the user number 56 of the payment company according to the payment data 24 when the payment data 24 related to the monetary claim is transmitted from the payment company. For this reason, the user number 56 is not necessary for the payment data 24.
The settlement account selection unit 14 specifies the user number 58 of the supplier company according to the payment data 24, and sets the settlement actual account number 52 as the settlement account number 50 when the prepayment classification 60 is not used for prepayment. On the other hand, the settlement temporary account number 54 is selected when there is a prepaid use. Therefore, the user number 58 of the supplier company is not necessary in the payment data 24.
Among the supplier companies, a prepaid usage destination with a prepaid use in the prepayment category 60 and a destination without a prepaid use are also referred to as no prepaid usage destinations.

  The record request data generation unit 16 includes the user number 56 of the paying company, the user number 58 of the supplier company, and the settlement account number 50 (the settlement actual account number 52 or the settlement temporary account of the selected supplier company). No. 54) is used to generate the record request data 26 for registering the monetary claim held by the supplier company with respect to the paying company as an electronic record claim.

In this way, the number specifying unit 12 specifies the user numbers 56 and 58 from the payment data 24, and the settlement account selecting unit 14 sets the settlement actual account number 52 or settlement as the settlement account number 50 according to the presence / absence of prepaid use. One of the temporary account numbers 54 is selected, and the record request data generation unit 16 adds the numbers required by the electronic bond recording organization 82 such as the user numbers 56 and 58 and the settlement account number 50 to the information of the payment data 24. The recording request data 26 is generated.
For this reason, in this embodiment, the paying company and the supplier company can use the electronic record receivable without complicated management of data items for using the electronic bond recording institution 82.
And the paying company simply adds the minimum necessary items to the data sent to the financial institution for the transfer request used previously and the data sent to the financial institution for bulk factoring. Thus, payment by electronic record receivables can be carried out, and settlement work can be streamlined.
In the present embodiment, a data structure having a settlement temporary account number 54 and a settlement actual account number 52 is adopted as the settlement account number 50 of the supplier company, and both are used properly.
The settlement actual account number 52 can be an account number of a deposit account of another bank that is continuously used by the supplier company for fund management. Prior to the start of using electronically recorded receivables, the bank account number specified by the supplier as the payment recipient for payment to the paying company can be used as the account to which funds for electronically recorded receivables are transferred. .

This settlement provisional account number 54 is established in connection with advance payment. The settlement provisional account number 54 is an account newly established in the Bank by a supplier company that is dealing with another bank in order to use the electronically recorded receivable. By using the settlement provisional account number 54, the Bank can become a contact financial institution of the supplier company when recording electronically recorded receivables such as transfers. By newly assigning the Bank as a financial institution and setting the prepaid amount and the payment destination for the due date payment to the actual payment account number 52, the supplier company can start using electronically recorded receivables. Instead of the account of the settlement provisional account number 54 established in the Bank, it is possible to continue using the account in the other bank that has been used.
In this way, in this embodiment, the supplier company needs a contract for using the electronically recorded receivable, but even after the start of using the electronically recorded receivable, the accounts receivable to the paying company is received. You can start using electronically recorded receivables without changing your account. For this reason, it is possible to reduce the hurdle for starting the use of electronic record receivables and increase the ratio of supplier companies using electronic receivables.
If a large number of supplier companies that used bills have shifted to electronic record receivables, this will reduce the burden of settlement on payment companies. In other words, to make it easier for the supplier company to use the electronically recorded receivables, using the settlement actual account number 52 and the settlement temporary account number 54 separately increases the participation rate of the supplier company to the electronically recorded receivable, Increasing the participation rate of the first-party company will reduce the total settlement burden of the paying company.

  As described above, in this embodiment, a supplier company that has a transaction with another bank has newly established a new bank for the use of electronically recorded receivables, regardless of the mechanism in which prepayment is realized. Instead of an account (settlement provisional account number 54), an account (settlement actual account number 52) established in another bank currently used by the supplier company can be used for prepayment using electronically recorded receivables. .

Referring to FIG. 1 again, the settlement support system 101 is connected to the electronic bond recording organization 82 via the relay system 80. The electronic bond recording institution 82 may be an all-bank participation type electronic bond recording institution 82 connected to a plurality of banks, not a recording institution inside the bank system. For example, Densai Net (registered trademark) is an example of an all-bank participation type electronic bond recording organization 82.
The relay system 80 is a system for connecting a financial institution such as a bank using an electronic record receivable and an electronic receivable recording institution 82, and provides an API such as an occurrence record request and a transfer record request.
When the electronic record receivable controller 10 receives the payment data 24 from the payment company, the electronic record receivable controller 10 refers to the data stored in the database 30 to generate the record request data 26 of the electronic record receivable, and the electronic receivable recording institution via the relay system 80 82 requests the occurrence record.
In order to realize advance payment from the Bank to the supplier company, in accordance with a prior contract, an assignment record for transferring the generated electronic record receivable to the Bank, a transfer record for transferring the electronic record receivable to the SPC associated with the Bank, In addition, procedures to make electronic record receivables a backing asset for advance payment (including collateral lending), such as recording pledges on electronic record receivables for collateral loans, are required.

  In order to use an electronically recorded bond as a backing asset, as with the generation of the record request data 26, a record request for recording assignment and pledge is required. For example, in order to make a record request for transfer to the electronic bond recording organization 82, the electronic record bond controller 10 may individually generate transfer record request data, or the transfer flag 62 may be added to the record request data 26 to be transferred. The transfer record request data 26 may be automatically generated by the relay system 80.

Referring to FIG. 2A, there is a trade / account relationship between the paying company A and the supplier company α as goods and services are delivered. The accounts receivable held by the supplier company α with respect to the paying company A is changed to an electronic record receivable by recording the electronic record receivable. Accounts payable by paying companies to suppliers become electronic record obligations.
Payment company A has a business relationship with Bank X on a daily basis. On the other hand, the supplier company α has a business relationship with another bank Y. In such a case, it is difficult to use the self-owned electronic bond recording organization 82. In this respect, in the present embodiment, a mechanism is easily realized in which a supplier company α that has a transaction with another bank can easily participate, centering on the business relationship between the paying company and the Bank.
The supplier company α sets the account opened in the other bank Y where the transaction is made as a settlement actual account 52 (α1). The supplier company α normally uses the actual settlement account 52 for billing to the paying company. The settlement actual account 52 is, for example, Y bank XX branch XXX number.

In order to transfer the electronic record receivable to the Bank X, the supplier company α makes a request for the transfer record to the electronic receivable recording institution 82 with the Bank serving as the bank financial institution. In this case, the supplier company α must have an account with the Bank X. In this embodiment, the account for recording in the electronic bond recording organization 82 is an account with a settlement provisional account number 54. Schematically, the accounts receivable correspond to the settlement actual account 52, while the electronically recorded receivables correspond to the settlement provisional account 54.
In order to use the electronic record receivable, both the paying company and the Bank X need to register an account number for settlement in the electronic receivable recording institution 82. In the present embodiment, the account number used by the paying company and the Bank for the settlement of the electronic record receivable is also referred to as a settlement account number 50. The settlement account number 50 of the supplier company may be a settlement actual account number 52 or a settlement temporary account number 54.

  Referring to FIG. 2 (B), the electronically recorded receivable was transferred from the supplier company α to the Bank X in order to use it as a prepayment supporting asset. The paying company A bears the electronic record debt, and the Bank X has the electronic record debt. In the electronic bond recording organization 82, the bank's own account number is registered instead of the temporary settlement account number 54 of the supplier company. Along with the transfer of the electronically recorded receivable, there is a receivable / debt relationship between the supplier company α and the Bank X. This receivable / liability will be resolved by prepayment from the Bank to the supplier company α or due date. In the present embodiment, the settlement actual account number 52 is used as a destination for the transfer for eliminating the debt that the Bank X bears on the supplier company α. For this reason, the supplier company α opens an account with the Bank in order to use the electronically recorded receivables. It is deposited into the account number 52. For this reason, when starting to use electronic record receivables, it is necessary to open an account administratively, but the bank account to be managed does not increase, and the account used by supplier company α continues Can be used.

In finance backed by electronic record receivables (accounts receivable), the maximum amount is determined according to the credit rating of the paying company. If the bank is a regional bank based in a different region, the discount (prepayment) of electronic record receivables where the paying company is the electronic record obligor will be discounted by the Bank having a business relationship with the paying company rather than the other bank. It is possible to perform credit (discount) with higher quality information with higher freshness.
In the discount of bills, other banks that do not have a transaction with the paying company discount the bills drawn by the paying company brought in from the supplier company α, but from the viewpoint of credit risk management and optimization of paperwork, The system that discounts all of us at a better level is better.
Administratively, if credit risk management of the paying company is performed, it is possible to realize prepayment for a large number of supplier companies to be delivered to the paying company. In this regard, when discounting promissory notes according to the amount brought in from a supplier company, there are a large number of sources from which bills are drawn. Will have to be done.
With the system of this embodiment, if the system of electronic record receivables is introduced in the relationship between the paying company and the Bank, the financial burden of financial institutions required for credit risk management will be comprehensively reduced and optimized at financial institutions nationwide. Therefore, it is possible to lower the cost for early cashing of accounts receivable and to provide higher quality funding services at lower cost.

<Hardware resources>
Referring to FIG. 3, the settlement system 101 according to the present embodiment includes a computing device 90, a main storage device 92, and an external storage device 94 as hardware resources, and is connected to the billing system 46. In a preferred embodiment, a FAX server 96 is provided.

The arithmetic device 90 is an information processing device such as a CPU, and performs information processing such as data comparison, calculation, and branch processing. The main storage device 92 is a volatile semiconductor memory, and is a storage device that is directly used by the arithmetic device 90. The external storage device 94 is a cache using a semiconductor memory, an SSD, a hard disk, or the like. The external storage device 94 or the like may be an external data center.
The external storage device 94 stores data such as various masters and tables, and also stores program data for executing the settlement support system.
The hardware resources shown in FIG. 3 can be realized by a server device that can execute a relational database management system or a mainframe.

  When the settlement support system program according to the present embodiment is executed by the computing device 90, the computing device 90 shown in FIG. 3 functions as the electronic record bond controller 10 shown in FIG. Various masters and tables can be realized by storage in the external storage device 94 or the main storage device 92.

The billing system 46 manages the bank account information and customer information in real time. As the account information, the transaction details of deposits and withdrawals, balance details, loan details and the like are managed. As customer information, for each CIF number, the presence / absence of a contract such as the company name, representative name, address, telephone number, FAX number, and salary transfer of the customer is managed. When there is a contract for a settlement support service (Densai collective factoring service) according to the present embodiment, it is managed that the account system 46 also has a contract.
The accounting system 46 is connected to Zengin-Net (registered trademark), and can execute transfer (internal exchange) to another bank based on the transfer data.
The settlement support system 101 can realize remittance by transfer to another bank by generating transfer data and sending it to the account system 46 at the time of advance payment or due date.

The FAX server 96 is connected to a paying company's facsimile machine or personal computer via a telephone line or an Internet line. The settlement support system 101 according to the present embodiment uses the FAX server 96 for communication such as generation, transfer, split, pledge setting, prepaid application and confirmation, prepaid transfer schedule notification, due date transfer schedule notification, etc. May be used. Examples of main formats transmitted by facsimile are shown in FIGS. 17 to 27 as examples. If you have a facsimile device, or if you can receive an e-mail with the facsimile data 98 as a PDF, you can use the electronic You can start using the receivables.
The supplier company α does not need to make a new electronic banking (EB) or internet banking contract, and it is not necessary to newly learn how to use EB that is different for each financial institution. Since it can be used, the usage rate of electronic record receivables can be increased. When the usage rate of electronically recorded receivables at supplier company α increases, the usage rate of bills decreases, so that the settlement affairs of the paying company can be unified and the burden of settlement affairs can be reduced overall.

<Payment support method>
In the first embodiment, the electronic record bond controller 10 executes identification of the user numbers 56 and 58 and selection of the settlement account number 50.
Referring to FIG. 4, the electronically recorded bond controller 10 first receives payment data 24 from a payment company online or offline (step S1). Then, the number specifying unit 12 of the electronic record bond controller 10 specifies the user number 56 of the paying company from a predetermined code included in the payment data 24 (step S2). For example, the payment data 24 is preliminarily determined as a payment company name, a settlement account number 50 of the payment company, a contract type code that can specify the payment company, a code such as a telephone number, and a code that can specify the payment company. Identify 24 paying companies.

  The settlement account selection unit 14 first specifies the user number 58 of the supplier company in accordance with the received payment data 24 (step S3). For example, the company name of the supplier company included in the payment data 24, the telephone number, the settlement actual account number 52, and the supplier for identifying the supplier company used by the paying company. Use a code to identify the supplier company.

  When the settlement account selection unit 14 identifies the supplier company, the settlement account selection unit 14 refers to the prepayment category 60 of the supplier company and confirms whether or not the prepayment is used (step S4). The settlement account selection unit 14 selects the settlement account number 54 as the settlement account number 50 when using prepaid (step S5). On the other hand, when the prepayment category 60 indicates no use of prepayment, the settlement actual account number 52 is selected (step S6).

  Subsequently, the record request data generation unit 16 uses the user number 56 of the paying company, the user number 58 of the supplier company, and the settlement account number 50 of the selected supplier company to perform the purchase. Record request data 26 is generated for registering a monetary receivable possessed by the receiving company with respect to the paying company as an electronic record receivable. The record request data 26 may be generated record reservation request data with the date of occurrence as the previous date.

  The number selection unit 12 specifies the user number 56 of the paying company, the settlement account selection unit 14 specifies the user number 58 of the supplier company, and sets the settlement account number 50 according to the presence / absence of prepaid use. In order to make a selection, the record request data generator 16 can generate record request data 26 necessary for generating an electronic record bond from the payment data 24 having the minimum items.

  In addition to the example shown in FIG. 4, the settlement support method includes the steps of the flowcharts of the present embodiment, so that the effects obtained by executing the flowcharts can be obtained.

<Payment support program>
3 and 4, the settlement support program according to the present embodiment implements the information processing shown in FIG. 4 using the hardware resources shown in FIG. 3.
This payment support program causes the computing device 90 of FIG. 3 to specify the user number of the payment company according to the payment data 24 when the payment data 24 relating to the monetary claim is transmitted from the payment company. The number specifying unit 12 (steps S1 and S2) is realized.
Further, the settlement support program causes the computing device 90 to specify the user number 58 of the supplier company in accordance with the payment data 24, and when the prepayment classification 60 is not used as prepayment as the settlement account number 50. While the settlement actual account number 52 is selected, the settlement provisional account number 54 is selected when there is a prepaid use (settlement account selection unit 14, steps S3 to S6).
Then, the settlement support program uses the user number 56 of the paying company, the user number 58 of the supplier company, and the settlement account number 50 of the selected supplier company to obtain the supplier company. Records request data 26 for registering a monetary claim held by the paying company as an electronic record claim (record request data generator 16, step S7).

  In addition to executing the steps shown in FIG. 4, the settlement support program includes the program for executing the steps of the other flowcharts of the present embodiment, and thereby can obtain the effects obtained by executing the flowcharts.

As described above, in the present embodiment, the settlement actual account 52 is used as a remittance destination to the supplier company, and the settlement provisional account 54 is used only for registration with the electronic bond recording institution 82, so that It is possible to encourage suppliers with business to use electronic record receivables widely.
If the business burden when a supplier company shifts to electronic record receivables can be reduced, the use of electronic record receivables by many supplier companies can be expected, and the participation rate of electronic record receivables will be improved. be able to. The higher the participation rate for electronically recorded receivables, the more the payment business burden of the paying company can be reduced.

In this way, all bank participation type Densai Net (registered trademark) can be widely used regardless of the supplier's bank, and the actual settlement account 52 is actually used by the supplier company. You can continue to use your account. Although it is necessary to open a settlement provisional account 54 at the Bank at the start of use of the electronic record receivable, there is no need to manage it for accounting purposes because it is not credited to the settlement provisional account 54. There are no deposit accounts to manage.
As a contribution to the reduction of the payment work burden of the paying company, first, the electronic record receivable controller 10 automatically adds the user numbers 56 and 58 and the settlement provisional account number 54 that can be used with the electronic record receivable. Therefore, the paying company does not need to newly manage the user numbers 56 and 58 used in the electronic bond recording institution 82 in order to use the electronic record receivable, and the same item as the transfer data that has been used in the past. Therefore, the burden of system development at the start of use of electronic record receivables is small, and the burden of paperwork during operation is also small.
Second, with a system in which a supplier company that uses prepayment transfers electronically recorded receivables to the Bank or an SPC related to the Bank, remittance between accounts with settlement at the maturity date, whether or not there is an individual advance Since the destination does not change in the bank or bank-related SPC accounts, the burden of settlement will not increase depending on the presence of advance payment.
Third, due to the above-mentioned effects, it is possible to expect an increase in the participation rate of the supplier's electronically recorded receivables, which reduces the usage rate of the hand, accompanying the issuance of paper media called bills, discounts and transfers Comprehensive payment administrative burden by reducing the administrative burden of changing payment destinations, unifying payment methods for many suppliers, and reducing administrative burdens such as drafting bills and dealing with discounts Can be reduced.
Since the settlement temporary account number 54 is an account number that is not actually a destination of payment, unlike the transfer-dedicated account of Patent Document 5, it increases the accounting work burden for both the payment company and the supplier company. I will not let you.
The settlement provisional account number 54 is an account number for specifying the account of the supplier company. However, it cannot be used unless it is a financial institution having a loan transaction with the supplier company like the special account of Patent Document 4. It is not a number, but there is no business with a supplier company, and a wide range of supplier companies with transactions with financial institutions (other banks) that exist throughout the country can be targeted.

<Settlement actual account number 52 as search key>
Referring back to FIG. 1, the database 30 includes a supplier company master 34. The supplier company master 34 stores the user number 58 of the supplier company, the settlement actual account number 52, and the settlement provisional account number 54 in association with each other. The supplier company master 34 preferably has a user number 58 or the like for each supplier company, with a supplier code that uniquely identifies the supplier as a main key. Even if the supplier company has a transaction with a plurality of paying companies A and B, the supplier company master 34 may have a unique configuration. On the other hand, the prepayment classification 60 shown in FIG. 1 may be set for each supplier company or for each contract between the paying company and the supplier company.

  Referring to FIG. 5, when receiving the payment data 24 from the paying company, the number specifying unit 12 specifies the settlement actual account number 52 for each supplier company in the payment data 24 (step S11). Subsequently, the number specifying unit 12 refers to the supplier company master 34 using the settlement actual account number 52 as a search key (step S12), and identifies the supplier company having the settlement actual account number 52 (step S13). ). Since the settlement actual account number 52 is a number unique to the supplier company, if the settlement actual account number 52 can be identified, the supplier company can be identified uniquely.

  Further, the number specifying unit 12 specifies the settlement provisional account number 54 of the specified supplier company (step S13). If the supplier company can be specified, the settlement provisional account number 54 of the supplier company is determined in advance. Therefore, by referring to the supplier company master 34, the only provisional account number for the supplier company can be obtained. 54 can be identified.

In order for the number specifying unit 12 to execute the information processing shown in FIG. 5, the paying company includes the settlement actual account number 52 for each supplier company in the payment data 24, so that the record request data of the electronically recorded receivable is recorded. Since the settlement provisional account number 54 necessary for generating the data 26 can be automatically specified, the generation burden of the payment data 24 of the payment company can be reduced, and as a result, the office work burden of the payment company can be reduced.
In particular, the fact that the settlement actual account number 52 is included in the payment data 24 is the same as the requirement that the payment account includes the transfer account number in the transfer data transmitted to the bank, so the payment company starts using the electronically recorded receivables. Can reduce the burden of system development.
When the actual account number 52 is used, the company name, department name and definition are unclear and confusing, and easy to understand and easy to check. In this way, by using the settlement actual account number 52, it is possible to effectively suppress an increase in the burden of paperwork due to the occurrence of inconsistency.

<Generation of transfer data>
Referring to FIG. 1 again, the electronic record bond controller 10 includes a transfer data generation unit 18. The transfer data generation unit 18 calculates a prepayment amount according to a calculation method predetermined in the prepayment category 60 in relation to an electronically-recorded receivable generated by using the supplier company with the prepayment category 60 as a creditor. Transfer data is generated using the transfer actual account number 52 as the transfer actual account number 52 as the transfer amount.

  In the first embodiment, the bank or the SPC related to the bank makes a prepayment using the electronic record receivable held by the supplier company for the paying company as a backing asset. The method of using electronic record receivables as supporting assets is the transfer of electronic record receivables to the Bank as disclosed in Example 2, the transfer to the Bank-related SPC, and the pledge of the Bank as a pledger / supplier company. For example, setting pledge rights for electronic receivables. If the Bank is a community-based financial institution, the system of transfer by the Bank itself is the simplest and easy to introduce.

When making a prepayment by the bank or the bank-related SPC, the transfer data generation unit 18 calculates a prepayment amount by a calculation method predetermined in the prepayment section 60, and uses the prepayment amount as a transfer amount. Prepayment amount, for example, in accordance with prepayment category 60 indicating the details of the prior contract, with respect to the total amount of electronic record receivables transferred, within the face value of electronic record receivables, to a predetermined fixed amount, the face value of electronic record receivables For example, a certain amount of money.
Then, the transfer data generation unit 18 uses the payment company account number 52 of the supplier company as the transfer destination account number as the transfer destination of the prepayment amount. As a result, in the electronic bond recording institution 82, payment is made to the settlement actual account number 52 that the supplier company uses on a daily basis instead of the settlement provisional account number 54 of the supplier company used at the time of occurrence. It can be. When the supplier company has a transaction with another bank, the settlement actual account is Y bank XX branch XXX number or the like. If the supplier company has a transaction with the Bank, the account number established at the Bank for daily use by the supplier company may be used.

  As described above, in the present embodiment, in generating the transfer data to the supplier company, the transfer destination account number is set to the settlement actual account number 52, and therefore, the supplier company is used for other accounting. The account can be used as it is, and there is no need to increase another bank account to be managed in order to use the electronic record receivable. By providing this convenience to the supplier company, it is possible to increase the participation rate for the electronically recorded receivables and to reduce the settlement work burden of the paying company by improving the participation rate.

  Furthermore, in this embodiment, the payment company only needs to generate the payment data 24 with the minimum number of items and use the electronically recorded receivable by simply adding the payment date to the transfer data that has been generated conventionally. It is possible to reduce the administrative burden for payment that the payment company has to make every month in accordance with the business activities.

In this embodiment, the Bank, which has a transaction with the paying company, introduces electronically recorded receivables for the purpose of reducing the administrative burden related to the accounting of the paying company. Funding for each supplier company is secondary and incidental.
It is customary that the Bank has already conducted financial analysis and community-based information exchange regarding the paying company prior to the introduction of the electronically recorded receivables, and without any additional information collected by the Bank, Prepayments can be made for a large number of vendor companies.
It is customary that the number of supplier companies is two to three digits compared to one of the paying companies, and since the locations are distributed throughout Japan, this led to transactions with paying companies. It is more reasonable for the financial industry as a whole to introduce electronic record loans.
In other words, this embodiment introduces electronically-recorded receivables with financial institutions that have transactions with paying companies as Company X, and within the scope of credit risk for paying companies acquired as part of Company X's community-based business. , Trying to make a prepayment backed by electronic record receivables to a large number of suppliers. In this regard, the conventional promissory note differs from the mechanism in which financial institutions with business with suppliers provide funding before the due date through discounts, but financial institutions with transactions with paying companies as in this embodiment. If an institution provides early funding to a supplier, the amount of information it can collect for credit risk management is larger, and there is no duplication of credit risk management across the financial industry, which is reasonable.
By introducing the electronically recorded receivable according to the present embodiment instead of the paper medium of the promissory note, the financial industry as a whole can provide the funding of the receivable receivable, which is the most rational in nature, at a low cost.
And even if it is going to realize collective factoring using all-bank participation type electronic bond recording institution 82, a single financial institution deals with all paying companies and suppliers, or patents It was necessary to become a financial institution for the electronic bond recording institution 82 by a contract with a representative in Document 3. In this respect, this embodiment is a supplier company that does not have a transaction, and only urges the prepaid customer to open a settlement provisional account number 54 that is not actually deposited. The bank account of the other bank can be used continuously with the settlement actual account number 52 without any change, and the Bank has a system with less administrative burden for both of the suppliers.
In addition, when the paying company uses the electronic record receivable structure for the supplier company, the time required for the explanation is small because there are few questions from the supplier company in the structure where the deposit account is currently used. And the amount of documents can be reduced.

  In this way, if it is possible to propose an electronic record receivable mechanism that is easy for a supplier company to introduce, the ratio of supplier companies that require the use of bills can be reduced to the maximum. It will be easier to build a system for unifying payment methods to other companies. If the bill usage ratio can be reduced, payment by electronic record receivable and payment by transfer will be made, but in the preferred example of embodiment 1, the actual account number 52 is set in the payment data 24 of the electronic record receivable. It can be used as a key for specifying the company, and can be dealt with by changing the extent to which a maturity date in the case of an electronically recorded bond is added to the data item of the transfer data for transfer. Further, the user number 58 for each supplier company necessary for using the all-bank participation type electronic bond recording institution 82 is also managed by the system of the present embodiment and does not need to be included in the payment data 24. The use of electronically recorded receivables using the settlement support system according to the present embodiment can reduce not only the payment related to electronically recorded receivables but also all the payment work of the paying company, and rationalize the entire payment work. .

<Numbering of settlement temporary account number 54>
Referring to FIG. 1 again, the electronic record bond controller 10 includes a pre-registration unit 19. The pre-registration unit 19 registers data relating to the paying company and the supplier company in the database 30 when contracting to use the electronically recorded receivable between the paying company and the supplier company.
When the pre-registration unit 19 registers the payment provisional account number 54 in the database 30, the pre-registration unit 19 assigns a unique account number to the supplier company issued for each supplier company. It may be pre-registered as the account number 54A. This is the number for each supplier company.

  Further, when the pre-registration unit 19 registers the settlement provisional account number 54 in the database 30, the one-to-one combination of the payment company and the supplier company that is issued for each combination of the payment company and the supplier company. Alternatively, a unique account number may be pre-registered as a settlement provisional account number 54B of the supplier company. This is the number for each contract between the paying company and the supplier company.

Referring to FIG. 6, the paying company A has a paying company code of 500, the branch number of the Bank serving as the window of the paying company is 300, and has a transaction with a supplier company α, β, γ, π. .
The paying company B has a paying company code of 501 and a branch number of our bank that serves as the payment company's window is 301, and has a transaction with a supplier company α, δ, ε.
The paying company C has a paying company code of 500, a branch number of the Bank serving as a payment company's window is 302, and has a transaction with a supplier company β, δ, θ, λ.
The numerical values shown in FIG. 6 and the like are simplified for explanation, and are different from the number of digits such as an actual account number, for example.

When issuing a settlement provisional account number 54 for each supplier company, in the example shown in FIG. 6, it is preferable to use a combination of the store number of the bank that serves as the payment company's window and a unique number.
In the case where the paying company collects the intentions of the supplier company and prompts the customer to switch to electronic record receivables, the branch in charge of the bank of the paying company serves as a consultation / contract window. In this case, when the settlement provisional account number 54A is issued, regardless of the address of the head office of the supplier company and the like, the administrative burden is small if the account is a branch office serving as the payment company. In the example shown in FIG. 6, the payment provisional account number 54A for the payment company A to the supplier companies α, β, γ, π is a serial number from the store numbers 300 and 6001 of the bank that serves as the window for the payment company. It was. In the branch of our bank number 300, the settlement provisional account number 54 can be issued with only a little additional work in the process of opening a normal savings account.
In the paying company B, the settlement temporary account number 54A (300 6001) has already been issued for the supplier company α, so that it is not a new number but an existing number. A new number is issued for the supplier company δ.
On the other hand, in the issue of the supplier company for the paying company C, the supplier companies β and δ are assumed to be existing numbers, and new numbers are issued to the supplier companies θ and λ.

  When the settlement temporary account number 54A is assigned to each supplier company, the supplier company can be uniquely identified from the settlement temporary account number 54A. Also, since Densai Net usage fees are in units of account numbers, if a new payment provisional account number 54A is assigned for each supplier company, the fee for this service will be set independently, Discounts can be realized.

In the example in which the payment provisional account number 54B of the supplier company is issued for each contract between the paying company and the supplier company, a combination of a payment company code for identifying the paying company and a serial number may be used.
For example, in the example shown in FIG. 6, the supplier company α, β, γ, π to the payment company A is a combination of the payment company code 500 and serial number, and the supplier company α is 500 001, The supplier company β is numbered 500 002. In this example, since the settlement temporary account number 54B is different for each contract, in the contract between the paying company B and the supplier company α, the supplier company α is given a number 501 001 separately from the 500 001 number. It is done.

As described above, when the settlement provisional account number 54B of the supplier company is set for each contract between the paying company and the supplier company, the counterparty of the contract can be uniquely identified by the settlement provisional account number 54B. For this reason, when the settlement provisional account number 54B is added to the transfer data, the counterparty of the transaction can be uniquely identified by the settlement provisional account number 54B, thereby reducing the accounting processing burden of each company.
In particular, even if the business name of the counterpart company is not displayed on the form for displaying the list of electronically recorded receivables or the layout of the printed output, if the settlement temporary account number 54B is present, both counterparts are specified. be able to.

By issuing this temporary settlement account number 54 separately from the actual settlement account number 52, as shown in FIG. There may be 82 window financial institutions.
Further, in the present embodiment, as shown in FIG. 6, even when there is a transaction with the bank X such as a supplier company γ, π, θ, Information processing in X can be unified.

  As described above, according to the first embodiment, by using the settlement temporary account number 54 and the settlement actual account number 52, it is possible to improve the participation rate of the supplier company to the electronic record reconstruction. This makes it possible to effectively unify the payment method to the supplier company, thereby reducing the office work burden of the paying company. In addition, since it is possible to undertake operations such as the generation of electronically recorded receivables using only simple payment data 24 at the same level as the transfer data, it is possible to reduce the total payment burden of the paying company. It becomes easy to deal with the rename and address change of the other company.

In the second embodiment, an example is disclosed in which, for an electronically recorded receivable of a prepaid customer, the Bank transfers the entire amount from the supplier company immediately after the occurrence, and the bank makes a prepayment or transfer to the supplier company on the due date. <Full transfer and voluntary prepayment of all users>
Referring to FIG. 7, as in the first embodiment, the settlement support system 102 in the second and third embodiments includes an electronic record bond controller 10 and a database 30.
As in the first embodiment, the electronic record bond controller 10 includes a number specifying unit 12, a settlement account selection unit 14, a recording request data generation unit 16, and a pre-registration unit 19.

Particularly in the second embodiment, the electronic record bond controller 10 includes a transfer control unit 20 and a prepayment data management unit 22.
When the transfer control unit 20 uses a prepayment for each monetary claim in the payment data 24 in the prepayment category 60, the bank will make all and all of the electronic record receivables generated from the record request data 26 of the monetary claim. Is turned on. In the second embodiment, the settlement support system does not generate the transfer record request data, but only sets the transfer flag 62 in the record request data 26, and the transfer record request data is generated by another system. In the example shown in FIG. 7, the relay system 80 refers to the transfer flag 62 of the recording request data 26, and when the transfer flag 62 is on, the transfer record data of the electronic record receivable recorded by the recording request data 26 is displayed. Generate.

  The prepayment data management unit 22 controls the prepayment to the supplier company at any time or periodically within the range of the balance of the amount of receivables that the bank has transferred the entire amount according to the transfer flag 62 being turned on. The prepayment data management unit 22 manages the contents of the electronically recorded receivables purchased by the transfer, executes prepayment to the supplier company within the range of the purchased electronically recorded receivables, and remits the balance not paid in advance on the due date. To do.

Prepayment modes managed by the prepayment data management unit 22 include a classification of whether to apply for prepayment at any time or regular (automatic prepayment), designation of an execution date in the case of regular, and amount of prepayment in the case of regular And the amount when the prepayment is a fixed amount is managed. Prepayment and prepayment for designation of receivable is a designation for prepaid the entire amount of electronically recorded receivables. Prepayment is specified in advance. The amount specified in advance is within the face value of the electronically recorded receivable.
At any time, the Bank receives a prepaid application at any time with the amount in the balance of the electronically recorded receivable transferred from the supplier company, and the applied amount is the prepaid amount.
The prepayment category 60 is a category in which these prepayment modes, a designated date and a designated amount are recorded in advance.

  For the electronically recorded receivables of a supplier company with a prepaid use contract, the transfer flag 62 is turned on when the record request data 26 is generated, and the bank purchases the entire amount of the electronically recorded receivable instead of a partial amount, and the prepaid data management unit 22 executes prepayment according to a prepaid mode (prepayment category 60) separately determined in advance with the supplier company.

Since the control target of the transfer flag 62 is not the partial (divided) portion of the electronic record receivable, but the full amount, the paying company must transfer the inter-account remittance as the electronic record creditor by purchasing the entire amount of the electronic record receivable. There is no need to make multiple transfers according to the split of one electronically recorded receivable or to change the remittance destination by discounting the due date. In other words, by adopting the full transfer, it is possible to avoid an increase in the office work burden of the paying company of the paying company due to the execution of the advance payment.
In addition, even though the total amount is transferred, the amount of advance payment to the supplier company is arbitrary, and it is possible for the supplier company to make a pre-paid amount that can be determined in advance or applied at any time. Can provide easy to use prepayment. Further, in the second embodiment, there is no player such as an agent or SPC, there is a transaction with a paying company, and a financial institution (the bank) who knows the paying company purchases electronically recorded receivables and makes a prepayment to the supplier company. Therefore, a stable prepayment can be executed by credit risk management based on information that is not complicated in the scheme and has high community-based information.
And since the contents of the payment affairs of the paying company do not change depending on whether or not there is an individual advance payment, the paying company is not aware of the amount and timing of the individual use of the advance payment. Accordingly, whether or not to use prepayment is registered with the paying company or the like, but it is not known to the paying company whether or not the supplier company actually uses the prepayment. For this reason, it is possible to provide a new prepayment method that is easy to use even for a supplier company that does not want the paying company to know about changes in the cash flow situation.
In this way, the payment company can use the flexible prepayment according to the needs of the supplier company without knowing whether the individual prepayment is used or not. Since the prepayment amount is transferred to the account, it is possible to provide a settlement method that is more convenient for the supplier company than the promissory note.
With these, if the participation rate of the electronic company's record receivables of the supplier company can be increased and the participation rate of the supplier company can be increased, the increase in the participation rate can further reduce the payment administrative burden of the paying company. it can.

<Data structure>
An example of a data structure in the second embodiment will be disclosed. The settlement support system 102 may be realized as a part of the account system 46 (a host computer of a financial institution) or may be realized by a server that executes a database management system. In order to match the customer information of the accounting system 46 and the master information of the server even when implemented on the server, the data registered in the master is first input to the accounting system 46 and automatically transmitted to the server side. However, conversely, the information registered on the server side may be transmitted to the billing system 46.
Even when the settlement support system 102 is realized by a server, the details and balance of the purchased receivables of the Bank may be managed in alignment with the account system 46 in the accounting processing of the Bank. The matching of data is not matching at the transaction level, but may be a mechanism in which items of the account system 46 and the server do not logically disagree on a daily basis, for example.

  Referring to FIG. 7 again, when the settlement support system 102 is configured by a server, as a master of the database 30, a payment company master 32, a supplier company master 34, a payment company contract master 36, and a supplier company contract. And a master 38.

  Particularly in the second embodiment, the supplier contract master 38 has a prepayment category 60 of the supplier company for each supplier company and for each paying company. In this example, whether or not prepayment is used and the prepayment method are determined not for each supplier company but for each contract between the paying company and the supplier company.

In the second embodiment, the database 30 includes a receivable purchase details table 40 and a receivable payment details table 42 as tables for managing the details of receivables and advance payments.
In particular, the receivable purchase details table 40 manages the contents of electronically recorded receivables transferred from a supplier company with prepaid use in response to the transfer flag 62 being turned on.

Referring to FIG. 8, for each paying company identified by the paying company ID, the paying company master 32 uses the paying company name, the collective factoring and the usage classification of the electronic record receivable, the settlement account number 50 established by the Bank, and the FAX number. Densai Net (registered trademark) has a Densai user number 56 for specifying the paying company, a maximum amount for accepting receivables, and a maximum amount for discount.
The credit receivable maximum amount is an extreme amount related to the total amount of electronic record receivables that the Bank can transfer among electronic record receivables whose paying company is an electronic record obligor. The discount extreme amount is an extreme amount that defines the upper limit of one electronic record receivable. These are determined according to the results of credit risk management according to the information obtained from the paying company.
The payment company master 32 has other bibliographic items such as address, telephone number, application for passbook printing with inter-account remittance, and various information required by the electronic record receivable recording organization.

The supplier company master 34 stores, for each supplier company identified by the supplier company ID, a supplier company name, a settlement actual account number 52, a settlement temporary account number 54, and a FAX number as shown in FIG. Densai user number 58 and the like.
The supplier company master 34 has other bibliographic items such as address, telephone number, application for bankbook printing with inter-account remittance, and various information required by the electronic record receivable recording organization.

  The payment company contract master 36 includes, for each contract of the payment support service (Densai lump factoring service) between the payment company and the Bank, a contract ID for uniquely identifying the contract on the server, and an accounting system 46 (host ), A contract number that uniquely identifies the contract, a CIF number that uniquely identifies the customer in the accounting system 46, a payment company ID that uniquely identifies the paying company in the settlement support system 102, and payment data 24. A data transmission code that uniquely identifies the contract with the paying company.

The supplier company contract master 38 is a master generated for each contract between the paying company and the supplier company, and uses both the paying company ID and the supplier company ID as main keys. The paying company has a supplier code that uniquely identifies the supplier and a prepayment category 60.
In the example of the supplier company contract master 38 shown in FIG. 8, the advance payment category 60 includes the type of advance payment (anytime, periodic, due date), the periodic advance payment method (full amount, specified amount), and the payment date category (transfer date, specified date). Day), prepaid designated amount and other items.

The type of advance payment is a type in which advance payment is made after waiting for an application from a supplier company. In the example shown in FIG. 16, this is supplier company α.
The type of prepayment type is a type in which prepayment is made on a predetermined fixed date. For example, in the example shown in FIG. 16, the specified date is the transfer date, and the supplier company β whose fixed amount (1,000,000 yen) is set for each claim. Suppose that the specified date is the transfer date and the supplier's face value is full.
There are various ways to use the prepayment date. For example, the prepayment type does not use prepayment. In the example shown in FIG. 16, the supplier company π is a supplier company π that does not use prepayment and is settled by payment between accounts directly from the paying company to the supplier company on the due date.

Referring to FIG. 9, the payment data 24 sent to the bank by the payment company includes various contract numbers (may be data transmission codes) and the payment account number 50 of the payment company in the header, for each supplier company. The actual account number 52 of the supplier company, the date of occurrence of the electronically recorded receivable, the maturity date, and the amount of occurrence are included. Occurrence date and maturity date may be included in the header.
The payment data 24 may include a company name of a paying company or a supplier company for a human check by a human.

The record request data 26 is data transmitted from the Bank to the electronic bond recording institution 82 via the relay system 80, and the user numbers 56 and 58 for identifying the paying company and the supplier company, the date of occurrence, and the expiration date. , A settlement account number 50 of the paying company, a provisional account number 54 of the supplier company, a transfer flag 62, and the like.
The company name of the paying company, etc. required for the electronic record receivable, and the name of the financial institution of each account number may be included in the record request data 26 transmitted from the Bank to the relay system 80, or the user at the relay system 80 The recording user master 84 may be added from the numbers 56, 58, etc.

  Referring to FIG. 10, a claim purchase details table 40 is a description of electronically recorded claims purchased by a bank from a supplier company, and uses a supplier company ID and a claim ID as main keys. The total of the supplier code, the paying company ID, the electronic record receivable number used to identify the receivable at the electronic receivable recording institution 82, the date of occurrence, the maturity date, the initial face value of the receivable, and the advance payment amount. With a paid amount of 64. When the paid amount 64 is subtracted from the nominal amount of the receivable, the balance of the receivable is obtained. The paid amount 64 may include an amount such as a fee required for executing the advance payment.

  The receivable payment details table 42 is the details of the prepaid payment for each prepaid execution of each receivable. The main key is the supplier company ID, the receivable ID, and the payment ID that represents the number of prepaid times. This receivable payment details table 42 has a supplier code, a paying company ID, an electronically recorded receivable number, a payment category (due date, advance payment), a advance payment type (as needed, periodic), a payment date, a maturity date, a payment amount, and a fee. . The sum of the payment amount and the fee is the advance payment amount, and the total of the advance payment amount is the paid amount 64. The advance payment type is a part of the advance payment category 60.

<Prepay for regular and fixed amount (specified amount)>
In Example 2, the Bank purchases the entire amount of electronically recorded receivables and provides early funding in response to a prepaid application for all or part of the amount.
The disclosure of the prepaid mode in the present embodiment is a disclosure of technology that is an example of information processing within a technically compatible content that can be technically calculated, and is a current state of social system. Or content that cannot be realized due to changes.
For this reason, the content disclosed in the present embodiment and examples is not an explanation of the service content scheduled to be provided by the patent applicant. The interest rate and the numerical value of the fee are also examples of disclosure of information processing contents, and are not explanations of actual services.
In the second embodiment, first, an information processing method for executing a type of advance payment in which the advance payment amount is designated in advance in the advance payment category 60 will be described.
Prepayment for which the amount is specified in advance is divided into a type (Fig. 15) in which a certain amount for each receivable is a prepaid amount for each receivable, and a receivable with a balance on the monthly designated date. There are types that use a fixed amount as a prepaid amount. A predetermined fixed amount may be used as the prepayment amount for the total balance of all receivables on the monthly designated date (for example, FIG. 11).
In the case of a fixed amount, if the balance of the receivable is lower than the fixed amount for both types, the balance of the receivable is set as the prepayment amount.

If the designated date of prepayment is the transfer date, for each electronic record receivable, the face value specified for each electronic record receivable or the face value of the electronic record receivable does not reach a certain amount Let the amount be the prepayment amount.
In the example of the supplier company β shown in FIGS. 15, 23 and 24, on the transfer date of the receivable (2016/4/15), a predetermined amount (1,000,000 yen) is transferred as a prepaid amount for each receivable do. In the example shown in FIG. 15 and the like, there are two cases with the April / 26 date and the 5/2 date as the 4/15 occurrence date, so a predetermined amount of 1 million yen is prepaid from each. Since there are two receivables, the total advance payment is 2 million yen. When the prepayment is executed, the prepayment data management unit 22 updates the paid amount 64 of each bond.
As shown in FIG. 15 and the like, when the designated date is the transfer date, the advance payment is executed for each bond only once.
If the specified date of prepayment is a specific date such as the 25th of every month, a system that allocates a fixed amount to each prepayment for all receivables that have a balance on a specific date, Prepaid. Further, even if the designated date is a specific date, the advance payment for each bond may be made only once.

In the case of fixed prepayment, the balance of all the receivables that have a balance on a specific date may be summed to make a prepayable amount on the reference date, and a certain amount of payment determined in advance within that range may be used. In this case, the information processing is almost the same as the prepayment for specifying the amount by application at any time.
Referring to FIG. 11, when the prepayment data management unit 22 handles a regular and fixed amount prepayment method as the prepayment section 60, the information processing starts on the day toward the scheduled prepayment date. In the example shown in FIG. 11, the date for the prepaid scheduled date is two business days before the prepaid date. If the 10th day of each month is a prepaid designated date, the prepaid scheduled date is 2 business days before that date. If necessary, an application up to three business days in advance is accepted, and information processing similar to FIG. 11 is started two business days in advance.

  The prepayment data management unit 22 refers to the supplier contract master 38 (step S22), and extracts a supplier company whose prepayment scheduled date is a scheduled date (step S23). Specifically, out of the supplier companies that have data in the supplier contract master 38, the two days after the prepaid scheduled date, unsearched, and the prepaid category 60 is a fixed date on a regular designated date. To extract.

  Subsequently, the prepayment data management unit 22 refers to the receivable purchase details table 40 (step S24), and specifies the electronic record receivable group before the maturity date among the electronic record receivables transferred from the supplier company. (Step S25). Subsequently, the balance of each electronic record receivable is assigned to the advance payment amount from the specified electronic record receivable group until reaching the fixed amount in the order of close maturity (step S26). If the electronically recorded bond group is not found, the process returns to step S22 to search for the next supplier company.

  When the prepayment amount is calculated, transfer data is generated in which the amount corresponding to the total amount of the prepayment amount assigned is the transfer amount, the scheduled scheduled date is the transfer date, and the settlement actual account is the transfer destination account (step S27). ). Actually, various fees are reduced from the advance payment amount, and the reduced amount is used as the transfer amount.

Further, the paid amount 64 of the claim purchase details table 40 is updated with the amount of the prepayment date on the transfer date (step S28).
When transfer data is generated in step S27 and the paid amount 64 is updated in step S28, the prepayment control is also completed for the supplier company, so the process returns to the search for the next supplier company (step S27). S29).

When the prepayment category 60 is a fixed amount on the specified date of the month, the maximum value of the monthly prepayment amount is the fixed amount by the calculation method shown in FIG. On the other hand, when the advance payment category 60 is a fixed amount on the date of transfer, the number increases in accordance with the number of electronic record receivables, but the number of advance payments for each electronic record receivable is 1. If the specified date is a fixed date for each claim and the specified date is a fixed amount for each claim, the prepaid amount is the sum of the fixed amounts for all claims that have a balance on the specified date of each month within the range where the claim has a balance.
According to these prepayment controls, it is possible to automatically generate transfer data for prepayment by simply predetermining the details of prepayment and registering it in the prepayment category 60. Can be stabilized. For this reason, electronically recorded receivables are disseminated as an alternative to promissory notes, and the participation rate of suppliers' electronically recorded receivables is improved, and this increase in the participation rate reduces the burden of payment work for paying companies in a comprehensive manner. be able to.

<Prepayment of regular and full amount (designated receivable)>
Referring to FIG. 12, the prepayment data management unit 22 starts processing from the reception of the payment data 24 when handling the prepayment method for the entire amount of all receivables as the prepayment category 60.
First, when the payment data 24 is received (step S31), a supplier company whose prepayment category 60 is all receivables and is full is extracted from the payment data 24 (step S32).

When there is a supplier company (step S33), the entire amount of the electronic record receivable of the extracted supplier company is assigned to the advance payment amount toward the date of occurrence of the electronic record receivable specified in the payment data 24 (step S34). .
The prepayment data management unit 22 sets the amount corresponding to the allocated prepayment amount as the transfer amount, sets the transfer date of the electronically recorded receivable to be recorded when the transfer flag 62 is turned on, as the transfer date. The transfer data with the payment real account as the transfer destination is generated (step S35).
Actually, the amount obtained by subtracting the fee required for prepayment from the total amount is the transfer amount. This transfer data is transmitted to the billing system 46.
The prepayment data management unit 22 records the paid amount 64 of the electronically recorded receivable as the total amount on the receivable purchase details table 40 as of the date of transfer (step S36).

In the example shown in FIG. 12, since the preparation for generating the transfer data for the advance payment is started from the time when the payment data 24 is received, even if the transfer date of the electronic record receivable is the same date as the occurrence date of the electronic record receivable , A prepaid transfer can be executed on the date of transfer.
The prepayment data management unit 22 can provide a service for stabilizing the cash flow of the supplier company in order to generate the transfer data, and provide simplified management of the receivables of the supplier company by automating the prepayment. Can do. Also, by realizing full payment in advance on the date of transfer, it is possible to cash as early as the promissory note discounted on the date of bill draft and increase the number of suppliers that join electronically recorded receivables. it can.
In particular, since it is a discount by a bank that has a transaction with a paying company, the examination time can be shortened compared with a discount by another bank that does not have a transaction with the paying company, and when the payment data 24 is received, Since preparations for execution (generation of transfer data) can be made, the transfer date can be completed on the transfer date, with the date of occurrence of the electronically recorded receivable as the transfer date.
As a result, it is possible to improve the participation rate of the supplier company in the electronically recorded receivables. By improving the participation rate for the electronic record receivable, it is possible to unify the payment method of the paying company, and to reduce the payment office work burden of the paying company comprehensively.

<Prepay at any time (prepayment date and amount specified)>
Next, an example of a prepayment process according to an application at any time will be described. The application for prepayment shall be made by the supplier company α applying to the bank by specifying the prepayment date and the prepayment amount three business days in advance.
Referring to FIG. 11 again, when it becomes two business days of the prepayment date for which the application is received at any time (step S21), the supplier company of the continual application having two business days as the prepaid scheduled date is extracted (from step S22). The same kind of processing as S23).

  Subsequently, all the electronic record receivable groups that are generated by the supplier company as electronic record creditors and purchased by the Bank are extracted (steps S24 and S25). Subsequently, the electronically recorded receivables are arranged in the order of the prepaid due date, and the balance of the electronically recorded receivable is allocated to the prepaid amount until the prepaid amount that has been applied for at any time near the prepaid due date (step S26).

  When the prepayment amount received is reached, transfer data is generated with the amount excluding the commission from the prepayment amount as the transfer amount and the actual settlement account as the transfer destination (step S27). The paid amount in the table 40 is updated.

  In this way, even if an arbitrary amount is paid in advance at any time, the advance payment is executed within the range of the balance that has already been fully purchased, and the electronic record receivable itself is not divided or transferred, so the advance payment is executed. This can be executed without informing the paying company, and the payment work burden of the paying company is not increased by executing the advance payment.

<Transfer flag 62>
Referring to FIG. 7 again, in the second embodiment, the settlement support system 102 is provided with a relay system 80 and a recording user master 84.
The relay system 80 provides an API for accessing the electronic bond recording organization 82. When the record request data 26 according to the API of the relay system 80 is generated, the relay system 80 generates data according to the regulations of the electronic bond recording organization 82. In addition, when the record user master 84 is connected to the relay system 80 and various data relating to the users of the electronic bond recording organization 82 are accumulated, the data items having the same contents are generated each time an electronic record bond is generated. Can be prevented, and it is possible to prevent a request other than a record request in accordance with a previously agreed contract from being made.

Particularly in the second embodiment, transfer record request data can be automatically generated by cooperation between the settlement support system 102 and the relay system 80. In the settlement support system according to the present embodiment, all the electronic record receivables whose electronic record creditors are supplier companies using prepayment are transferred to the Bank. With regard to this transfer, it is wasteful to generate transfer record request data every time as an office processing burden or as a use of computer resources.
Therefore, it is preferable to include the data item of the transfer flag 62 in the record request data 26 and automatically generate transfer record request data on the relay system 80 side when the transfer flag 62 is on. In particular, if an electronic record receivable is recorded as a request for a future date, a record request is reserved, and the transfer record is automated, it is possible to prepare for future advance payments. Specifically, the electronic record receivable can be generated on the day of occurrence of the electronic record receivable, the electronic record receivable can be transferred and recorded on the same day thereafter, and prepayment can be executed on the same day.

As described above, according to the second embodiment, since a variety of advance payments can be prepared on the assumption that the entire amount is transferred to the Bank, it is possible to provide advance payments according to the needs of a wide variety of suppliers, Even when a new transaction is made with a supplier company that has not, the deposit account currently used by the supplier company is used as the settlement actual account number 52, so that it can be used as a prepaid transfer account. .
For this reason, the paying company proposes to join a large number of supplier companies to electronically recorded receivables (switching from bills), thereby increasing the participation rate of the supplier companies and unifying the payment method. When many of the supplier companies switch to electronic record receivables, the payment affairs of the paying company can be dramatically streamlined.
Thereby, all of the payment company, the supplier company, and the financial institution introducing the system of the present embodiment can improve the productivity by IT.

Next, an embodiment will be described in which a form is transmitted by facsimile in order to make a prepayment to a supplier company. In this embodiment, facsimile is used instead of EB or Internet banking, so that the electronic record receivables of the supplier company can be used and made cheaper and the subscription rate is improved.
The present embodiment is an example of a technique that can be realized in the first embodiment and / or the second embodiment, and the method disclosed as the embodiment can be implemented in the first embodiment and / or the second embodiment.
Referring to FIG. 7 again, the payment support system 102 of this embodiment is provided with a FAX server 96. The electronic record receivable controller 10 includes a facsimile data generation unit 23 that generates facsimile data 98 relating to the payment of the paying company and the supplier company.

  The facsimile data generation unit 23 generates a list of electronic record receivables generated, transferred, and purchased electronic record receivables as the facsimile data 98 relating to the settlement, and the reference date prepayable amount, prepayment transfer, transfer by due date settlement, withdrawal of due date settlement. Generate a report that informs you of the schedule. The facsimile data generation unit 23 sends a report informing this schedule to the supplier company and the paying company via the FAX server 96 on the day of each execution date (for example, 2 to 10 days before the execution date). To the facsimile machine. In a supplier company and a payment company, electronic mail management application software that operates on a computer can also be used as a facsimile machine.

In this embodiment, an example of payment data 24 from the payment company shown in FIG. 6 to the supplier company α, β, γ, π is shown in FIG. 13, an example of the generated record reservation request data is shown in FIG. FIG. 15 shows an example of prepayment to the supplier company β, and FIG. 16 shows an example of correspondence between payment by the paying company and payment to the supplier companies α, β, γ, and π.
Examples of the facsimile data 98 relating to these settlement support are shown in FIGS.

Referring to FIG. 13, the payment data 24 having an occurrence date of April 15, 2016 is a total of six cases: two cases with a maturity of 4/26 and four cases with a maturity of 5/2. The identification of the payment data 24 can be surely specified by using the contract numbers xxx500. In the present embodiment, the user number 56 of the payment company is specified with reference to the payment company master 32 by the various contract numbers added to the payment data 24 manually or automatically.
The payment data 24 may have at least the items shown in FIG. 13. For example, the company name of the supplier company or the like is useful for checking human resources, but generation of occurrence record (reservation) billing data in the settlement support system 102 is generated. Is not required.
For example, as shown in FIG. 6, the supplier company having Y bank Naha branch 001 as the settlement actual account number 52 is α company, and the settlement account selection unit 14 refers to the supplier company master 34. The user number 58 of the supplier company can be specified from the settlement actual account number 52 (step S12 in FIG. 5). The payment data 24 includes two electronically recorded receivables with different maturity dates for the supplier company.

  Referring to FIG. 14, the generated record reservation request data 26 includes a user number 56, a settlement account number 50, an occurrence date, a maturity date, an occurrence amount (amount amount), and a transfer flag 62. The electronic record receivable controller 10 may add a name of a company or a financial institution according to a request from the electronic receivable recording institution 82. 84, and may be added by the relay system 80.

  When the electronic record receivable controller 10 receives the payment data 24 shown in FIG. 13, the number special section 12 refers to the payment company contract master 36 by using the contract number of the payment data 24 and the data transmission code as a key. After specifying the ID (500 in the figure), the settlement account number 50 (X bank Nagano branch 001 in the figure) is specified with reference to the payment company master 32 (step S2 in FIG. 4).

In the electronic record receivable controller 10, for each receivable in the payment data 24, the settlement account selection unit 14 refers to the supplier company master 34 using the settlement actual account number 52 as a key, and uses the user number 58 of the supplier company. Is specified (step S3 in FIG. 4). Next, the settlement account selection unit 14 refers to the supplier company contract master 38 and confirms whether or not prepayment is used between the payment company and the supplier company (step S4 in FIG. 4).
In the example shown in FIG. 14 and the like, since three of the supplier companies have prepaid use, the settlement temporary account number issued by the bank for each supplier company in FIG. 54 is selected (step S5 in FIG. 4). On the other hand, since there is no prepaid use for one supplier company π, the settlement actual account number 52 (Z bank Tsuruoka branch 012 in the figure) shown in FIG. 6 is selected (FIG. 4). Step S6).

  In the present embodiment, the transfer control unit 20 refers to the supplier company contract master 38 using the supplier company ID or user number 58 of the supplier company as a key, and uses the prepaid category in the prepaid category 60. At this time, the transfer flag 62 is turned on. The transfer flag 62 is a flag indicating that the Bank will transfer the entire amount of the electronic record receivable generated by the record request data 26 of the monetary receivable.

Then, as shown in FIG. 14, the record request data generation unit 16, the user number 58 of the supplier company, the settlement account number 50 (the settlement actual account number 52 or the settlement temporary account number 54), the occurrence date, the due date, By setting the generated amount and the transfer flag 62, the generated record (reservation) billing data 26 is generated. The occurrence date is a future date (previous date) with respect to the generation date of the recording request data 26.
In FIG. 14, # 01 to # 06 at the left end are the numbers of receivables given for explanation on the drawings, and are the numbers of receivables used in FIGS. 15 and 19 to 25.

When receiving the occurrence record (reservation) request data, the relay system 80 reads out and adds the items unchanged from the prior agreement from the record user master 84, and requests the record in accordance with the standard defined by the electronic bond recording organization 82. The data 26 is transmitted to the electronic bond recording organization 82.
The relay system 80 automatically generates transfer record request data for transferring an electronic record receivable to a predetermined bank for a monetary receivable in which the transfer flag 62 is on, and transmits it to the electronic receivable recording organization 82. good.

In the present embodiment, the electronic record receivable controller 10 determines that the prepayment data management unit 22 pays the full amount in accordance with the transfer flag 62 being turned on on the day for the prepayment date (the day before several business days of the prepayment date). Prepayment to the supplier company at an arbitrary amount is controlled at any time or within a range of the balance of receivables.
For example, when the prepayment data management unit 22 refers to the prepayment category 60 of the supplier company contract master 38 of the supplier company β, the prepayment date is a fixed amount of 1 million yen for the transfer date and the amount for each bond. The electronic record receivable of the date toward the prepayment date that is the transfer date is searched. Since β has 2,412,000 maturities with a maturity date of 4/26 and 2,312,000 maturities with a maturity date of 5/2, the prepayment data management unit 22 makes the prepayment possible for these receivables exceeding 1 million yen. 1 million yen, the prepayment date is the transfer date (the same day as the occurrence date of the electronically recorded receivable shown in FIG. 14), the account number of the transfer account is the settlement account number 52 of the supplier company β (FIG. 6) The transfer data as Z bank Suzukawa branch 011) shown in FIG. In practice, the transfer amount is obtained by subtracting various fees from the advance payment amount.
As shown in FIG. 15, each balance of the electronically recorded receivable purchased from the supplier company β is an amount obtained by subtracting the prepaid amount from the generated amount.
As described above, in this embodiment, it is possible to automatically make a prepayment within the balance of the electronically recorded bond.

Referring to FIG. 16, the payment company pays a total of six payments to four supplier companies α, β, λ, π.
The prepaid category 60 of the supplier company α is at any time, and this time there was an application for 3 million yen. In the example shown in Fig. 16, 3,000,000 yen out of a total of 4,722,000 yen is paid in advance on 4/18. It has been transferred from.

The prepayment category 60 of the supplier company β is a regular / fixed amount, the prepayment date is the transfer date, and the fixed amount is 1 million yen for each claim. Prepare for advance payment from the date of receipt of payment data 24, with the date of occurrence of electronic record receivable and the transfer date 4/14 as the advance payment date. The transfer is made to the account of number 52 (Z bank Suzukawa branch 011 which is another bank Z). The prepayment on the day of the transfer may be executed after receiving a transfer registration notification from the electronic bond recording institution 82, or the transfer is registered as scheduled due to the occurrence of a very exceptional event. Even if this is not possible, the payment can be completed without receiving a notice of transfer by adopting a mechanism that requires the paying company to pay to the Bank.
On the due dates 4/26 and 5/2, the balance of purchased receivables is transferred to the settlement account number 52 of the supplier company β.

  The prepayment category 60 of the supplier company γ is regular / full amount, and the designated date is the transfer date. On the transfer date of 4/14, the entire amount of the receivable is transferred in advance, and there is no balance on the 5/2 date, so no transfer is made.

  The supplier company π does not use prepayment, and the transfer flag 62 of the generated record (reservation) billing data shown in FIG. 14 is also off, and is not transferred to the bank. In the electronically recorded receivable, the settlement account number 50 of the supplier company π is a settlement actual account number 52 (Z bank Tsuruoka branch 012), and settlement is made to this settlement actual account number 52 by remittance between accounts on the due date.

In the mechanism shown in FIG. 16, the payment company A can handle the amount of money to be paid in a lump without the burden of paperwork depending on the presence or absence of the advance payment. For example, if the total amount of money in a certain range is put together into an account, individual withdrawals are automatically made and payment can be completed.
As shown in Fig. 16, the supplier company can use the prepayment of the required amount in a way that suits the situation of each supplier company, making it easy to switch from bills to electronically recorded receivables. It is easier to schedule fund management than settlement by transfer with unknown date.
In addition, since the individual amount paid in advance by the supplier company is not notified to the paying company, it can be assumed that there is a supplier company that feels attractive in that the prepaid can be used without being individually recognized by the paying company. . In addition, when using this service, a paying company can propose an extension of the payment date to a supplier company by encouraging the use of advance payment for early funding under certain conditions.
In this way, the payment company can rationalize the payment affairs by collectively handling the payment, and the supplier company can use various advance payments according to the needs.

Next, an example of a form (facsimile data 98) generated by the facsimile data generation unit 23 will be described with reference to FIGS.
Referring to FIGS. 17 and 18, the payment data 24 shown in FIG. 13 is processed, and 4/6 before and after the generation record (reservation) claim data shown in FIG. The generated account receivable statement (facsimile data 98) is sent to the facsimile machine with 4/15. This specification is tabulated for each payment date, and the facsimile data 98 shown in FIG. 18 corresponds to 5/2 minutes.
This generated record receivable statement is a list of monetary receivables generated as electronic record receivables. Prepayment category 60 shows whether it is prepaid use or densai use, but this is two choices when applying for the use of electronically recorded receivables. Detailed information on how to use prepaid Absent.
Further, in this generated record receivable statement, the settlement actual account number 52 is also displayed for the prepaid user. When using an all-bank participation type electronic bond recording institution 82, the supplier company must use the account number established at the Bank. However, if the settlement support system according to the present embodiment is used, Since the usage of the number 52 and the settlement provisional account number 54 can be automated, the payment company, which is the user, can be notified of the actual settlement account number 52 actually used from the supplier company.
In the generated record request (reservation) data transmitted from the bank X to the electronic bond recording organization 82, the settlement provisional account number 54 is used for the supplier company using the advance payment (FIG. 14).
If the payment company can be contacted with the settlement actual account number 52, it is not necessary for the payment company to manage a new account number (the settlement temporary account number 54 necessary for using the electronic bond recording organization 82).

Referring to FIG. 19, the supplier company α, whose advance payment category 60 is at any time, has an electronic record receivable generation and transfer date (4/15) on a date (4/6) before a certain period. A collective factoring transfer receivable confirmation is transmitted as facsimile data 98. When using prepayment at any time, it is necessary to apply within the amount of this electronically recorded receivable, so supplier company α uses this transfer receivable confirmation to determine whether or not prepayment is used. Judgment is made and a pre-payment application is made within the range of the prepaid amount on the base date.
This transfer receivable confirmation will be displayed including other electronically recorded receivables that have been transferred from paying company A to supplier α, and the newly transferred receivable will be clearly marked with a mark such as *. May be.
As described above, when the supplier company is notified of the amount within the prepaid amount on the base date, it is easy to consider the cash advance based on the advance payment.

Referring to FIG. 20, as shown in FIG. 16, the Densai lump factoring prepaid application confirmation form is sent as facsimile data 98 to the supplier company α that has applied for an advance payment of 3 million yen. The prepayment data management unit 22 allocates the prepayment amount from the monetary claim whose due date arrives first to the prepayment application amount. In the example shown in FIG. 20, the prepayment amount of 3 million is allocated by first allocating the entire amount of the receivable number 01 whose due date is 4/26 and then allocating the necessary 589,000 yen from the receivable number 03 whose due date is 5/2. Secure the yen. After this prepayment, the balance will be 1,722,000.
In advance payment by specifying the amount of money, the amount of interest can be minimized by allocating from the closest date.

Referring to FIG. 21, a notification of Densai batch factoring payment is sent as facsimile data 98 at the same time as the application confirmation form shown in FIG. Prepayment requires an interest rate for the number of days until the due date and a transfer fee, so the interest rate calculation shown in FIG. 21 is shown, and the amount after the reduction of interest and transfer fee is the transfer amount.
As described above, in this embodiment, the scheduled transfer date can be notified by facsimile before the transfer execution date.

  Referring to FIG. 22, when there is no second advance payment after the prepaid shown in FIG. 21, the payment amount due date is sent as facsimile data 98 before the due date of 5/2 as notice of the due date. In the notice of the due date, the face value of the electronically recorded receivable, the total of the paid amount 64 due to the advance payment, and the receivable amount as the balance are clearly indicated. This transfer is made to an account number established in another bank specified by the settlement actual account number 52.

  Referring to FIG. 23, a densai lump factoring transfer receivable confirmation is sent as facsimile data 98 to supplier company β. The supplier company β also clearly indicates that the advance payment designation date is the transfer date and the advance payment request amount (fixed amount) is 1 million yen as the advance payment category 60.

  Referring to FIG. 24, a notification of Densai lump factoring payment is sent as facsimile data 98 to supplier company β, which is a fixed payment in advance. In the example shown in FIG. 24, prepayment with a fixed amount as a prepayment amount is executed for two receivables with different due dates because each exceeds the fixed amount. The interest calculation up to the due date, the transfer fee, etc. are reduced, and the transfer is executed to the settlement actual account number 52 opened in the other bank Z.

  Referring to FIG. 25, notification of the arrival date of 5/2 is sent as facsimile data 98 to supplier company β. On 4/28, which is the date of sending the notice shown in FIG. 25, the due date of 4/26 minutes has already been settled. The receivable shown in FIG. 25 has a face value of 2,412,000 yen on the 5/2 term, a paid-up amount 64 of 1,000,000, and a receivable amount of 1,412,000 yen on the due date. In this case as well, the amount obtained by reducing the transfer fee becomes the transfer amount.

Referring to FIG. 26, for the settlement date of 5/2, a notice of batch factoring date settlement is sent as facsimile data 98 to the paying company. When the electronic record receivables are also sent from the electronic bond recording organization 82, it is not essential to transmit the form (facsimile data 98) shown in FIG. 26, but the notification shown in FIG. Since it is an amount, it is useful information for confirming the paying company.
The withdrawal amount shown in FIG. 26 is a total of three cases with a maturity date of 5/2 for the three supplier companies shown in FIG. These three cases are paid in advance, such as fixed amount and full amount each time, but if the payment company deposits the payment amount into the bank account at once, individual withdrawal will be made automatically, It is possible to make a payment by clerical work for a large number of payments, thereby streamlining the payment work.

As described above, according to the present embodiment, since the Bank, which has a transaction with the paying company, serves as a window for electronically recorded receivables, it is possible to make a report of the occurrence, transfer, advance payment, transfer, etc. at the scheduled stage, and Since these forms are sent as facsimile data 98 to the supplier company by facsimile, there is no need for EB or Internet banking contracts or proficiency, and it is possible to use electronic record receivables and receive advance payments according to needs. .
Since the form informing the schedule is transmitted by facsimile data 98, the mechanism for using the electronically recorded receivable is simple and easy to understand. Therefore, the utilization rate for the electronically recorded receivable can be expected. In particular, by using the settlement provisional account number 54, contracts with remote suppliers in Japan that do not have transactions with the Bank are easy, and if you can send and receive facsimiles, you can join electronically recorded receivables. Compared with various proposals that have been proposed in the past, it is possible to realize a mechanism that is extremely easy to join.
In this way, in this embodiment, the system for transmitting the form informing the schedule with the facsimile data 98 is used, so that the participation rate in the electronic record receivable is increased, and the improvement of this participation rate makes it possible to comprehensively pay the payment business of the paying company. Can be reduced.

A, B, C Payment company α, β, γ Supplier company X Bank (financial institution)
Y Other bank (financial institution)
10 Electronic Record Claim Controller 12 Number Identification Unit 14 Settlement Account Selection Unit 16 Record Request Data Generation Unit 18 Transfer Data Generation Unit 19 Preregistration Unit 20 Transfer Control Unit 22 Prepayment Data Management Unit 23 Facsimile Data Generation Unit 24 Payment Data 26 Record Request Data 30 Database 32 Payment company master 34 Supplier company master 36 Payment company contract master 38 Supplier company contract master 40 Receivable purchase details table 42 Receivable payment details table 46 Account system 50 Settlement account number 52 Settlement actual account number 54, 54A , 54B Settlement temporary account number 56 User number (payment company)
58 User number (supplier company)
60 Prepayment category 62 Transfer flag 64 Payment amount 80 Relay system 82 Electronic bond recording organization 84 Record user master 90 Arithmetic unit 92 Main storage unit 94 External storage unit 96 FAX server 98 Facsimile data

Claims (10)

A paying company with whom the Bank has transactions, a supplier company with which the Bank or other banks have transactions, a database for managing data relating to monetary claims held by the supplier company with respect to the paying company,
An electronic record receivable controller for generating record request data for generating the monetary receivable of the paying company to the supplier company as an electronic record receivable,
The database is
A user number of the paying company used to record the electronic record receivable with the paying company as a debtor; and
A user number of the supplier company used to record the electronic record receivable with the supplier company as a creditor; and
When making a prepayment from the Bank to the supplier company in support of the electronically recorded receivables of the supplier company, a prepayment classification for specifying the type of the prepayment in advance,
A settlement account number used by the supplier company to record the electronically recorded receivable, and a temporary settlement provisional account number established at the Bank in relation to the advance payment;
A settlement account number of the supplier company established in the Bank or the other bank, and a settlement actual account number into which the settlement amount of the electronic record receivable is actually deposited,
The electronic record bond controller is
A number specifying unit for specifying the user number of the payment company according to the payment data when payment data related to the monetary claim is transmitted from the payment company;
The user number of the supplier company is specified according to the payment data, and when the prepayment category is no prepayment use, the settlement actual account number is selected as the prepayment account number, while prepayment use is present In the case of the settlement account selection unit for selecting the settlement temporary account number,
Using the user number of the paying company, the user number of the supplier company, and the settlement account number of the selected supplier company, the supplier company makes the payment company A record request data generation unit that generates record request data for registering a monetary claim held as the electronic record claim,
A payment support system characterized by that. The database comprises a supplier company master having the user number of the supplier company, the settlement actual account number, and the settlement provisional account number associated with each other,
The number specifying unit is
A process of specifying a settlement actual account number for each supplier company in the payment data;
A process of identifying a supplier company having the settlement actual account number by referring to the supplier company master using the settlement actual account number as a search key;
And a process for identifying the settlement provisional account number of the identified supplier company,
The settlement support system according to claim 1. The electronic record bond controller is
In the relationship with the electronically recorded receivables in which the prepayment category uses the supplier company with prepayment use, the prepayment amount by the calculation method determined in advance in the prepayment category is set as the transfer amount, and the settlement actual account number With a transfer data generation unit that generates transfer data with
The settlement support system according to claim 1 or 2, characterized in that. The electronic record receivable controller comprises a pre-registration unit for registering data relating to the paying company and the supplier company in the database when contracting to use the electronic record receivable between the paying company and the supplier company,
When the pre-registration unit registers the settlement temporary account number in the database, a unique temporary account number is assigned to the supplier company issued for each supplier company. Pre-register as a number,
The settlement support system according to claim 3. The electronic record receivable controller comprises a pre-registration unit for registering data relating to the paying company and the supplier company in the database when contracting to use the electronic record receivable between the paying company and the supplier company,
When this pre-registration unit registers the settlement provisional account number in the database, the one-to-one combination of the payment company and the supplier company issued for each combination of the payment company and the supplier company Pre-register a unique account number as the temporary settlement account number for the supplier.
The settlement support system according to claim 3. The electronic record bond controller is
For each monetary claim in the payment data, when the prepayment is used in the prepayment category, the transfer flag that the Bank will transfer all and all of the electronically recorded receivable generated by the record request data of the monetary claim A transfer control unit to turn on,
A prepayment data management unit that controls prepayment to the supplier company at any time or periodically within the range of the balance of the amount of receivables that the Bank has transferred in full according to the turn-on of the transfer flag,
The settlement support system according to claim 1, 2, 3, 4 or 5. The database is
A supplier contract master having a prepayment category of the supplier company for each supplier company and for each paying company;
A claim purchase details table for managing the contents of electronically recorded claims to be transferred from the supplier company with the advance payment in accordance with the transfer flag being turned on,
When the prepayment data management unit handles a regular and fixed amount prepayment method as the prepayment classification,
A process of extracting a supplier company whose prepaid scheduled date is a scheduled scheduled date with reference to the supplier contract master on the day toward the scheduled prepaid date;
A process for identifying a group of electronically recorded receivables transferred from the supplier company with reference to the receivable purchase details table and before the maturity date;
A process of assigning a balance of each electronically recorded claim to a prepayment amount from the specified electronically recorded claim group to the fixed amount in order of arrival of the maturity date,
A process of generating transfer data with an amount corresponding to the total amount of the prepayment allocated as a transfer amount, the scheduled date as the transfer date, and the settlement real account as a transfer destination account;
Processing to update the paid amount in the receivable purchase details table with the amount of the prepayment date on the transfer date;
The settlement support system according to claim 6, further comprising: When the prepayment data management unit handles the prepayment method for the entire amount of all receivables as the prepayment classification,
After receiving the payment data, a process of extracting a supplier company in which the prepayment classification is all receivable and full amount from the payment data;
A process of assigning the entire amount of the electronic record receivable of the extracted supplier company to the advance payment amount for the date of occurrence of the electronic record receivable specified in the payment data;
The amount corresponding to the allocated prepayment amount is set as the transfer amount, the transfer date of the electronic record receivable recorded according to the transfer flag being turned on is set as the transfer date, and the settlement account of the supplier company is transferred. Processing to generate the transfer data ahead,
A process of recording the paid amount of the electronically recorded receivable as a full amount on the receivable purchase details table as of the date of transfer;
8. The settlement support system according to claim 7, further comprising: A paying company with whom the Bank has transactions, a supplier company with which the Bank or other banks have transactions, a database for managing data relating to monetary claims held by the supplier company with respect to the paying company,
An electronic record receivable controller for generating record request data for generating the monetary receivable of the paying company to the supplier company as an electronic record receivable,
The database is
A user number of the paying company used to record the electronic record receivable with the paying company as a debtor; and
A user number of the supplier company used to record the electronic record receivable with the supplier company as a creditor; and
When making a prepayment from the Bank to the supplier company in support of the electronically recorded receivables of the supplier company, a prepayment classification for specifying the type of the prepayment in advance,
A settlement account number used by the supplier company to record the electronically recorded receivable, and a temporary settlement provisional account number established at the Bank in relation to the advance payment;
Using a settlement support system comprising a settlement account number of the supplier company established in the bank or the other bank, and a settlement actual account number into which the settlement amount of the electronic record receivable is actually deposited A settlement support control method for supporting settlement,
The electronic record bond controller is
When the payment data related to the monetary claim is transmitted from the payment company, the user number of the payment company is specified according to the payment data,
The user number of the supplier company is specified according to the payment data, and when the prepayment category is no prepayment use, the settlement actual account number is selected as the prepayment account number, while prepayment use is present In the case of, select the settlement temporary account number,
Using the user number of the paying company, the user number of the supplier company, and the settlement account number of the selected supplier company, the supplier company makes the payment company Generating record request data for registering a monetary claim held as the electronic record claim,
A settlement support control method characterized by the above. A paying company with whom the Bank has transactions, a supplier company with which the Bank or other banks have transactions, a database for managing data relating to monetary claims held by the supplier company with respect to the paying company,
An electronic record receivable controller for generating record request data for generating the monetary receivable of the paying company to the supplier company as an electronic record receivable,
The database is
A user number of the paying company used to record the electronic record receivable with the paying company as a debtor; and
A user number of the supplier company used to record the electronic record receivable with the supplier company as a creditor; and
When making a prepayment from the Bank to the supplier company in support of the electronically recorded receivables of the supplier company, a prepayment classification for specifying the type of the prepayment in advance,
A settlement account number used by the supplier company to record the electronically recorded receivable, and a temporary settlement provisional account number established at the Bank in relation to the advance payment;
Using a settlement support system comprising a settlement account number of the supplier company established in the bank or the other bank, and a settlement actual account number into which the settlement amount of the electronic record receivable is actually deposited A payment support control program for supporting payment,
In the electronic record bond controller,
When payment data related to the monetary claim is transmitted from the payment company, the user number of the payment company is specified according to the payment data,
The user number of the supplier company is specified according to the payment data, and when the prepayment classification is no prepayment use, the settlement real account number is selected as the settlement account number, while prepayment use is present. In the case of, let me select the settlement temporary account number,
Using the user number of the paying company, the user number of the supplier company, and the settlement account number of the selected supplier company, the supplier company makes the payment company Generating record request data for registering a monetary claim held as the electronic record claim,
A payment support control program characterized by the above.

Images