JP4356922B2 - Batch payment processing system and method - Google Patents

Description

  The present invention relates to a collective settlement processing system and method, and more particularly, to a collective settlement processing system and method including a function of managing accounts payable related to a paying company group including a plurality of paying companies.

  A lump-sum payment processing system is known in which a financial institution is interposed between a paying company and a paying company, so that it is possible to omit the issuance of bills and bill settlement operations, which have been done in the past, and to fund them before the due date. (Patent Document 1, Japanese Patent Application No. 2002-70745, etc.).

There are several forms in the lump-sum payment processing system depending on how the accounts receivable or accounts payable are handled, but the basic flow is almost as follows.
(I) A commercial transaction is performed between the paying company and the delivering company, and the delivering company makes a charge request to the paying company.
(ii) The paying company transmits accounts payable details (accounts payable), that is, payment details to the financial institution. The financial institution accepts payment affairs.
(Iii) The delivering company assigns the trade receivables to the financial institution, and the paying company confirms the details of the credit assignment and accepts the assignment. Accordingly, at this point, the payment details and the claim assignment details are the same.
(Iv) The delivery company can apply for a prepayment to the financial institution before the due date.
(V) The paying company can apply for early repayment to the financial institution before the due date.
(Vi) The paying company transfers the current accounts payable to the financial institution on the due date. The financial institution settles the prepayment and deposits the money to the delivery company.
JP 11-96275 A

  In the conventional lump sum payment processing system, when the payer is in the form of a paying company group consisting of a plurality of related companies, the payables of these paying companies are virtually treated as payables of one paying company. Therefore, the delivery company cannot identify the trade receivable held by each paying company.

  The object of the present invention is to understand the breakdown of accounts payable and trade receivables for both the paying company and the paying company when the paying company is a paying company group consisting of a plurality of companies. It is to provide an easy system.

  Specifically, in the lump-sum payment processing system, when the payer is in the form of a paying company group consisting of a plurality of companies, the paying company can identify accounts receivable for the entire paying company group and at the same time, each paying company. It is an object of the present invention to provide a system including a management function for accounts receivable, which can also identify accounts receivable held every time.

  Furthermore, in the lump-sum payment processing system, when the payer is in the form of a paying company group consisting of a plurality of paying companies, the paying company group includes the data processing method for accounts payable related to the lump-sum payment processing, including processing for all companies To provide a system including an account payable management function in which data processing of the paying company group is performed based on this designation. And

  It is another object of the present invention to provide a system including a function for linking payment data of a collective payment processing system with CMS data in a payment company group.

  Furthermore, it aims at providing the method corresponding to the said system.

  In order to achieve the above object, the present invention provides the following systems and methods.

(1) The collective settlement processing system according to claim 1 is the first embodiment of the present invention, and is between a paying company group consisting of a plurality of paying companies each having payables and a paying company having accounts receivable. In order to perform lump sum settlement processing, the accounts payable management server for managing the payment details data of each of the plurality of payment companies, the delivery company server for managing the credit transfer details data of the delivery company, the accounts payable management server, And a collective payment processing server for performing data transmission with the delivery company server, and the collective payment processing server includes the following units.
(A) Receivable assignment consisting of receivable assignment detailed data of each of a plurality of paying companies , which summarizes the receivable assignment detailed data related to each payment detailed data of the plurality of paying companies for the paying company and for the paying company group. Means for receiving statement summary data from the accounts payable management server;
(B) means for storing the received claim assignment summary data in a claim assignment statement data file;
(C) means for transmitting the claim assignment summary data to the delivery company server;
(D) a web server that creates a web page that can be browsed by the supplier company server;
(E) means for displaying the claim assignment summary data read from the claim assignment details data file on the web page;
(F) means for receiving prepayment application data for applying for prepayment of one or more target receivables selected from the displayed receivable assignment details summary data from the delivery company server via the web page;
(G) Means for storing prepaid details data created based on the received prepaid application data in a prepaid details data file

(2) The collective payment processing system according to claim 2 is characterized in that, in claim 1, the collective payment processing server further includes the following means.
(H) Means for displaying on the web page the advance payment details data relating to the one or more subject claims read from the advance payment details data file so as to notify the delivery company that advance payment is to be made.

(3) The collective payment processing system according to claim 3 is characterized in that the collective payment processing server according to claim 1 or 2 further includes the following means.
(I) means for creating due payment data for each of the plurality of payment companies based on the receivable assignment summary data and the advance payment details data and storing the due payment data in a due payment data file;
(J) Means for displaying due date data of each of the plurality of paying companies read from the due date data file on the web page in order to notify the paying company that payment is due in advance.

(4) The collective settlement processing system according to claim 4 is the second embodiment of the present invention, and is between a paying company group consisting of a plurality of paying companies each having an accounts payable and a paying company having accounts receivable. An integrated management server that integrally manages the payment details data of each of the plurality of payment companies, and an account payable that manages the payment details data of each of the plurality of payment companies received from the integrated management server, It has a money management server and a collective settlement processing server for performing data transmission between the accounts payable management server, and the collective settlement processing server has the following means.
(A) The processing related to the receivable assignment details data of each of the plurality of paying enterprises is performed including all enterprise unit data that is the total amount of receivables of all paying enterprises of the paying enterprise group, or Means for registering processing method designating data for designating whether to perform only with each company unit data (b) Summarizing the payment assignment data relating to the payment details data of each of the plurality of payment companies for the delivery company, and the payment company (C) means for receiving, from the accounts payable management server , receivable assignment detailed summary data comprising a plurality of paying enterprises, each of a plurality of paying enterprises, and all enterprise unit data, and received said receivable assignment detailed summary data means for storing in claim assignment item data file (d) is receivable assignment approval the claim assignment item compiled data The Lai said receivables assignment specification compiled data read out from the web server (f) the claim assignment detailed data file to create a web page that can be viewed by along with the means (e) the accounts payable management server to be sent to the accounts payable management server data , Means for displaying on the web page including all company unit data or only each company unit data by referring to the processing method designation data;
(G) means for receiving early reimbursement application data for applying for early reimbursement of one or a plurality of target receivables selected from the displayed receivable assignment details summary data from the accounts payable management server via the web page (h) ) Means for creating early repayment detail data of the one or more target loans based on the received early repayment application data and storing it in the early repayment detail data file

(5) The collective settlement processing system according to claim 5 is characterized in that in claim 4, the collective settlement processing server further includes the following means.
(I) Means for transmitting the early payment details data to the integrated management server including all company unit data

(6) The collective payment processing system according to claim 6 is characterized in that, in claim 4, the collective payment processing server further includes the following means.
(J) Means for transmitting prepaid details data including all company unit data to the integrated management server

(7) The collective payment processing system according to claim 7 is characterized in that, in claim 4, the accounts payable management server has the following means.
Means for creating a form including all company unit data or using only each company unit data based on the receivable transfer statement summary data received from the collective payment processing server

(8) The collective payment processing system according to claim 8 is characterized in that, in claim 4, the accounts payable management server has the following means.
(K) Means for creating due payment data for each of the plurality of paying companies based on the receivable assignment summary data and the early payment details data and storing the due payment data file in the due payment data file. (L) Each of the plurality of paying companies Means for transmitting due date data of each of the plurality of paying companies read from the due date data file including all company unit data to the accounts payable management server in order to charge the due date to the account.

(9) The collective payment processing system according to claim 9 is characterized in that, in claim 8, the accounts payable management server has the following means.
Means for creating a form including all company unit data or using only each company unit data based on due date payment data of each of the plurality of payment companies received from the collective payment processing server

(10) The collective payment processing system according to claim 10 is characterized in that, in claim 8, the collective payment processing server further includes the following units.
(M) Create CMS linkage data for reflecting due date data of each of the plurality of payment companies read from the due payment data file in the loan data between the plurality of payment companies, and store the data in the CMS linkage data file Means (n) Means for transmitting the CMS cooperation data read from the CMS cooperation data file to the CMS server of the payment company group

(11) The collective settlement processing method according to claim 11 is the first embodiment of the present invention, and is between a paying company group consisting of a plurality of paying companies each having payables and a paying company having accounts receivable. In order to perform lump sum settlement processing, the accounts payable management server for managing the payment details data of each of the plurality of payment companies, the delivery company server for managing the credit transfer details data of the delivery company, the accounts payable management server, It is executed by a collective payment processing server that transmits data to and from the delivery company server, and the collective payment processing server has the following steps.
(A) Receivable assignment consisting of receivable assignment detailed data of each of a plurality of paying companies, wherein the receivable assignment detailed data relating to each payment detailed data of the plurality of paying companies is collected for the paying company and the paying company group. Receiving the statement summary data from the accounts payable management server;
(B) storing the received claim assignment details data in a claim assignment details data file;
(C) transmitting receivable transfer statement summary data of each of the plurality of paying companies to the delivery company server;
(D) creating a web page viewable by the supplier company server;
(E) displaying the previous claim assignment summary data read from the claim assignment details data file on the web page;
(F) Receiving prepayment application data for applying for prepayment of one or a plurality of target receivables selected from the summary of receivable assignment details of each of the plurality of paying companies displayed from the delivering company server via the web page And steps to
(G) A step of storing prepaid details data created based on the received prepaid application data in a prepaid details data file

(12) The collective payment processing method according to claim 12 is characterized in that, in claim 11, the collective payment processing server further includes the following steps.
(H) A step of displaying on the web page the prepaid details data relating to the one or more target receivables read from the prepaid details data file in order to notify the delivery company that advance payment is to be made.

(13) The collective payment processing method according to claim 13 is characterized in that, in claim 11 or 12, the collective payment processing server further includes the following steps.
(I) creating due date payment data for each of the plurality of paying companies based on the receivable transfer statement summary data and the advance payment detail data, and storing the due date payment data file; (j) due date payment to the paying company Displaying the due date payment data of each of the plurality of paying companies read from the due date payment data file on the web page to notify in advance that

(14) The collective settlement processing method according to claim 14 is the second embodiment of the present invention, and is between a paying company group consisting of a plurality of paying companies each having an accounts payable and a paying company having accounts receivable. An integrated management server that integrally manages the payment details data of each of the plurality of payment companies, and an account payable that manages the payment details data of each of the plurality of payment companies received from the integrated management server, It is executed by the money management server and the collective payment processing server that transmits data between the accounts payable management server, and has the following steps executed by the collective payment processing server.
(A) The processing related to the receivable assignment details data of each of the plurality of paying enterprises is performed including all enterprise unit data that is the total amount of receivables of all paying enterprises of the paying enterprise group, or Step (b) of registering processing method designating data for designating whether to perform only with each company unit data (b) Summarizing receivable transfer details data relating to each payment details data of the plurality of paying companies for the paying company and summarizes the groups, the claim assignment specification compiled data for claim assignment detailed compiled data composed of each of the claim assignment detailed data and the total enterprise unit data of the plurality of payment company received step (c) receiving from the Accounts payable server storing in claim assignment item data file (d) is the claim assignment item compiled data Kwon step to be sent along with the assignment approval request data to the accounts payable management server (e) the claim assignment specification compiled read from step (f) the claim assignment detailed data file to create a viewable web page by the accounts payable management server The data is displayed on the web page including all company unit data or only each company unit data by referring to the processing method designation data. (G) Select from the displayed receivable transfer statement summary data (H) receiving from the accounts payable management server via the web page the early repayment application data for applying for early repayment of the one or a plurality of the subject loans, the one or more based on the received early repayment application data Create early repayment details data for the subject receivables in the early repayment details data file Step to be stored in the

(15) The collective settlement processing method according to claim 15 further includes the following steps executed by the collective settlement processing server in claim 14.
(I) a step of transmitting the early repayment detail data including all company unit data to the integrated management server

(16) The collective payment processing method according to claim 16 further includes the following steps executed by the collective payment processing server according to claim 14.
(J) A step of transmitting prepaid details data including all company unit data to the integrated management server

(17) The collective payment processing method according to claim 17 is characterized in that, in claim 14, the collective payment processing server further includes the following steps.
The accounts payable management server
A step of creating a form including all company unit data or using only each company unit data based on the receivable transfer statement summary data received from the collective payment processing server

(18) The collective payment processing method according to an eighteenth aspect is further characterized in that, in the fourteenth aspect, the collective payment processing server further includes the following steps.
(K) Creating due date payment data for each of the plurality of paying companies based on the receivable transfer statement summary data and the early payment details data and storing the due date data in a due date data file (l) each of the plurality of paying companies Sending the due payment data of each of the plurality of paying companies read from the due payment data file including all company unit data to the accounts payable management server in order to charge the due payment to the account.

(19) The collective settlement processing method according to claim 19 further includes the following steps executed by the accounts payable management server according to claim 18.
A step of creating a form including all company unit data or using only each company unit data based on due date payment data of each of the plurality of payment companies received from the collective payment processing server.

(20) The collective settlement processing method according to claim 20 further includes the following steps executed by the collective settlement processing server according to claim 18.
(M) Create CMS linkage data for reflecting due date data of each of the plurality of payment companies read from the due payment data file in the loan data between the plurality of payment companies, and store the data in the CMS linkage data file Step (n) The step of transmitting the CMS cooperation data read from the CMS cooperation data file to the CMS server of the payment company group

  In the first and second embodiments of the collective payment processing system and method of the present invention, when the paying company is a paying company group consisting of a plurality of companies, the accounts payable to both the paying company and the paying company. And a system that makes it easy to grasp the breakdown of accounts receivable. The delivery company can identify the receivables for the entire paying company group and at the same time can identify the receivables held for each paying company, thereby enabling more efficient cash management.

  In particular, in the second embodiment, when the payer is in the form of a paying company group consisting of a plurality of paying companies, the paying company group uses the data processing method for accounts payable related to collective settlement processing as a process for all companies. Can be specified in advance, or only the processing of each company unit, and based on this specification, the data processing of the paying company group is performed, so it is possible to manage the accounts payable more efficiently It becomes.

  Furthermore, the function of linking the due date payment data of the collective payment processing system with the CMS data in the payment company group enables more efficient fund management.

(I) Collective payment processing system including management service function for delivery company A first embodiment of the present invention will be described with reference to FIGS. 1 and 2A to 2D. The first embodiment realizes a management service for the delivery company side so that the delivery company can grasp the receivables for the entire paying company group and at the same time can identify the receivables held for each paying company. System.

(I-a) System Configuration FIG. 1 is a diagram schematically and schematically showing a configuration of a collective payment processing system according to the first embodiment and a flow of data processing.

The payment company group 40 includes a plurality of payment companies, for example, a parent company and a plurality of subsidiaries. Each paying company conducts a commercial transaction with the delivery company, thereby generating an accounts payable (account) for the delivery company.

  The accounts payable management server 20 is a computer that collects and manages accounts payable, that is, payment details of each paying company, and performs management on the paying company side with respect to collective settlement, and is installed in, for example, a parent company. The accounts payable management server 20 is connected to the collective payment processing server 10 and the delivery company server 30 via an appropriate communication network. As an example, the accounts payable management server 20 is further connected to payment company terminal computers 41a to 41d installed in each payment company via an appropriate communication network. In addition, regarding the accounts payable generated by the business transaction between the parent company and the delivery company, the parent company itself shall be treated as one paying company.

  The collective payment processing server 10 is a computer that performs data processing related to the collective payment processing between the paying company group 40 and the delivery company, and an appropriate communication network between each of the accounts payable management server 20 and the delivery company server 30. Data processing is performed by transmitting data through the network.

  The delivery company server 30 is a computer installed at the delivery company, and manages the receivable company's side related to accounts receivable and collective settlement for each paying company. The collective settlement processing server 10 and the accounts payable server 20 are connected via an appropriate communication network.

  Hereinafter, the system configuration of each server will be outlined, but the functions related to the present invention will be mainly described.

<Bulk settlement processing server 10>
The collective payment processing server 10 is an appropriate computer, and the control unit 11 includes a CPU and a memory such as a RAM. Furthermore, a storage device 12 that is an auxiliary storage device such as a hard disk, for example, and a communication device 13 for performing data transmission with the accounts payable management server 20 and the delivery company server 30 via an appropriate communication network are provided. Although not shown, an input device such as a keyboard, an output device such as a display and a printing device, and other normal peripheral devices are provided.

  In the collective payment processing server 10, predetermined application software installed in the storage device 12 is read into the memory of the control unit 11 and executed by the CPU, whereby the collective payment processing server 10 performs various processing units 11 a to 11 c described later. And so on. The storage device 12 further stores various data related to the processing of the system in the data files 12a to 12c and the like.

  The communication device 13 includes one or a plurality of communication means for communicating via the Internet, a dedicated line, or the like, and a hardware device such as a router, a modem, a terminal adapter, etc. necessary for each communication means and a predetermined communication protocol. It consists of corresponding communication control software. The specific configuration is not specified. For example, it includes the functions of the web server 13a, mail server 13b, and leased line device 13c.

  The web server 13a has a function of displaying a web page created with HTML document data that can be browsed by the delivery company server 30 or the accounts payable management server 20 via the Internet, for example, and also the delivery company server 30 or the accounts payable management. External software (such as CGI) for interactively transmitting various data to and from the server 20 is included.

The mail server 13b has a function of exchanging electronic mail with the delivery company server 30 or the accounts payable management server 20 via the Internet, and data transmission is also possible by this. For example, an SMTP server. The leased line device 13c has a function of transmitting data to the delivery company server 30 or the accounts payable management server 20 via the leased line.

<Accounts payable management server 20>
The accounts payable management server 20 is an appropriate computer, and the control unit 21 includes a CPU and a memory such as a RAM. Further, for example, a storage device 22 that is an auxiliary storage device such as a hard disk, a payment company terminal 41a to 41d , a collective payment processing server 10 and a delivery company server 30, and a communication device 23 for performing data transmission via an appropriate communication network. It comprises. Although not shown, an input device such as a keyboard, an output device such as a display and a printing device, and other normal peripheral devices are provided.

  In the accounts payable management server 20, predetermined application software installed in the storage device 22 is read into the memory of the control unit 21 and executed by the CPU, whereby the account payable management server 20 performs various processing means 21 a to 21 d described later. And so on. The storage device 22 further stores various data related to the processing of this system in the data files 22a, 22b and the like.

  The communication device 23 includes one or a plurality of communication means for communicating via the Internet, a dedicated line, or the like, and a hardware device such as a router, a modem, and a terminal adapter required by each communication means, and a predetermined communication protocol. It consists of corresponding communication control software. The specific configuration is not specified. For example, the functions of the web server 23a, the mail server 23b, and the leased line device 23c are included.

  The web server 23a has a function of displaying a web page created with HTML document data that can be browsed by the payment company terminal 41a (introducing browser software) via the Internet, for example. Includes external software (CGI or the like) for interactively transmitting various data.

  The mail server 23b has a function of exchanging electronic mails with the payment company terminal 41a and the like, the collective payment processing server 10 and the delivery company server 30 via the Internet, and can also transmit data. For example, an SMTP server. The dedicated line device 23c has a function of transmitting data to and from the collective payment processing server 10 via the dedicated line.

  The accounts payable management server 20 also includes browser software in order to function as a client for browsing the web page created by the collective payment processing server 10.

<Delivery company server 30>
The supplier company server 30 is an appropriate computer, and the control unit 31 includes a CPU and a memory such as a RAM. Furthermore, a storage device 32, which is an auxiliary storage device such as a hard disk, and a communication device 33 for performing data transmission with the collective payment processing server 10 and the accounts payable management server 20 via an appropriate communication network are provided.

  In the delivery company server 30, predetermined application software installed in the storage device 32 is read into the memory of the control unit 31 and executed by the CPU, so that the delivery company server 30 functions as various processing means 31a to 31c described later. To do. The storage device 32 further stores various data related to the processing of this system.

  The communication device 33 includes one or a plurality of communication means for communicating via the Internet or a dedicated line, etc., and a hardware device such as a router, a modem, a terminal adapter, etc. necessary for each communication means and a predetermined communication protocol. It consists of corresponding communication control software. The specific configuration is not specified.

  The display device 34 is a display device that displays a web page for a delivery company created by the collective payment processing server 10, and the web page can be browsed by the browser software 35. When a web page is displayed, data is input from an input device 36 such as a keyboard, and external software of the web server 13a of the collective payment processing server 10 is activated via the web page (techniques such as CGI and ASP). Thus, data can be exchanged with the collective payment processing server 10 interactively.

(I-b) Flow of lump-sum payment processing The flow of lump-sum payment processing in the lump-sum payment processing system of FIG. 1 will be described below. Shall be.

<Commerce>
A commercial transaction is performed between each of the plurality of payment companies in the payment company group and the delivery company (step S1). As a result, the delivery company has accounts receivable for each paying company, and each paying company has accounts payable for the delivering company. The payment management system of each paying company creates payment details data for the payable. Each created payment detail data is prepared so that it can be transmitted from the payment company terminal 41a or the like to the outside.

<Concurrent debt underwriting data processing 21a>
Here, an example will be described in which the payable debt of each paying company of the paying company group is assumed as a joint debtor by the concurrent debt underwriter. The concurrent debt underwriter is, for example, a parent company or a financial institution subsidiary. When this method is adopted, first, each paying company applies to the concurrent debt underwriting company for the concurrent debt underwriting, and the concurrent debt underwriting company accepts the application. In this system, the concurrent debt underwriting data processing means 21a of the accounts payable management server 20 performs this procedure.

  First, in step S2, the payment details data relating to this application is transmitted together with the debt acceptance application data from each payment company terminal 41a or the like to the accounts payable management server 20. The payment details data includes data for identifying the creditor (delivery company) and the debtor (payment company) in addition to the data of the amount of receivable and the due date of the receivable. Upon receipt of these data, the accounts payable management server 20 performs a process of accepting debt acceptance for these claims, and temporarily stores each payment detail data in the storage device 22. Thereafter, debt acceptance data is transmitted to each paying company.

<Payment details data processing 21b>
The accounts payable management server 20 collects the payment details data stored in the storage device 22 on a predetermined date (until the prepaid date of each month) in the collective settlement , and collects a plurality of payment enterprise groups. Preparation data to be sent to the collective payment processing server 10 is made as summary data consisting of the respective payment assignment details data of the paying company . The collected credit assignment details data is stored in the claim assignment details data file 22 a of the storage device 22. On the other hand, the accounts payable management server 20 transmits the collected payment details data to the delivery company server 30 (step S3). The delivery company server 30 receives the payment details data and stores it in the storage device 32.

<Receivable Assignment Data Processing / Receivable Assignment Data Processing 21c>
In step S4, the accounts payable management server 20 transmits to the collective settlement processing server 10 approval data for the credit transfer together with the credit transfer details data read from the storage device 22a.

<Debt Transfer Data Processing 11a>
When the collective settlement processing server 10 receives the claim assignment details data and the approval data from the accounts payable management server 20, the collective settlement processing server 10 stores the claim assignment details data together with the acceptance data in the claim assignment details data file 12a of the storage device 12. The upper diagram of FIG. 2A is a diagram schematically showing an example of the claim assignment details data file 12a in the collective payment processing server 10. For example, there are “receivable number”, “receivable amount”, “prepayable date”, “initial receivable amount”, “management information”, and “remarks” as each information item field, and each stores data. In this example, data of each paying company name is stored in “Remarks”, and these are paying company identification data 101. As a result, it is possible to distinguish the credit transfer details data for each paying company.

  Further, in step S5, the collective payment processing server 10 transmits the receivable assignment details data to the delivery company server 30 together with the approval data. This is to notify the delivery company of the details of the assignment of receivables. As an example of a specific procedure, first, the collective payment processing server 10 notifies the delivery company server 30 by e-mail or the like that preparation for transmission of bond assignment details data is ready. Next, the delivery company server 30 connects to the web page created for the delivery company server, and browses the notice screen of the credit transfer details. The lower diagram of FIG. 2A schematically shows an example of a web page screen created by the collective payment processing server 10 for the delivery company server. The collective payment processing server 10 reads the credit transfer details data of each of a plurality of paying companies from the credit transfer details data file 12a, and creates and displays a web page including predetermined related information. This includes the payment company identification data 102, so that the delivery company can recognize the breakdown within the payment company group.

<Debt Transfer Data Processing 31a>
The delivery company server 30 receives the receivable assignment details data and the approval data from the collective payment processing server 10. For example, the delivery company server 30 transmits download request data from the web page shown in the lower part of FIG. 2A, and in response thereto, the collective payment processing server 10 transmits the bond assignment details data and its approval data. Thereafter, the delivery company server 30 stores the received receivable assignment details data together with the approval data in a receivable assignment details data file (not shown) in the storage device 32.

<Prepayment data processing 31b, 11b>
There are two types of prepaid applications by a supplier in a lump sum settlement: a regular discount method and an occasional discount method.

  The delivery company server 30 transmits the prepaid application data to the collective payment processing server 10 in step S6. As an example of a specific procedure, the delivery company server 30 connects to a web page created for the delivery company server and browses a prepaid application screen. The lower diagram of FIG. 2B schematically shows an example of a web page screen created by the collective payment processing server 10 for the delivery company server.

  Here, it is assumed that the collective payment processing server 10 stores prepaid details data in a prepaid details data file 12b as shown in the upper diagram of FIG. 2B. The advance payment details data file 12b can be created from the claim assignment details data file 12a, and also includes payment company identification data 103. For example, each information item field includes “target flag”, “receivable number”, “prepaid date”, “receivable amount”, “prepaid receivable balance”, “prepaid application amount”, and “remarks”. Stored. In this example, data of each paying company name is stored in “Remarks”, and these are paying company identification data 103. This makes it possible to distinguish the advance payment detail data for each paying company.

  The collective payment processing server 10 displays the advance payment details data for each of the plurality of payment companies read from the advance payment details data file 12b on the web page. This includes the payment company identification data 104, so the delivery company can recognize the breakdown within the payment company group.

  The delivery company server 30 can transmit the prepaid application data to the collective payment processing server 10 from the prepaid application screen in the lower diagram of FIG. 2B. For example, after clicking on the target check box 105 of one or a plurality of target receivables desired to be paid in advance on the screen with a mouse or the like, the “Send” button is clicked. Thereby, the advance payment application data is transmitted to the collective payment processing server 10 via the web page. The prepayment application data includes data of one or more selected target receivables and a prepayment desired date. On the prepayment application screen, by clicking the “prepayment simulation” button, the collective settlement processing server 10 calculates a prepayment amount based on a discount rate, an interest rate, etc., and displays the result on a web page. Can be included.

  When the collective payment processing server 10 receives the prepaid application data from the delivery company server 30 via the web page, the collective settlement processing server 10 performs a process of accepting the prepaid application for the selected one or more target receivables. Specifically, the flag of the selected target bond is set out of the target flags provided for each prepaid detail data in the prepaid detail data file 12b in the upper diagram of FIG. 2B. The prepaid detailed data stored in the prepaid detailed data file 12b in this way is appropriately updated based on the prepaid application data.

  Further, the collective payment processing server 10 transmits prepayment notice data to the delivery company server 30 in step S7 prior to prepayment (transfer). As an example of a specific procedure, first, the collective payment processing server 10 notifies the delivery company server 30 by e-mail or the like that preparation for transmission of prepaid notification data is ready. Next, the delivery company server 30 connects to a web page created for the delivery company server and browses a prepaid notification screen. The lower diagram of FIG. 2C schematically shows an example of a web page screen created by the collective payment processing server 10 for the delivery company server. The collective payment processing server 10 reads the advance payment details data with the target flag set from the advance payment details data file 12b shown in the upper part of FIG. 2C, and creates and displays a web page including predetermined related information. Since the payment company identification data 108 is included in this, the delivery company side can recognize which payment company in the payment company group is the receivable.

<Due Date Payment Data Processing 11c, 31c, 21d>
The collective payment processing server 10 transmits due date payment notification data to the delivery company server 30 in step S8 prior to due date payment (transfer). As an example of a specific procedure, first, the collective payment processing server 10 notifies the delivery company server 30 by e-mail or the like that it is ready to send due payment notification data. Next, the delivery company server 30 connects to the web page created for the delivery company server, and browses the due date notification screen. The lower part of FIG. 2D schematically shows an example of a web page screen created by the collective payment processing server 10 for the delivery company server.

  Here, it is assumed that the collective payment processing server 10 stores due date data in due date data file 12c as shown in the upper diagram of FIG. 2D. The due date payment data file 12c can be created from the claim assignment details data file 12a and the advance payment details data file 12b, and includes payment company identification data 109. For example, there are “receivable number”, “receivable amount”, “initial receivable amount”, “prepaid execution amount”, “management information”, and “remarks” as each information item field, and each stores data. In this example, data of each paying company name is stored in “Remarks”, and these are paying company identification data 109. This makes it possible to distinguish due date payment data for each paying company.

  The collective payment processing server 10 reads due date data of each of a plurality of paying companies from the due date data file 12c shown in the upper diagram of FIG. 2D, and creates and displays a web page including predetermined related information. Since the payment company identification data 110 is included in this, the payment company can recognize which payment company in the payment company group is the receivable.

  Further, the collective payment processing server 10 transmits due date payment request data together with due date payment data to the accounts payable management server 20 in step S9. As an example of a specific procedure, first, the collective payment processing server 10 notifies the accounts payable management server 20 that preparation for transmission of due date payment request data is made by e-mail or the like. Next, the accounts payable management server 20 connects to a web page created for the accounts payable management server and browses a due date billing screen. Due date data can be downloaded via this web page. Accounts payable management server 20 stores the received due date payment data and due date payment request data in due date data file 22b. Thereafter, the accounts payable management server 20 performs due date settlement processing in step S10. The actual settlement is performed by transfer, and notification data regarding settlement is transmitted to the collective settlement processing server 10.

  Further, in step S11, the accounts payable management server 20 transmits due payment request data together with the due date payment data to each paying company terminal 41a and the like, and in step S12, notification data on due date settlement from each paying company. Receive.

(II) Batch Settlement Processing System Including Management Service Function for Payment Company Group A second embodiment of the present invention will be described with reference to FIGS. 3 and 4A to 4F. The second embodiment specifies and registers in advance one of the data processing methods as to whether the data processing related to the lump sum settlement processing is performed including data for all paying company units or only for each paying company unit data. It is a collective payment processing system that realizes a management service for the payment company side that performs data processing of the payment company group based on this designation.

(II-a) System Configuration FIG. 3 is a diagram schematically and schematically showing the configuration of the collective payment processing system according to the second embodiment and the flow of data processing.

The payment company group integrated management server 80 is a server that integrally manages accounts payable (payables) of a payment company group composed of a plurality of payment companies, and is preferably an ERP system that is an integrated business management system. Realized as a function. Although not shown, the payment company group is composed of a plurality of payment companies, and includes, for example, a head office and a plurality of branch offices, or a parent company and a plurality of subsidiaries or affiliates thereof. Each paying company conducts a business transaction with a delivery company, thereby generating an accounts payable for the delivery company. Incidentally, the payment company group has CMS server 90 for performing integrated management for funds luck each company in the group.

The accounts payable management server 50 is a computer that receives the accounts payable of each paying company, that is, payment details, from the integrated management server 80 and manages the paying company on the basis of the collective settlement based on this. The accounts payable management server 50 is connected to the collective payment processing server 60 via an appropriate communication network.

  The lump-sum payment processing server 60 is a computer that performs data processing related to lump-sum payment processing between the paying company group and the delivery company, and an appropriate communication network is provided between each of the accounts payable management server 50 and the delivery company server 70. Data processing is performed by transmitting data through the network.

The delivery company server 70 is a computer installed at the delivery company, and manages the receivable company side and the collective settlement on the delivery company side for each paying company. It is connected to the collective payment processing server 60 via an appropriate communication network.

  Hereinafter, the system configuration of each server will be outlined, but the functions related to the present invention will be mainly described.

<Bulk settlement processing server 60>
The collective payment processing server 60 is an appropriate computer, and the control unit 61 includes a CPU and a memory such as a RAM. Further, the communication device 63 includes a storage device 62 that is an auxiliary storage device such as a hard disk, and performs data transmission with the accounts payable management server 50, the delivery company server 70, and the integrated management server 80 via an appropriate communication network. It comprises. Although not shown, an input device such as a keyboard, an output device such as a display and a printing device, and other normal peripheral devices are provided.

  In the collective payment processing server 60, predetermined application software installed in the storage device 62 is read into the memory of the control unit 61 and executed by the CPU, whereby the collective payment processing server 60 performs various processing means 61a to 61f described later. Function as. The storage device 62 further stores various data related to the processing of this system in the data files 62a to 62f.

  The communication device 63 includes one or a plurality of communication means for communicating via the Internet or a dedicated line, and a hardware device such as a router, a modem, and a terminal adapter required by each communication means and a predetermined communication protocol. It consists of corresponding communication control software. The specific configuration is not specified. For example, the functions of the web server 63a, the mail server 63b, and the leased line device 63c are included.

  The web server 63a has a function of displaying a web page created with HTML document data that can be browsed by the delivery company server 70, the accounts payable management server 50, or the integrated management server 80 via the Internet, for example. 70, and external software (CGI or the like) for interactively transmitting various data with the accounts payable management server 50 or the integrated management server 80.

  The mail server 63b has a function of exchanging e-mails with the delivery company server 37, the accounts payable management server 50, and the integrated management server 80 via the Internet, and can also transmit data. For example, an SMTP server. The dedicated line device 63c has a function of transmitting data to the delivery company server 70, the accounts payable management server 50, and the integrated management server 80 via the dedicated line.

<Accounts payable management server 50>
The accounts payable management server 50 is an appropriate computer, and the control unit 51 includes a CPU and a memory such as a RAM. In addition, a storage device 52, which is an auxiliary storage device such as a hard disk, and a collective settlement processing server 60 and a communication device 56 for performing data transmission via an appropriate communication network are provided. It includes an input device 55 such as a keyboard, a display device 53 such as a display, an output device such as a printing device, and other ordinary peripheral devices.

  In the accounts payable management server 50, predetermined application software installed in the storage device 52 is read into the memory of the control unit 51 and executed by the CPU, whereby the account payable management server 50 performs various processing means 51 a to 51 d described later. Function. The storage device 52 further stores various data related to the processing of the present system in the data files 52a, 52b and the like.

  The communication device 56 includes one or a plurality of communication means for communicating via the Internet, a dedicated line, or the like, and a hardware device such as a router, a modem, and a terminal adapter required by each communication means and a predetermined communication protocol. It consists of corresponding communication control software. The specific configuration is not specified. For example, it includes functions of a web server, a mail server, and a dedicated line device. The web server has a function of displaying a web page created with HTML document data that can be browsed by the integrated management server 80 via the Internet, for example, and external software (CGI) for performing various data transmission interactively. Etc.). The mail server has a function of exchanging electronic mails with the integrated management server 80 and the collective payment processing server 60 via the Internet, and data transmission is also possible by this. For example, SMTP and POP servers. The dedicated line device has a function of transmitting data between the integrated management server 80 and the collective payment processing server 60 via the dedicated line.

  The accounts payable management server 50 also includes browser software in order to function as a client for browsing the web page created by the collective payment processing server 60.

<Delivery company server 70>
The delivery company server 70 is the same computer as the delivery company server 30 (FIG. 1) in the first embodiment described above, and performs the same data processing in the second embodiment. Therefore, the data processing between the delivery company server 70 and the collective payment processing server 60 is almost the same as the collective payment processing system in the first embodiment described above, and a description thereof will be omitted.

<Integrated management server 80>
The integrated management server 80 is an appropriate computer, and the control unit 81 includes a CPU and a memory such as a RAM. Furthermore, the communication apparatus 83 for performing data transmission with the memory | storage device 82 which is auxiliary storage apparatuses, such as a hard disk, the accounts payable management server 50, and the lump sum payment processing server 60 via an appropriate communication network is provided. Furthermore, an input device such as a keyboard, a display device such as a display, an output device such as a printing device, and other normal peripheral devices are provided.

  In the integrated management server 80, predetermined application software installed in the storage device 82 is read into the memory of the control unit 81 and executed by the CPU, whereby the integrated management server 80 functions as various processing units 81a to 81c described later. . The storage device 82 further stores various data related to the processing of this system in each data file 82a and the like.

<CMS server 90>
The CMS server 90 of the paying company group in FIG. 3 performs integrated management of the fund operation of each company in the paying company group. For example, fund management for each company, borrowing management from financial institutions, and lending management between paying companies.

  The CMS server 90 is an appropriate computer, and the control unit 91 includes a CPU and a memory such as a RAM. In addition, a storage device 92 that is an auxiliary storage device such as a hard disk, for example, and a collective payment processing server 60 and a communication device 93 for performing data transmission via an appropriate communication network are provided. Furthermore, an input device such as a keyboard, a display device such as a display, an output device such as a printing device, and other normal peripheral devices are provided.

  In the CMS server 90, predetermined application software installed in the storage device 92 is read into the memory of the control unit 91 and executed by the CPU, whereby the CMS server 90 functions as various processing means 91a described later. The storage device 92 further stores various data related to the processing of this system in each data file 92a and the like.

(II-b) Flow of Collective Payment Processing Hereinafter, the flow of the collective payment processing in the collective payment processing system of FIG. 3 will be described, but this is an example and includes a modification by a known technique.

<Commerce>
A commercial transaction is performed between each of the plurality of payment companies in the payment company group and the delivery company (step S31). As a result, the delivery company has accounts receivable for each paying company, and each paying company has accounts payable for the delivering company.

<Payment details data processing 81a>
The integrated management system 80 creates the payment details data of the accounts payable of each payment company in the payment company group, and stores it in the payment details data file 82a of the storage device 82 (payment details data processing 81a). Next, in step S <b> 32, payment details data of each of a plurality of payment companies is transmitted from the integrated management system 80 to the accounts payable management server 50. The payment details data includes data for identifying the creditor (delivery company) and the debtor (payment company) in addition to the data of the amount of receivable and the due date of the receivable.

<Payment details data processing 51a>
The accounts payable management server 50 stores the payment details data from the integrated management server 80 in the storage device 22. Next, in step 33, the accounts payable management server 50 reads the payment details data of each of the plurality of paying companies from the storage device 22 , collects the paying companies and collects the paying company groups, and performs predetermined settlement in the collective settlement. On the day (until the prepaid day of each month), it is transmitted to the collective settlement processing server 60 as summary data consisting of the individual loan assignment details data of a plurality of paying companies . This transmission is transmitted including “total enterprise unit data” which is the total amount data of the amounts of receivables of all paying companies, in addition to the receivable assignment details data of each paying enterprise.

<Payment company group registration process 61a>
Here, processing performed in advance by the collective payment processing server 60 will be described. The collective payment processing server 60 performs a process of registering in advance the data processing method designated by the paying company group in the collective payment process, that is, a process of storing the data processing method in the payment company group registration file 62 a of the storage device 62 . The following two data processing methods can be specified.
(i) Data processing method that includes all enterprise unit data in addition to each enterprise unit data
(ii) A data processing method that includes only data for each company

  FIG. 4A is a diagram schematically showing an example of the payment company group registration file 62a. The information item fields include at least “payment company group name”, “payment company name”, and “processing method designation data”. In the “processing method designation data” field, data designating one of the data processing methods (i) or (ii) is stored. The collective payment processing server 60 refers to the payment company group registration file 62a in an aspect where the collective payment processing is necessary.

<Debt transfer data processing 61b>
When the collective settlement processing server 60 receives the claim assignment details data from the accounts payable management server 50 in step S33, the collective settlement processing server 60 stores the claim assignment details data in the claim assignment details data file 62b of the storage device 62. The upper diagram of FIG. 4B is a diagram schematically showing an example of the claim assignment details data file 62b. For example, there are “receivable number”, “receivable amount”, “prepayable date”, “initial receivable amount”, “management information”, and “remarks” as each information item field, and each stores data. In this example, data of each paying company name is stored in “Remarks”, and these are paying company identification data 201. As a result, it is possible to distinguish the credit transfer details data for each paying company. In this table format file, each company unit data 202 is stored in the first to fourth lines, and all company unit data 203 consisting of the total amount of receivables for each company is stored in the bottom line.

  Next, the collective payment processing server 60 transmits the claim assignment acceptance request data together with the claim assignment details data including the entire company unit data to the accounts payable management server 50 in step S34. As an example of a specific procedure, first, the collective payment processing server 60 notifies the accounts payable management server 50 by e-mail or the like that preparation for transmission of the claim assignment approval request data is completed. Next, the accounts payable management server 50 connects to a web page created for the accounts payable management server, and browses an acceptance request (confirmation) screen for receivable assignment. The central view of FIG. 4B schematically shows an example of a web page screen created by the collective payment processing server 60 for the accounts payable management server. The collective settlement processing server 60 reads the credit transfer details data of each company and all companies from the claim transfer details data file 62b, and creates and displays a web page including predetermined related information. This includes payment company identification data 204, so that the payment company can recognize the breakdown within the payment company group. Further, in addition to each company unit data 205, all company unit data 206 is also displayed.

<Receivable Assignment Data Processing / Receivable Assignment Data Processing 51b>
The accounts payable management server 50 receives from the collective payment processing server 60 the claim assignment details data including all company unit data and the approval data. For example, the download request data is transmitted by clicking the “Download” button from the web page in the central diagram of FIG. 4B, and the transfer request data including all company unit data from the collective payment processing server 60 and the approval thereof. Request data is sent.

  The accounts payable management server 50 stores the downloaded claim assignment details data in the claim assignment details data file 52 a of the storage device 52. Accounts payable management server 50 employs a data processing method adapted to the paying enterprise group, and accordingly outputs one of two types of credit transfer confirmations shown in the lower diagram of FIG. In the data processing method indicated by reference numeral 51b- (1), a bond assignment confirmation is output for each company using only the data for each company. In the data processing method indicated by reference numeral 51b- (2), a bond transfer confirmation document including all company unit data is output.

  Furthermore, the accounts payable management server 50 transmits approval data for the transfer of receivables to the collective settlement processing server 60 in step S35. The collective settlement processing server 60 stores the received credit assignment approval data in the claim assignment details data file 62b of the storage device 62.

<Early payment data processing 51c, 61c>
In lump sum settlement, early payment may be made by the paying company. Accounts payable management server 50 transmits early payment application data to batch settlement processing server 60 in step S36. As an example of a specific procedure, the accounts payable management server 50 connects to a web page created for the accounts payable management server and browses an early payment application screen. 4C and 4D schematically show an example of a web page screen created by the collective payment processing server 60 for the accounts payable management server. The lower diagram of FIG. 4C is a web page created by the collective settlement processing server 60 referring to the payment company group registration file 62a and determining that a processing method including all company unit data is designated. . Accordingly, in addition to each company unit data 210, all company unit data 211 is displayed. On the other hand, the lower diagram in FIG. 4D is a web page created by determining that the processing method for only the company unit data is designated. Therefore, only each company unit data 210 is displayed.

  Here, it is assumed that the collective payment processing server 60 stores the early payment details data in the early payment details data file 62c as schematically shown in the upper diagrams of FIGS. 4C and 4D. The early payment details data file 62c can be created from the claim assignment details data file 62b, and includes payment company identification data 209. For example, each information item field includes “target flag”, “credit number”, “settlement date”, “initial credit amount”, “management information”, and “remarks”, and each stores data. In this example, data of each paying company name is stored in “Remarks”, and these are paying company identification data 209. Thereby, early payment details data for each paying company can be distinguished. In this table format file, each company unit data 207 is stored in the first to fourth lines, and all company unit data 208 consisting of the total amount of receivables for each company is stored in the bottom line.

  The collective settlement processing server 60 displays the early repayment details data for each of the plurality of payment companies read from the early repayment details data file 62c on the web page. Since the payment company identification data 212 is included in this, the payment company side can recognize the breakdown within the payment company group.

  The accounts payable management server 50 can transmit the early repayment application data to the collective settlement processing server 60 from the early repayment application screen shown in the lower diagram of FIG. 4C or 4D. For example, the target check box of one or a plurality of target loans for which early reimbursement is desired on the screen is clicked with a mouse or the like, and the “Send” button is clicked. As a result, the early payment application data is transmitted to the collective payment processing server 60 via the web page. The early repayment application data includes data of the selected one or more target bonds.

  When the collective settlement processing server 60 receives the early repayment application data from the accounts payable management server 50 via the web page, the collective settlement processing server 60 performs a process of accepting the early repayment application for the selected one or more target receivables. Specifically, among the target flags provided for each early payment details data file 62c in the upper right payment details data file 62c in FIG. 4C or FIG. The early repayment details data stored in the early repayment details data file 62c as described above is appropriately updated based on the early repayment application data.

  Next, the collective payment processing server 60 transmits the early repayment details data read from the early repayment details data file 62c to the integrated management server 80 including all company unit data in step S37. When the integrated management server 80 receives the early repayment details data, the integrated management server 80 performs off-balance processing of the corresponding accounts payable (early repayment data processing 81b).

<Prepayment data processing 61d>
The prepaid data processing 61d by the collective payment processing server 60 is performed with the delivery company server 70 in the same manner as in the first embodiment. The collective payment processing server 60 stores the advance payment details data in the advance payment details data file 62d. Further, in step S38, the collective payment processing server 60 transmits the advance payment details data read from the advance payment details data file 62d to the integrated management server 80 including all company unit data. When the integrated management server 80 receives the prepayment detail data, the integrated management server 80 performs a process of accruing the corresponding payable (prepayment data processing 81c).

<Due Date Payment Data Processing 51d, 61e>
In step S39, the collective payment processing server 60 transmits due date payment request data together with due date data of each of a plurality of paying companies including all company unit data to the accounts payable management server 50 for due date payment. As an example of the procedure, first, the collective payment processing server 60 notifies the accounts payable management server 50 by e-mail or the like that preparation for transmission of due payment request data is ready. Next, the accounts payable management server 50 connects to a web page created for the accounts payable management server, and browses a billing screen for due payment. The central view of FIG. 4E schematically shows an example of a web page screen created by the collective payment processing server 60 for the accounts payable management server.

  Here, it is assumed that the collective payment processing server 60 stores due date payment data in the due date payment data file 62e as schematically shown in the upper diagram of FIG. 4E. The due date payment data file 62e can be created from the claim assignment details data file 62b and the early payment details data file 62c, and includes payment company identification data 215. For example, there are “receivable number”, “receivable amount”, “initial receivable amount”, “early repayment amount”, “management information”, and “remarks” as each information item field, and each stores data. In this example, data of each paying company name is stored in “Remarks”, and these are paying company identification data 215. This makes it possible to distinguish due date payment data for each paying company. In this table format file, each company unit data 213 is stored in the first to fourth lines, and all company unit data 214 consisting of the total amount of receivables for each company is stored in the bottom line.

  The collective payment processing server 60 reads due date data of each of a plurality of paying companies from the due date data file 62e shown in the upper diagram of FIG. 4E, and creates and displays a web page including predetermined related information. Since the payment company identification data 215 is also included in this, the delivery company side can recognize which payment company in the payment company group is the receivable. Further, in addition to each company unit data 216, all company unit data 217 is also displayed.

  Accounts payable management server 50 can download due payment data via this web page. The accounts payable management server 50 stores the received due date payment data and due date payment request data in the due date data file 52b.

  The accounts payable management server 50 outputs one of the two due payment invoices shown in the lower diagram of FIG. 4E according to the data processing method of the paying company group. In the data processing method indicated by reference numeral 51d- (1), a due payment invoice is output for each company using only the company unit data. In the data processing method indicated by reference numeral 51d- (2), a due payment invoice including all company unit data is output.

  Note that the fee billing data for each paying company is processed in exactly the same way as the above-mentioned due date billing request data, and there are two forms (whether it includes all company unit data or only each company unit data). Is output.

  Thereafter, the accounts payable management server 50 performs due date payment settlement processing in step S40. Since payment is made by transferring all paying companies together, notification data related to payment is sent to the collective payment processing server 60 including all company unit data.

(III) Collective payment processing system including cooperation service function with CMS server of payment company group As an additional function of the system of the second embodiment, a cooperation function with CMS server of payment company group can be incorporated.

<CMS cooperation data processing 91a>
The CMS server 90 stores loan data between a plurality of paying companies in an inter-company loan data file 92a in the storage device 92, and manages this. On the other hand, the collective payment processing server 60 shares this loan data (not shown). The collective payment processing server 60 reads the above-mentioned due date payment data from the due date payment data file 62e, and creates CMS linkage data for reflecting the due date payment data in the loan data between payment companies. The created CMS cooperation data is stored in the CMS cooperation data file 62f.

  Further, in step 41, the collective payment processing server 60 transmits the CMS cooperation data read from the CMS cooperation data file 62f to the CMS server of the paying company group.

  The CMS server 90 updates the intercompany loan data file 92a with the received CMS cooperation data (CMS cooperation data processing 91a).

It is the figure which showed roughly the structure of the collective payment processing system by 1st Embodiment, and the flow of data processing roughly. The upper diagram is a diagram schematically showing an example of the credit assignment details data file 12a. 1 schematically shows an example of a web page screen created by the collective payment processing server 10 for a delivery company server. The upper figure is a diagram schematically showing an example of the advance payment details data file 12b. The following diagram schematically shows an example of a web page screen created by the collective payment processing server 10 for the delivery company server. The upper figure is a diagram schematically showing an example of the advance payment details data file 12b. The following diagram schematically shows an example of a web page screen created by the collective payment processing server 10 for the delivery company server. The upper figure is a diagram schematically showing an example of the due date payment data file 12c. The following diagram schematically shows an example of a web page screen created by the collective payment processing server 10 for the delivery company server. It is the figure which showed roughly the structure of the lump sum payment processing system by 2nd Embodiment, and the flow of data processing roughly. It is the figure which showed typically an example of the payment company group registration file 62a. The upper diagram is a diagram schematically showing an example of the credit assignment details data file 62b. The central diagram schematically shows an example of a web page screen created by the collective payment processing server 60 for the accounts payable management server. The figure below is a diagram schematically showing the form output method for two forms of credit transfer confirmation. The upper diagram is a diagram schematically showing an example of the early payment details data file 62c. The following diagram schematically shows an example of a web page screen created by the collective payment processing server 60 for the accounts payable management server. The upper diagram is a diagram schematically showing an example of the early payment details data file 62c. The following diagram schematically shows an example of a web page screen created by the collective payment processing server 60 for the accounts payable management server. The upper diagram is a diagram schematically showing an example of the due date payment data file 62c. The central diagram schematically shows an example of a web page screen created by the collective payment processing server 60 for the accounts payable management server. The figure below is a diagram that schematically shows the form output method for two due payment invoices.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 Collective settlement processing server 11 Control part 11a Claim transfer details data processing means 11b Prepayment data processing means 11c Due date payment data processing means 12 Storage device 12a Claim transfer details data file 12b Advance payment details data file 12c Due date payment data file 13 Communication device 13a Web Server 13b Mail server 13c Dedicated line device 20 Accounts payable management server 21 Control unit 21a Coexistent debt underwriting data processing means 21b Payment details data processing means 21c Claim transfer data / acceptance data processing means 21d Due date payment data processing means 22 Storage device 22a Claims Assignment details data file 22b Due date data file 23a Web server 23b Mail server 23c Dedicated line device 30 Delivery company server 31 Control unit 31a Claim assignment details data processing means 1b Prepaid data processing means 31c Due date data processing means 32 Storage device 33 Communication device 34 Display device 35 Browser software 36 Input device 40 Payment company group 41a, 41b, 41c, 41d Member company terminal 50 Accounts payable management server 51 Control unit 51a Payment Detailed data processing means 51b Claim transfer data / acceptance data processing means 51c Early payment data processing means 51d Due date data processing means 52 Storage device 52a Claim transfer details data file 52b Due date data file 53 Display device 54 Browser software 55 Input device 56 Communication Device 60 Collective settlement processing server 61 Control unit 61a Payment company group registration processing means 61b Claim transfer statement data processing means 61c Early payment data processing means 61d Prepayment data processing means 61 Due date payment data processing means 61f CMS linkage data processing means 62 Storage device 62a Payment company group registration file 62b Claim transfer details data file 62c Early payment details data file 62d Prepayment details data file 62e Due payment data file 62f CMS linkage data file 63 Communication device 63a Web server 63b Mail server 63c Dedicated line device 70 Delivery company server 80 Payment company group purchasing management server 81 Control unit 81a Payment details data processing means 81b Early payment data processing means 81c Prepayment data processing means 82 Storage device 82a Payment details data file 83 Communication device 90 Payment company group CMS server 91 Control unit 91a CMS linkage data processing means 92 Storage device 92a Inter-company loan data file 93 Equipment

Claims (20)

Accounts payable management for managing the payment details data of each of the plurality of paying companies in order to perform a lump sum settlement process between a paying company group consisting of a plurality of paying companies each having an accounts payable and a paying company having an accounts receivable. In a collective settlement processing system comprising a server, a delivery company server that manages the credit transfer details data of the delivery company, and a collective settlement processing server that performs data transmission between the accounts payable management server and the delivery company server, The collective payment processing server is
(A) Receivable assignment consisting of receivable assignment detailed data of each of a plurality of paying companies, wherein the receivable assignment detailed data relating to each payment detailed data of the plurality of paying companies is collected for the paying company and the paying company group. Means for receiving statement summary data from the accounts payable management server;
(B) means for storing the received claim assignment summary data in a claim assignment statement data file;
(C) means for transmitting the claim assignment summary data to the delivery company server;
(D) a web server that creates a web page that can be browsed by the supplier company server;
(E) means for displaying the claim assignment summary data read from the claim assignment details data file on the web page;
(F) means for receiving prepayment application data for applying for prepayment of one or more target receivables selected from the displayed receivable assignment details summary data from the delivery company server via the web page;
(G) A collective settlement processing system comprising: means for storing prepaid detailed data created based on the received prepaid application data in a prepaid detailed data file. The collective payment processing server further includes:
(H) means for displaying on the web page the prepaid details data relating to the one or more target receivables read from the prepaid details data file so as to notify the delivery company in advance that prepayment will be made; The collective payment processing system according to claim 1. The collective payment processing server further includes:
(I) means for creating due payment data for each of the plurality of payment companies based on the receivable assignment summary data and the advance payment details data and storing the due payment data in a due payment data file;
(J) having means for displaying due date data of each of the plurality of paying companies read from the due date data file on the web page in order to notify the paying company that payment is due in advance. The collective payment processing system according to claim 1 or 2, characterized in that. Integrated management that integrates and manages the payment details of each of the plurality of paying companies in order to perform a lump sum settlement process between a paying company group consisting of a plurality of paying companies each having payables and a paying company having accounts receivable. A server, an accounts payable management server that manages the payment details data of each of the plurality of payment companies received from the integrated management server, and a collective settlement processing server that transmits data between the accounts payable management server In the collective payment processing system, the collective payment processing server includes:
(A) The processing related to the receivable assignment details data of each of the plurality of paying enterprises is performed including all enterprise unit data that is the total amount of receivables of all paying enterprises of the paying enterprise group, or Means for registering processing method designation data for designating whether to perform only with each company unit data,
(B) the compilation for claim assignment statement data deliveries company according to each of the payment data of a plurality of payment company, and summarizes the payment company groups, each claim assignment detailed data and the total enterprise-wide multiple payment companies It means for receiving a claim assignment detailed compiled data composed of data from the accounts payable management server,
(C) means for storing the received claim assignment summary data in a claim assignment statement data file;
(D) means for transmitting said claim assignment specification compiled data with claim assignment authorization request data to the Accounts Payable server,
(E) a web server that creates a web page viewable by the accounts payable management server;
(F) Displaying the receivable assignment summary data read from the receivable assignment details data file on the web page, including all enterprise unit data or only each enterprise unit data by referring to the processing method designation data Means to
(G) means for receiving early repayment application data for applying for early repayment of one or a plurality of target receivables selected from the displayed receivable assignment summary data from the accounts payable management server via the web page;
(H) A collective settlement processing system comprising means for creating early repayment detail data of the one or more target receivables based on the received early repayment application data and storing it in an early repayment detail data file. The collective payment processing server further includes:
5. The collective settlement system according to claim 4, further comprising: (i) means for transmitting the early reimbursement detailed data including all company unit data to the integrated management server. The collective payment processing server further includes:
(J) The collective payment system according to claim 4, further comprising means for transmitting prepaid details data including all company unit data to the integrated management server. The accounts payable management server
5. The apparatus according to claim 4, further comprising means for creating a form including all company unit data or using only each company unit data based on the receivable assignment summary data received from the collective payment processing server. Batch payment processing system. The collective payment processing server further includes:
(K) means for creating due payment data for each of the plurality of payment companies based on the receivable assignment summary data and the early repayment statement data, and storing the due payment data in a due payment data file;
(L) In order to request due payment to each of the plurality of paying companies, the payables including all company unit data including due date data of each of the plurality of paying companies read from the due payment data file. 5. The collective payment processing system according to claim 4, further comprising means for transmitting to a management server. The accounts payable management server
The system according to claim 1, further comprising means for creating a form including all enterprise unit data or using only each enterprise unit data based on due date payment data of each of the plurality of enterprises received from the collective payment processing server. The collective payment processing system according to 8. The collective payment processing server further includes:
(M) Create CMS linkage data for reflecting due date data of each of the plurality of payment companies read from the due payment data file in the loan data between the plurality of payment companies, and store the data in the CMS linkage data file Means,
9. The collective payment processing system according to claim 8, further comprising: (n) means for transmitting the CMS cooperation data read from the CMS cooperation data file to a CMS server of the payment company group. Accounts payable management for managing the payment details data of each of the plurality of paying companies in order to perform a lump sum settlement process between a paying company group consisting of a plurality of paying companies each having an accounts payable and a paying company having an accounts receivable. In a collective settlement processing method executed by a server, a delivery company server that manages the transfer details data of the delivery company, and a collective settlement processing server that performs data transmission between the accounts payable management server and the delivery company server The collective payment processing server is
(A) Receivable assignment consisting of receivable assignment detailed data of each of a plurality of paying companies , which summarizes the receivable assignment detailed data related to each payment detailed data of the plurality of paying companies for the paying company and for the paying company group. Receiving the statement summary data from the accounts payable management server;
(B) storing the received claim assignment details data in a claim assignment details data file;
(C) transmitting receivable transfer statement summary data of each of the plurality of paying companies to the delivery company server;
(D) creating a web page viewable by the supplier company server;
(E) displaying the previous claim assignment summary data read from the claim assignment details data file on the web page;
(F) Receiving prepayment application data for applying for prepayment of one or a plurality of target receivables selected from the summary of receivable assignment details of each of the plurality of paying companies displayed from the delivering company server via the web page And steps to
(G) storing the advance payment details data created based on the received advance payment application data in a advance payment details data file. The collective payment processing server further includes:
(H) displaying in advance the prepaid details data relating to the one or more target receivables read from the prepaid details data file on the web page in order to notify the delivery company that advance payment is to be made. 12. The collective payment processing method according to claim 11. The collective payment processing server further includes:
(I) creating due date payment data for each of the plurality of paying companies based on the claim assignment summary data and the advance payment details data, and storing the due date payment data file;
(J) displaying the due date data of each of the plurality of paying companies read from the due date data file on the web page in order to notify the paying company that payment is due in advance. 13. The collective payment processing method according to claim 11 or 12, wherein: Integrated management that integrates and manages the payment details of each of the plurality of paying companies in order to perform a lump sum settlement process between a paying company group consisting of a plurality of paying companies each having payables and a paying company having accounts receivable. Executed by a server, an accounts payable management server that manages payment details data of each of the plurality of payment companies received from the integrated management server, and a collective settlement processing server that transmits data between the accounts payable management server In the collective payment processing method, the collective payment processing server includes:
(A) The processing related to the receivable assignment details data of each of the plurality of paying enterprises is performed including all enterprise unit data that is the total amount of receivables of all paying enterprises of the paying enterprise group, or A step of registering processing method designation data for designating whether to perform only with each company unit data;
(B) the compilation for claim assignment statement data deliveries company according to each of the payment data of a plurality of payment company, and summarizes the payment company groups, each claim assignment detailed data and the total enterprise-wide multiple payment companies receiving a claim assignment detailed compiled data composed of data from the accounts payable management server,
(C) storing the received claim assignment summary data in a claim assignment statement data file;
(D) transmitting the claim assignment summary data together with the claim assignment approval request data to the accounts payable management server;
(E) creating a web page viewable by the accounts payable management server;
(F) Displaying the receivable assignment summary data read from the receivable assignment details data file on the web page, including all enterprise unit data or only each enterprise unit data by referring to the processing method designation data And steps to
(G) receiving early reimbursement application data for applying for early reimbursement of one or a plurality of target receivables selected from the displayed receivable assignment details summary data from the accounts payable management server via the web page;
(H) a step of creating early repayment detail data of the one or more target receivables based on the received early repayment application data and storing it in an early repayment detail data file. The collective payment processing server further includes:
15. The collective settlement method according to claim 14, further comprising the step of: (i) transmitting the early repayment detail data including all company unit data to the integrated management server. The collective payment processing server further includes:
(J) The collective settlement method according to claim 14, further comprising a step of transmitting prepaid details data including all company unit data to the integrated management server. The accounts payable management server
15. The method according to claim 14, further comprising the step of creating a form including all company unit data or using only each company unit data based on the receivable transfer statement summary data received from the collective payment processing server. Batch payment processing method. The collective payment processing server further includes:
(K) creating due date payment data for each of the plurality of paying companies based on the claim assignment summary data and the early payment details data, and storing the due date data in a due date data file;
(L) In order to request due payment to each of the plurality of paying companies, the payables including all company unit data including due date data of each of the plurality of paying companies read from the due payment data file. 15. The collective payment processing method according to claim 14, further comprising a step of transmitting to the management server. The accounts payable management server
5. The method according to claim 1, further comprising the step of creating a form including all company unit data or using only each company unit data based on due date payment data of each of the plurality of payment companies received from the collective payment processing server. The collective payment processing method according to claim 18. The collective payment processing server further includes:
(M) Create CMS linkage data for reflecting due date data of each of the plurality of payment companies read from the due payment data file in the loan data between the plurality of payment companies, and store the data in the CMS linkage data file Steps,
19. The collective payment processing method according to claim 18, further comprising: (n) transmitting the CMS cooperation data read from the CMS cooperation data file to a CMS server of the payment company group.

Images