JPH1196275A - Accounts payable trade batch payment trust system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To reduce the costs of stamp tax charge, issue business, or the like, and to make it possible to surely receive prices before a settlement date by checking an amount transferred from a payer on the settlement day and a set money trust and transferring the amount to each client based on the details of the trust in each client. SOLUTION: Receiving processing for credit sales claim data sent from a payer is executed (a). Only data matched with a data receiving schedule out of the received data are registered. After the data receiving processing, the contents of the received data are transmitted to the payer through a facsimile(FAX) as a detailed statement of a trust claim (b). A trust is set up in each data reception. Consequently beneficiary right transfer and transfer to a third person can be attained. After setting up the trust, following documents are transmitted to the payer, the client and a 2nd beneficiary through the FAX (c), (d). Namely a trust claim detailed balance sheet is transmitted to the client through the FAX in each setting of a trust. A trust beneficiary right detailed balanced sheet and a period-sorted payment schedule are respectively transmitted to the 2nd beneficiary and the payer through the FAX in each setting of a trust.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a system for trust payment of accounts payable by a trust method without issuing bills.

[0002]

2. Description of the Related Art Generally, bill settlement is used for settlement between a paying company and a supplier company. In other words, the supplier company performs a procedure for billing the payment together with the delivery to the paying company. In contrast, the paying company issues bills of exchange to the vendor, and the vendor converts the bill to the maturity date of the bill or to the amount discounted by the bill discount if there is a demand for funds before the maturity date. The method of doing was adopted. In transmitting data, JBA procedures include a transmission method using a personal computer procedure using a JIS-8 code as a transmission code and a transmission method using a basic procedure using an EBCDIC code as a transmission code. However, the JBA data reception system using a personal computer could only receive either the personal computer procedure or the basic procedure.

[0003]

In the settlement using the bill, there is a problem that the paying company has to pay a stamp tax to be attached to the bill, and the cost of issuing the bill is increased. On the other hand, for suppliers, there were problems associated with the clerical work of bills and the problem of preventing accidents in storing bills. Recently, as a service to eliminate bills of exchange, a method of purchasing accounts receivable by factoring companies has been introduced by city banks, etc.
For the supplier, the quality of the receivables has changed to the factoring company risk receivables, and the accounting process is "Accounts receivable"
However, there were problems such as the change to “unpaid money”. In transmitting data, some of the transmitting companies include a computer procedure company and a basic procedure company. However, there is a problem that existing products can only receive data transmission from one of a company of a basic procedure and a company of a personal computer procedure. A further object of the present invention is to enable a transmitting company to receive data in both the personal computer procedure and the basic procedure. Another object of the present invention is to automatically convert received data into a code system (JIS-8 code) usable by a personal computer.

[0004]

SUMMARY OF THE INVENTION The present invention has been studied to solve the problems of settlement using the above bills and settlement by factoring. As a result, the method of securitization of receivables by a trust system is utilized by utilizing a computer system. This is a trust system for payment of accounts payable using a trust method in suppliers, paying companies, and trust banks, finding that the problem can be solved. That is, the present invention relates to (1) (a) data transmitted by a paying company (payer) to a trust bank by sending a statement of the accounts receivable and trade generated by the supplier (consignor) to the paying company (payer). (B) a device for notifying the paying company (payer) of the transmitted data as a statement of claims, and (c) a trust setting after obtaining the consent of the paying company (obligor) without any consent. A device for notifying the supplier (consignor) of the balance of trust receivables (accounts receivable). (D) After confirming the lump-sum payment to the trust bank based on the above aggregation on the settlement date of the receivables of the paying company, On the same day, the trust bank includes a device for transferring the payment to the beneficiary right holder in a trust account payable lump-sum trust system. In the above (a) reader, (i) customer information (payer, (Contractor) and (ii) Receivable data Checking the receivable data that has not yet been received before or after the scheduled reception date, accepts the receivable data transmitted from each payer, and the receivable detail notification device shown in FIG. After receiving the data (correcting the data if there is a correction), prepare a trust receivable statement (grouped by payer) based on the received data and transmit it to each payer. (C) Trust receivable balance The notification device receives and checks the presence or absence of an objection to the above-mentioned receivables statement from each payer, returns the objectionable receivables item to the data transmission device of (a), and sets the trust setting for each payer for the unobstructed receivables item. (I) preparing and transmitting a due date payment schedule compiled by due date to the payer based on the trust receivable statement set up in the trust; and (ii)
A trust receivable statement balance table prepared for each trustee is prepared and transmitted to the trustee, and the consent of the payer and the trustee is obtained. (D) The transfer device prepares fund transfer data, prepares payment date data, and The transfer to these payers is carried out, the amount transferred from the payer on the settlement date based on this is checked against the trust set above, and based on each trustee's trust statement, each (2) The beneficiary right holders in (2) and (d) are a consignor and a second beneficiary, and the (a) reader is used to perform the transfer to the consignor. (I) The customer information registered in advance is the payer, the consignor, and the second beneficiary, and (c) the trust setting is performed for each payer with respect to the undeclared receivables by the trust receivable balance notifying device. (I) payment based on the trust receivable statement To creates transmit the due date by the payment calendar that was organized by the due date, as well as creating transmission the receivables in the trust specification balance table was organized by consignor are to (ii) consignor, (ii
i) The trust beneficiary right statement balance table compiled for each second beneficiary is created and transmitted to the second beneficiary to obtain the consent of the payer, the consignor and the second beneficiary, and the accounts payable described in (1) above Payment trust system, (3) between (c) and (d), (f) the trust bank receives a discount application from the trustee and / or second beneficiary,
It has a device that mediates investors based on the discount application and performs a transfer procedure on behalf of the consignor and / or the second beneficiary. In the transfer procedure device (f), the consignor and / or the second (Ii) System registration of the beneficiary right transfer consent request sent from the beneficiary, acceptance of the transfer application, transfer, and transmission of beneficiary right transfer information to the consignor and / or the second beneficiary, (1) or (2) Accounts payable lump-sum trust system described in (2), (4) Payer, consignor, confirmation between the second beneficiary and the trust bank, having correction device (1), (2) or (3) The described system. FIG. 1 shows a flowchart of the system of (1) and (2),
FIG. 2 is a flowchart of the processing flow of (1) and (2).
The flowchart of the system of (3) is shown in FIG.
FIG. 4 shows a flowchart of the processing flow of (3).

FIG. 5 shows a processing flow of the data reception processing in (a). In order to perform the trust setting, which is the most important in the accounts payable lump-sum trust system of the present invention, without error, it is necessary to strictly perform this data reception processing without error. Therefore, as shown in FIG. 5, the data reception processing is strictly performed without error by combining four types of checks, that is, a reception file configuration check, a header record check, a data record check, and a client information check. The method of each check is as follows. 1. Reception file configuration check (1) File size: multiple of 120 bytes, or 12
Must be a multiple of 0 bytes + 1 byte. (2) Record order check The order of records in the file is as follows: Header record (A) → Data record (B) → Trailer record (C) ... Repeat ... Header record (A) → Data record (B) → Trailer Record (C) → End record (D). The header record (A) is information about each payer, the data record (B) is information about the client (s) to be paid by each payer, and the trailer record (C) is the total number and amount of B, The combination of (A) and (C) is determined by the relationship of (B), and for some (B), the number of cases and the total amount of (B) in (C) are incorrect. And an error comes out. And AB ₁ B for each date
₂ B ₃ . . . A plurality of units, with C as one unit, are closed at the end record of D. If such a configuration is not established, an error is issued.

[0006] 2. Header record check (1) Attribute check (check that numbers are to be entered where numbers are to be inserted and characters where characters are to be inserted are characters) The characters specified for each item are registered. Kana character item: Only kana characters recognized by EBCDIC are recognized. Amount / date item: Only numbers are allowed. (2) Payer information check (account name, account number, etc.) Information on the payer in the header record matches the contents of the payer information table registered in the database. At this time, by checking the combination of the account name and account number, it is recognized that the corporation and the corporation are the same, and the fuzzy check can be performed with a certain margin, such as ignoring the space. I have. (3) Header Record Matching Check If there are multiple header records (A) with different due dates in the reception file, the contents of those header records (A) must match (however, the due date). Is unique among all header records). Data attribute check (check for B) Characters specified for each item must be registered. Kana character item: Only kana characters recognized by EBCDIC are recognized. Amount / date item: Only numbers are allowed. Check each item of data record, trailer record and end record. 4. Account information check of the client The account information on the data record must be registered in the client information table. The same operation as checking the payer information is performed.

FIG. 6 shows a processing flow of the trust setting in (b), and FIG. 7 shows a processing flow of the trust receivable notification in (c).

FIG. 8 shows a processing flow of the payment in (d). In the figure, each item is as shown below. 1. Payment Date Transfer Data Creation (1) Transfer data (F-mate format file) is created based on the balance and transfer amount of each statement. (2) The transfer amount is obtained by subtracting the transfer fee from the total balance of the statement. Calculation of transfer fee a. For subcontractors, the transfer fee is $ 0 b. In the case of the client, the transfer fee is calculated under the following conditions. Transfer destination is Fuji Bank Kabutocho branch → $ 0 Transfer destination is Fuji Bank and other than Kabutocho branch → Payer information, bank collection fee × (1 + consumption tax rate) Transfer destination is other than Fuji Bank → Payer information, other bank request Commission x
(1 + consumption tax rate) c. In the case of the payer's burden, the payer bears the transfer fee only once for each statement, and the consignor bears the fee otherwise. (If the balance becomes $ 0 due to the split transfer process and if the balance remains at the time of payment date processing, etc., the payer will pay at the time of payment date processing.) (3) Details of transfer to the same bank account If there are multiple cases, the transfer data is combined into one so that they need only be transferred once. (If the statement to be collected includes both the statement paid by the client and the statement paid by the payer, it is treated as a payer burden.) Payment date transfer data transmission (1) 1. Copy the F-mate file created in step 2 to the F-mate transmission FD. (2) Payment date form output-Payment date processing result list-Bank account slip invoice data (payment date processing)-SK system general-purpose journal entry form.

FIG. 9 shows a processing flow for a third-party transfer application in which beneficiary rights are transferred (split) from the consignor to the second beneficiary. The cancellation of the third-party transfer is performed based on the following condition (1), and items (2),
(3) is as follows. (1) Cancellation of third-party transfer Cancellation conditions for third-party transfer ・ Transfer to a third party ・ Transaction application statement does not exist each time ・ If canceled before the transfer date , The third-party transfer input inspection table is printed (for cancellations after the transfer date, the third-party transfer input inspection table is not printed) (2) Checking the input details Conditions of the transfer target statement ・ Trust settings have been made・ Not canceled ・ Transferable amount exists ・ Payment date has not yet arrived (3) Check of input items Transfer date, transfer amount, details of transferee second beneficiary check ・ Transfer date> system date ・ Transfer Checking the business day of the day ・ Two business days after the input details> transfer date ・ Transferable amount-transfer amount ≧ 0 ・ The second beneficiary who entered is the second beneficiary of the trustee of the input details.

In the above (a), in the present invention, the connection mode classification of the TTC part of the received start request message is stored, and thereafter, data reception is performed using the connection mode classification, whereby the personal computer procedure and the basic procedure are performed. It supports both data transmissions. Also, when data is received in the basic procedure, the code is automatically converted (EBCDIC code → JIS-8 code).
I do. Specific schemes of the accounts payable lump-sum trust system of the present invention include: Trust setup: Supplier delivers goods to paying company and accounts receivable is generated.
(The paying company notifies each supplier of the amount of accounts receivable through a "payment summary table" etc.) The paying company transfers the accounts receivable on behalf of the supplier (sets up a monetary receivable trust). At that time, the paying company sends the details of the receivables to the trust bank by computer transmission, and the trust bank collects the transmitted data for each supplier. Thereafter, the paying company will add additional accounts receivable each month on behalf of the supplier. The trust bank will have a counter-criterion for the transfer of the trust by obtaining a fixed dated consent from the paying company. After the transfer of the trust, the trust bank notifies the supplier of the balance of the trust receivables (accounts receivable). The supplier will have a beneficiary right through the above trust setting. The beneficiary rights of the supplier can be split and transferred by registering the second beneficiary information. II. Financing of the supplier or the second beneficiary company The supplier or the second beneficiary can raise the financing by transferring the receivables converted into beneficiary interests in a discounted form after the financing date (bills) Discount). The trust bank mediates investors and performs transfer procedures on behalf of the supplier or second beneficiary based on a discount application from the supplier or second beneficiary. The discount application method is as follows: (1) As-needed application method (PM3 three business days before the funding date:
(The fax must be delivered to the company by 00.) (2) There are two types of lump-sum application method (automatic funding every month on the day when the money is available). III. When accounts receivable is collected (bill maturity date) The paying company transfers money to the trust bank on the settlement date of accounts receivable (maturity date of the bill). On the same day, the trust bank will transfer the money to the beneficiary right holders. Cash flow when vendor or second beneficiary capitalizes accounts receivable: paying company → trust bank → investor Cash flow when not financing: paying company → trust bank → vendor or second beneficiary Person

[0011]

DESCRIPTION OF THE PREFERRED EMBODIMENTS The outline of the system of the present invention will be described more specifically as follows. I. Trust setting 1) Registration of customer information a. Registration of payer information When a new customer is created, the payer information is first registered in the system. If the payer information is not registered, the entrustor information and the second beneficiary information shown in the following a and c cannot be registered. I. Registering Consignor Information Register consignor information for the payer registered at the destination in the system. If the client information is not registered, the second beneficiary information cannot be registered. The consignor is able to transfer the beneficiary right in a normal manner and to the second beneficiary (transfer to a third party). C. Registration of the second beneficiary information When transferring the beneficiary right of the client to a third party, it is necessary to register in advance the second beneficiary information. The second beneficiary can transfer ordinary beneficiary rights only to the beneficiary rights transferred from the client. 2) Preparation and transmission of trust receivable statement a. After the data reception (or data correction if correction) process, the contents of the received data are transmitted to the payer as a trust receivable statement. 3 ) Trust setting a. After confirmation of the trust receivable statement by the payer, trust is set for each data reception unit. 4) Notification of trust setting a. After the trust is established, the following notice will be given to the payer, the consignor, and the second beneficiary. (A) Trust receivable statement balance table Notify the trustee each time a trust is set up. (B) Trust beneficiary right statement balance table Notify the second beneficiary each time a trust is set up. (C) Schedule of payment by due date Notify the payer each time a trust is set up. II. Financing of suppliers or second beneficiary companies 5) Transfer application (application at any time) a. Receipt of transfer application System registration of the beneficiary right transfer consent request sent to the investor sent from the consignor (or second beneficiary). 6) Transfer to a third party a. Transfer to third parties Transfer part or all of the beneficiary rights held by the client to a third party (second beneficiary). 7) Notice of transfer of beneficiary rights a. After sending the fund transfer data (today is the transfer date statement)
The following notice is sent to the client and the second beneficiary. (A) Trust beneficiary right transfer condition confirmation document Notify the contents of the beneficiary right transfer to the consignor or second beneficiary. (B) Trust beneficiary right transfer condition confirmation (third party transfer) The details of the third party transfer will be notified to the client. (C) Notification of transfer of trust beneficiary right Notification to the second beneficiary of the details of the transfer of the third party. III. When accounts receivable is collected (bill maturity date) 8) Fund transfer a. Create fund transfer data Create transfer data for the details of the transfer of funds the next business day. I. Send fund transfer data Send the transfer data created in (1) to the bank. 9) Payment date a. Creation of payment date data Transfer data is created in a batch process for items that are due for payment two business days later. I. Send payment date data Send the transfer data created in a. Above to the bank. One JBA procedure receiving program can receive both the PC procedure and the basic procedure, and the data received in the basic procedure is automatically converted to a code system usable by the personal computer. The received data saves the received content as it is, and only the basic procedure saves the file after code conversion. The code conversion table can be changed by the user. At the time of code conversion, if the storage area is insufficient, an error message is displayed and an operator's instruction is waited. The program is
Incoming calls are always monitored, and if there is a request to open a station via a telephone line, it is automatically received. After normal reception, the system automatically returns to the incoming call monitoring state.

[0012]

EXAMPLES Examples of the present invention will be described and described, but it goes without saying that the present invention is not limited to these examples. (1) When setting up a trust As shown in Table 1, when a supplier sells (delivery) goods (generates accounts receivable) to a paying company, the paying company generates accounts payable. The closing date (end of month) is determined from the delivery date (account receivable). Confirmation of accounts receivable is performed between the delivery date and the closing date. The paying company transmits an application for trust transfer (trust setting) and accounts payable data to the trust bank on behalf of the supplier. Accounts payable data describes the date and time of the supplier, etc., and uses the message format used in the lump-sum payment system. The trust bank receives the accounts payable data, reads the data in the system, accepts the trust setting, outputs the statement of receivables from the system, and faxes to the paying company. The paying company checks the receivable detail information, and contacts the company by facsimile in case of data correction. The trust bank will correct the data, if any (data confirmation date, fundable date-
Up to 5 days). The paying company issues a letter of consent to transfer the receivables and brings them to the trust bank (providing a counter-requirement). (The trust bank separately bills the paying company for the fixed-date cost.) The trust bank outputs the statement of receivables from the system and sends it to each supplier by fax.

[0013]

[Table 1]

(2) At the time of funding the supplier As shown in Table 2, the supplier faxes the transfer consent request form to the trust bank. The trust bank receives the transfer consent request form, registers it in the system after stamping, and faxes the receipt confirmation to the supplier. (Transfer application date: FAX must arrive from -4 days before funding until 3:00 PM three business days before settlement). The trust bank will notify the supplier (and investors) of the transfer statement of the beneficiary rights by facsimile (equipment must meet the requirements) (fixed date fee will be separately charged to paying company) (transfer date: available date of funding-2) Days). The trust bank remits to the purchasing company (the investor remits to the trust bank). (Settlement date: transfer date + 2 days).

[0015]

[Table 2]

(3) Third party transfer As shown in Table 3, by registering the beneficiary right transfer consent request sent from the consignor by facsimile in advance in the system, a transfer application to the second beneficiary can be made. Approve the details of the acceptance and transfer application.

[0017]

[Table 3]

(4) Payment of accounts receivable As shown in Table 4, the paying company pays to the trust bank on the payment date. The trust bank transfers funds to the beneficiary suppliers (and investors). The trust bank prepares and mails a monthly report.

[0019]

[Table 4]

[0020]

Embodiment 1 (1) Registration of customer information a. Registration of payer information When a new customer is created, the payer information is first registered in the system. If payer information is not registered, entrustor information and second beneficiary information cannot be registered. I. Registering Consignor Information Register consignor information for the payer registered at the destination in the system. If the client information is not registered, the second beneficiary information cannot be registered. The consignor is able to transfer the beneficiary right in a normal manner and to the second beneficiary (transfer to a third party). C. Registration of the second beneficiary information When transferring the beneficiary right of the client to a third party, it is necessary to register in advance the second beneficiary information. The second beneficiary can transfer ordinary beneficiary rights only to the beneficiary rights transferred from the client. (2) Data reception schedule registration Register the expected date of receiving the receivables data sent from the payer. The annual reception schedule can be registered from once to 99 times per month. Unable to register if payer information is not registered. If the holiday for which the schedule is to be registered is not registered in the holiday management, the holiday is erroneously registered, so it is necessary to confirm the registered content of the holiday management. (3) Data reception a. The receivable data sent from the payer is accepted. As this data, only the data that matches the data reception schedule of (2) is registered. The receiving method includes a method of receiving data transmitted (automatic),
How to manually input and accept from information such as fax (manual)
There are two types. The reception method is determined by the registered contents of the data reception schedule at the time of data reception, and thus can be changed at any time before data reception. I. The automatic reception automatically registers the accounts receivable data sent from the payer in the system. If the payer information of the receivables and receivables data is not registered in the system, it is automatically registered in the system unless the attribute of the item is incorrect. After registration, the receivables receivable data list is printed,
Check for errors. Error data is corrected using a data correction function. C. In the manual reception, the data is manually registered in the system from a facsimile or the like sent from the payer. All other functions perform the same processing as automatic reception. (4) Data correction a. The data correction function is used when there is an error in the contents of the reception data, or when a request for correction of data is made by a contact from the payer. Additions, changes, and deletions are possible for each line item. Data can be corrected until the beneficiary right is transferred or a third party is transferred. After the correction, the data correction list is printed, and the details of the correction are confirmed. (5) Batch deletion a. Delete them collectively for each reception data. If incorrect data is received by mistake and batch deletion is performed, the reception process can be restarted. The batch deletion function physically deletes all the details in the unit of the reception data. Note that if you delete it by mistake, it cannot be undone. Also,
As in the case of data correction, beneficiary right transfer or third-party transfer can be collectively deleted, so care must be taken when deleting trust-set details. (6) Preparation and transmission of trust receivable statement a. After receiving the data (or correcting the data if there is a correction), the content of the received data is faxed to the payer as a trust receivable statement. When you click the “Send Trust Claim Details” button, the system will automatically perform fax transmission, but be sure to check for non-delivery notices. (7) Trust setting a. Set trust settings for each data reception unit. After setting up the trust,
The SK system general-purpose journal entry form is printed. By setting up a trust, beneficiary rights can be transferred and third parties can be transferred. The specification of the comprehensive transfer request destination is registered in the system as a transfer reservation specification when setting up the trust. (8) Sending the customer report (trust setting) a. After the trust is set up, the following form is faxed to the payer, the consignor, and the second beneficiary. “Customer report form (trust setting)
Click the "Send" button and the system will automatically
The transmission is performed until X transmission, but the confirmation of the non-delivery notification is performed without forgetting. (A) Trust receivable statement balance table FAX is sent to the client each time a trust is set up. When the trust is set for the first received data every month, a trust receivable statement balance table is created and transmitted for all trust statements that have not expired and that are held by all the payers of the payer. At the time of setting the trust for the second and subsequent received data, a trust receivable statement balance table is created and transmitted for all the unexpired trust statements of the trustees who hold the trust set details this time. (B) Trust beneficiary right statement balance table A fax is sent to the second beneficiary each time a trust is set up. 1 every month
When a trust is set for the second received data, a trust beneficiary right statement balance table is created and transmitted for all unexpired trust statements held by all second beneficiaries of the payer.
When the trust is set for the second and subsequent received data, the trust beneficiary right statement balance table is not created and transmitted. (C) Schedule of payment by due date A fax is sent to the payer each time a trust is set up. Regardless of the number of receipts, create a due date payment schedule for all the payers' lines that are due after the trust setting date &
Send. (9) Interest registration a. Register the market interest rate used for calculating the discount rate.
Value Date is 2 business days after Tibor (1M
１２12M) and short Ps are registered daily. After registration, the market interest rate registration list is printed, so check the contents. (10) Transfer application (application at any time) a. Transfer application acceptance Register the beneficiary right transfer consent request sent by FAX from the consignor (or second beneficiary) in advance in the system. After the trust setting date, the transfer application can be input until the date of the transfer (until the transfer date is before the transfer data is transmitted). After registration, a beneficiary right transfer consent input scrutiny table is output. After the scrutiny is complete, the transfer will be valid by giving a batch approval. I. Cancellation of transfer application acceptance The transfer application will be canceled in detail units if there is an error in the information entered in a, or if the transfer application is withdrawn. After the cancellation, the beneficiary right transfer consent input scrutiny table is re-output, so the cancellation details are confirmed. Cancellation after batch approval is canceled by cancellation of approval. Cancellation is possible up to the date of the transfer (until the transfer date is before the transfer data is sent). C. Batch Approval Collectively approve the details of the transfer application received for each inspection table. The system will automatically perform the transfer calculation on the day before the transfer, together with the statement of the comprehensive transfer request destination, for the collectively approved specifications. D. Cancel Approval Cancels the batch approved items. Cancellation of approval is basically the same as cancellation of acceptance of transfer application, except for the difference between whether the target item to be canceled is unapproved or approved. The item of the comprehensive transfer request destination is canceled using the approval cancellation. Please note that after the cancellation of the specification, all reassignments will be applied at any time. (11) Third party transfer a. Transfer to third parties Transfer part or all of the beneficial interests held by the client to a third party. Since advance registration is not possible, enter the details for which the desired transfer date (transfer date) will be the next business day today. In order to transfer to a third party, it is necessary to register the transferee (second beneficiary information) in advance. After the registration, a third-party transfer input inspection table is output, and the input contents are inspected. I. Third-Party Transfer Cancellation of a third-party transfer is performed on a per-item basis, such as when there is an error in the information entered in a) or when the transfer application is withdrawn. After the cancellation, the third-party transfer input inspection table is re-output, so the cancellation details are confirmed. (12) Transmission of the customer report (transfer of beneficiary right) a. After sending the fund transfer data (today is the transfer date statement)
The following forms are faxed to the client and the second beneficiary. When you click the "Send reference form (benefit right transfer)" button, the system will automatically perform fax transmission, but do not forget to confirm the non-delivery notice. (A) Trust beneficiary right transfer condition confirmation document Fax transmission of the contents of the beneficiary right transfer (only for the transfer date today) to the consignor or second beneficiary. (A) Trust beneficiary right transfer condition confirmation document (third-party transfer) FAX transmission of the contents of the third-party transfer (only for the details of the transfer date today) to the client. (C) Trust beneficiary right transfer notice FAX transmission of the contents of the third party transfer (today only for the details of the transfer date) to the second beneficiary. (13) Fund transfer a. Create fund transfer data Create transfer data for the details of the transfer of funds the next business day. Create it first in the morning of the day. (12: 0
(Because it will not be possible to fund the next day unless it is sent to the bank by 0.) If a cancellation statement occurs before creating the fund transfer data, the corresponding statement is canceled. If a cancellation statement is generated after the fund transfer data is created, the relevant statement is canceled and the fund transfer data is re-created again. I. Transmission of fund transfer data The transfer data created in (1) is output to the FD for Super FUJI mate. The output FD is set in the FUJI mate terminal and transmitted to the bank. After the FD is output, the details cannot be canceled, so the process is performed after confirming the presence or absence of the canceled details. (14) Payment date a. Creation of payment date data Transfer data is created in a batch process for items that are due for payment two business days later. I. Payment date data transmission The transfer data created in (1) above is output to the Super FUJI Mate by FD in business processing on the next business day. FD output
Is set in the FUJI mate terminal and transmitted to the bank.
Like the fund transfer data, it is created first in the morning of the day. (1
Do not send to the bank to 2:00 and the next day for capital reduction is not in time) (15) business end A. Finish all operations of today and start batch processing. In the batch process, updating process of beneficiary right balance, transfer calculation process, payment date process, and the like for processing on the next business day are performed, so it is confirmed that there is no unloading operation of today. After the work is completed, a work schedule and a payment amount confirmation table are output.

[0021]

According to the system of the present invention, it is possible to reduce the burden of stamp duty and issuance affairs by using bills of exchange, and suppliers who cannot afford cash can pay the trust bank after paying a certain fee. The beneficiary rights can be transferred and received reliably before the due date, and the creditworthiness of the paying company can be used to raise funds at short-term prime rates or lower.
Also, compared to the means by which the factoring company purchases accounts receivable, the counterparty and risk of accounts receivable do not change,
This is an excellent effect that the supplier can receive the fund settlement service without changing the contents of the receivables. Furthermore, the supplier can transfer the beneficiary right to the second beneficiary in a divided manner, which is also efficient and convenient. By performing a plurality of checks in the data reception using a computer, the trust setting can be performed strictly and easily. In addition, when setting up a trust for a trust receivable, the trust setting process is performed for one received data group instead of setting the trust for each item, so that the processing time for the trust setting does not depend on the number of items. Things.

[Brief description of the drawings]

FIG. 1 is a flowchart of a system according to claims 1 and 2;

FIG. 2 is a flowchart showing a work flow of the system according to claims 1 and 2;

FIG. 3 is a flowchart of a system according to claim 3;

FIG. 4 is a flowchart showing a work flow of the system according to claim 3;

FIG. 5 is a flowchart illustrating a processing flow of a data reception process.

FIG. 6 is a flowchart showing a trust setting process flow.

FIG. 7 is a flowchart illustrating a processing flow of trust receivable notification.

FIG. 8 is a flowchart illustrating a processing flow of payment.

FIG. 9 is a flowchart showing a processing flow for a third party transfer application.

FIG. 10 is a schematic diagram of a scheme when a basic agreement is concluded among a paying company, a supplier, and a trust bank.

FIG. 11 is a schematic diagram of a scheme when a trust is set up (monthly) between a paying company, a supplier and a trust bank.

FIG. 12 is a schematic diagram of a scheme for financing a supplier company among three parties: a paying company, a supplier, and a trust bank.

FIG. 13 is a schematic diagram of a scheme at the time of collection of accounts receivable (bill maturity date) between a paying company, a supplier, and a trust bank.

Claims (4)

[Claims] (1) An apparatus for reading data transmitted by a paying company (payer) to a trust bank for details of accounts receivable generated by delivery from a supplier (consignor) to the paying company (payer). (B) a device for notifying the paying company (payer) of the transmitted data as a credit statement, (c) a paying company (obligor)
After the trust is set up with the consent of No. 1, the device that notifies each supplier (consignor) of the balance of the trust receivables (accounts receivable), (d) the settlement date of the receivables of the paying company After confirming the lump sum transfer to the trust bank based on the above aggregation, the trust bank includes a combination of a device for transferring the lump sum to the beneficiary right holder on the same day. Based on (i) customer information (payer, consignor) and (ii) receivable receivable data reception schedule registered in advance, the apparatus receives unreceivable data of the receivable receivable data on or before the scheduled reception date. After checking the receivables data transmitted from each payer, the receivable detail notification device shown in (b) receives the receivables data (if there is a correction, corrects the data), Classify by payer (Collected) a trust receivable statement is prepared and transmitted to each payer. (C) The trust receivable balance notifying device receives and checks whether or not there is an objection to the above receivable statement from each payer, and checks the disputed receivable statement. Is (a)
To the data transmission device, and set up a trust for each payer with respect to the undeclared receivables statement. Based on the trust receivables set up in the trust, (i) prepare a due date payment schedule for the payer by date. And (ii) prepares and sends a trust receivable statement balance table compiled for each consignor to the consignor and obtains the consent of the payer and the consignor. (D) The transfer device prepares fund transfer data, Creates the payment date data and transmits it to these payers, checks the amount transferred from the payer on the settlement date based on this and the trust set up above, and sets each trustee A one-time payment account payable trust system, in which transfer is made to each client based on another trust statement. 2. The beneficiary right holder in (d) is a consignor and a second beneficiary, and (i) the customer information registered in advance by the reader (i) is the payer, the consignor and the second beneficiary. The beneficiary, and (c) the trust receivable balance notification device sets trust for each payer with respect to the undeclared receivable details, and based on the trust receivable details set for the trust, (i) summarizes the receivable date to the payer by due date. Create and transmit due date payment schedules, (ii) create and transmit trust receivable statement balance tables compiled by client, and (iii) provide trust to secondary beneficiaries by secondary beneficiary. 2. The account payable lump-sum trust system according to claim 1, wherein the beneficiary right balance table is created and transmitted to obtain the consent of the payer, the consignor and the second beneficiary. (3) Between (c) and (d), (f) the trust bank receives a discount application from the trustee and / or the second beneficiary, mediates an investor based on the discount application, and commissions the investor. And / or the second beneficiary, and has a device for performing the transfer procedure.
Or, register the beneficiary right transfer consent request sent from the second beneficiary in the system, accept the transfer application, perform the transfer,
3. The account payable lump sum trust system according to claim 1, wherein the beneficiary right transfer information is transmitted to a consignor and / or a second beneficiary. 4. A device according to claim 1, 2 or 3, further comprising a confirmation and correction device between the payer, the client, the second beneficiary and the trust bank.
The described system.