Electronic payment agency business system and payment agency processing method for electronic payment business system

Abstract

To provide a settlement service high in value-added for a corporation utilizing a settlement agent system.SOLUTION: In an electronic settlement agent operation system communicating with: a plurality of payment source PCs 1-1 to 1-N doing accounting processing; a plurality of payment destination PCs 7-1 to 7-N doing accounting processing, agent bank system 5 implementing payment processing; and a proxy processing server 4 implementing an operation of business to business billing and payment, and conducting a payment agent service, the electronic settlement agent operation system is configured to transmit payment calculation data that the proxy processing server 4 calculates to any payment source PC of the payment source; and, in responce to reception of a payment verification to the payment calculation data from any payment source PC of the payment source, implement an agent payment to a payment bank account following payment destination information registered from the payment source PCs 1-1 to 1-N via the agent bank system 5.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to an electronic payment system and a payment agent processing method for the electronic payment system. [Background technology]

[0002] In recent years, electronic payment systems have evolved, and corporate payment methods have become increasingly electronic. There is a noticeable trend toward using credit card payments more easily to reduce payment workloads.

[0003] Additionally, an increasing number of companies are using proxy systems for payments in business-to-business (B2B) transactions. Currently, Paid, BizPay, and NP Deferred Payment (each service name) are available online as proxy systems that can be contracted.

[0004] These agency systems each have their own unique agency processing systems, ensuring convenience for contracted companies in terms of business payments and providing services that make inter-company payment processing more efficient, thereby reducing the complicated work of sellers receiving payments and buyers conducting credit checks, payment confirmations, and payment collections. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Publication No. 2021-33939 Summary of the Invention [Problem to be solved by the invention]

[0006] However, the price of using these payment processing systems is mainly to reduce operational costs, and the value of using them is one-sided, so it is not recognized that there is a clear difference between the payment processing systems that are adopted.

[0007] The present invention has been made to solve the above-mentioned problems, and an object of the present invention is to provide an electronic payment business system and a payment agency processing method for an electronic payment business system that can provide high-value-added payment services to companies that use the payment agency system. [Means for solving the problem]

[0008] The electronic settlement system of the present invention for achieving the above object comprises the following configuration. An electronic payment agency business system that provides payment agency services by communicating with multiple first data terminals that handle accounting processing for the payer, multiple second data terminals that handle accounting processing for the payee, a bank system that performs payment processing, and an agency processing server that handles billing and payment operations between each legal entity, wherein the agency processing server comprises: a calculation means that analyzes multiple invoice data uploaded from any of the payer's first data terminals to calculate the total payment amount; a transmission means that transmits the payment statement data calculated by the calculation means to any of the payer's first data terminals; an agency payment means that, in response to receiving payment authentication for the payment statement data from any of the payer's first data terminals, executes an agency payment via the bank system to a payment bank account according to the payee information registered from the payer's data terminal; and a notification means that notifies any of the first data terminals of the completion of payment based on the agency payment amount data executed by the agency payment means. [Effects of the Invention]

[0009] According to one or more embodiments of the electronic payment system of the present invention, it is possible to provide a high-value-added bank payment service to corporations that use the payment agent system. [Brief explanation of the drawings]

[0010] The drawings illustrate particular embodiments of the present invention, including essential features of the invention as well as alternative and preferred embodiments. [Figure 1]1 is a block diagram illustrating the configuration of an electronic settlement agency business system according to an embodiment of the present invention. [Figure 2] 2 is a chart illustrating the flow of data processing by an introduction processing unit of the proxy processing server shown in FIG. 1. [Figure 3] 1. FIG. 4 is a chart illustrating the flow of data processing by the BM acquirer registration unit of the proxy processing server shown in FIG. [Figure 4] 1. FIG. 4 is a flowchart illustrating the flow of a payment destination registration process performed by the payment source PC shown in FIG. [Figure 5] FIG. 2 is a flowchart illustrating the flow of the invoice upload process by the payer's PC shown in FIG. 1. [Figure 6] 2 is a chart illustrating the flow of processing by the proxy payment unit to the payee of the proxy processing server shown in FIG. 1. FIG. [Figure 7] 2 is a chart illustrating the flow of processing by the billing unit for the payer of the proxy processing server shown in FIG. 1. [Figure 8] 2 is a chart illustrating the flow of processing by a mileage issuance processing unit of the proxy processing server shown in FIG. 1. [Figure 9] 2 is a chart illustrating the flow of processing by a mile exchange processing unit of the proxy processing server shown in FIG. 1. [Figure 10] 10 is a flowchart illustrating a fee payment process in the electronic settlement agency business system according to the present embodiment. [Figure 11] 10 is a flowchart illustrating a fee payment process in the electronic settlement agency business system according to the present embodiment. [Figure 12] FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. [Figure 13] FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. [Figure 14] FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. [Figure 15]FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. [Figure 16] FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. [Figure 17] FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. [Figure 18] FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. [Figure 19] FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. [Figure 20] FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. [Figure 21] FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. [Figure 22] FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. [Figure 23] FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. [Figure 24] FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. [Figure 25] FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. [Figure 26] FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. [Figure 27] FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. [Figure 28] FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. [Figure 29] FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. [Figure 30] FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. [Figure 31] FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. [Figure 32] FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. [Figure 33] FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. [Figure 34] FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. [Figure 35] FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. [Figure 36] FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. [Figure 37] FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. [Figure 38] FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. [Figure 39] FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. [Figure 40] FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. [Figure 41] FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. [Figure 42] FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. [Figure 43] FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. [Figure 44] 2 is a chart illustrating the flow of one-tap processing by the proxy processing server shown in FIG. 1. FIG. [Figure 45] 2 is a chart illustrating the flow of one-tap processing by the proxy processing server shown in FIG. 1. FIG. DETAILED DESCRIPTION OF THE INVENTION

[0011] Next, the best mode for carrying out the present invention will be described with reference to the drawings. The following embodiments relate to the electronic settlement agency business system shown in FIGS. 1 to 11, and include not only essential configurations of the invention but also optional and preferred embodiments. <System configuration description> [First embodiment] Next, the best mode for carrying out the present invention will be described with reference to the drawings.

[0012] Figure 1 is a block diagram illustrating the configuration of an electronic payment agency business system according to this embodiment. This system shows an example of a system in which a data terminal on the paying corporation side, a data terminal on the payment recipient side, and a server device running a payment service (TobePay (service name)) program, which will be described later, can communicate via a network. More specifically, in the electronic payment agency business system shown in this embodiment, a payment agency service is provided by communication between a plurality of first data terminals (payment source PC1-1 to 1-N) that handle accounting processing for the payer, a plurality of second data terminals (payment destination PC7-1 to 7-N) that handle accounting processing for the payee, a bank system (agency BK5) that executes payment processing, and an agency processing server 4 that executes billing and payment operations between each corporation.

[0013] The TobePay system uses Global Mega Cloud's database for its architecture and data source, enabling the service to be built in an environment that is less susceptible to common vulnerabilities.

[0014] In addition, logic that cannot be expressed with Appsync and GraphQL is implemented using Lambda as Appsync's resolver, and is run as a disposable volatile process, which means that the introduction of viruses and malware can be fundamentally avoided.

[0015] In other words, the TobePay system is characterized by its security infrastructure that allows all clients to continue transactions safely and securely.

[0016] In Fig. 1, 1-1 to 1-N are payment source PCs that run various user applications under a specific operating system and are also configured to be able to run a payment service application provided by this service system. The payment service application is downloaded from the proxy processing server 4 and installed. Here, the payer PCs 1-1 to 1-N are assumed to be PCs managed by various corporations (e.g., dental clinics). The PCs themselves are equipped with normal hardware resources, and are configured so that the CPU loads the operating system from memory resources such as a hard disk onto the RAM, and executes various applications managed by the OS to perform various business processes such as data processing, network communication processing, display processing, and printing processing. In this embodiment, the TobePay system functions as a payment agent processing program managed by the OS. Here, the TobePay system provides a user interface for the payer's PC and the payee's PC to accept and confirm agent processing such as login, bill entry, and confirmation of monthly bill amounts. This allows accounting staff at the payer's PC and the payee's PC to easily view the web screens provided by the TobePay system, and to enter the necessary information and perform approval procedures through a common, highly user-friendly screen.

[0017] Reference numeral 4 denotes an agent processing server, which is connected via the Internet I to be able to communicate with payer PCs 1-1 to 1-N, payee PCs 7-1 to 7-N, and an agent bank system (referred to as agent BK in the figure) 5. The agent bank system 5 is connected to designated payment bank systems 51-1 to 51-N, including bank systems across the country and around the world.

[0018] The proxy processing server 4 stores various applications in a memory unit (not shown) including an introduction processing unit 41 for introducing this service, a BM acquirer registration unit 42, a payee registration unit 43, an invoice upload unit 44, a proxy payment unit to the payee 45, and a billing processing unit to the payer 46, and a main control unit (not shown) consisting of various processors controls communication processing and executes data processing for various services.

[0019] Examples of each introduction processing unit 41, BM acquirer registration unit 42, payee registration unit 43, invoice upload unit 44, proxy payment to payee unit 45, and billing processing unit to payer 46 will be described in detail with reference to the drawings described below.

[0020] The BM management server 8 is configured to include a mileage issuance processing unit 81 and a mileage exchange processing unit 82, and uses a storage unit (not shown) to manage the issuance of business miles according to the payment amount via the ToBPay system and the balance of business miles. Note that the mileage management processing and mileage exchange processing via the ToBPay system will be described later.

[0021] In this embodiment, the BM management server 8 has business mile storage means for storing business mileage, and a mileage issuance processing unit 81 performs processing to issue business mileage to the paying corporation according to the payment amount of the paying PC serving as the first data terminal. Also, a mileage exchange processing unit 82 performs processing to exchange the amount for business mileage to be appropriated for the required payment in accordance with instructions from the first data terminal. Here, the BM management server 8 is connected to the proxy processing server 4 and the paying PC via the Internet network I so that they can communicate with each other.

[0022] In addition, in this embodiment, the ToBPay system is described as being configured so that the BM management server 8 and the proxy processing server 4 work together to share the BM processing, but it may also be configured so that the proxy processing server 4 performs the functional processing on behalf of the BM management server 8. Furthermore, the functional processes of the introduction processing unit 41, BM acquirer registration unit 42, payee registration unit 43, invoice upload unit 44, proxy payment to payee unit 45, and bill processing unit 46 executed by the proxy processing server 4 may be configured as a single application, and payment processing services may be provided via a payment processing screen operated by the payer PCs 1-1 to 1-N and payee PCs 7-1 to 7-N.

[0023] In addition, the proxy processing server 4 is equipped with a controller unit equipped with a CPU, ROM, RAM, etc., and a communication unit that communicates with the payment source PCs 1-1 to 1-N and the payment destination PCs 7-1 to 7-N via the Internet network I, and performs encryption processing to enable transactions that ensure security.

[0024] In addition, when instructions are sent directly from the proxy processing server 4 to the accounts of the payment recipient PC or payment source PC by email, etc., an electronic certificate is attached to prevent damage such as the leakage of customer data due to phishing scams or hacking.

[0025] It is assumed that the payer PCs 1-1 to 1-N, payee PCs 7-1 to 7-N, agent bank system 5, bank systems 51-1 to 51-N, credit company terminals 6-1 to 6-N, and agent processing server 4 are each equipped with a communication processing unit that communicates with the Internet network I, and that an environment for encrypted communications is established.

[0026] In addition, this system uses a global mega cloud database for its architecture and data source, creating a system that provides services in an environment where common vulnerabilities are less likely to be introduced.

[0027] This prevents the introduction of viruses and malware, and the system is designed to allow all clients to continue trading safely and securely.

[0028] In the electronic payment agency business system configured in this manner, the calculation function of the proxy payment unit 45 to the payee of the proxy processing server 4 analyzes multiple invoice data uploaded from any of the payment source PCs 1-1 to 1-N to calculate the total payment amount.

[0029] Furthermore, the payment statement data calculated by the payment agent unit 45 to the payee is sent to any one of the first data terminals of the payer by the communication function of the agent processing server 4. Furthermore, in response to receiving payment authentication for the payment statement data from any one of the payer PCs 1-1 to 1-N, the payment agent unit 45 to the payee executes an agent payment via the agent BK5 to the payment bank account according to the payee information registered by the payer PCs 1-1 to 1-N.

[0030] Furthermore, the communication function of the proxy processing server 4 notifies any one of the first data terminals of the completion of payment based on the proxy payment amount data executed by the proxy payment unit 45 to the payee.

[0031] Specific processing of each processing unit of the proxy processing server 4 shown in Fig. 1 will be explained in order below with reference to Fig. 2 to Fig. 9. Each functional processing by the proxy processing server 4 functioning as the ToBPay system will be explained in detail below with reference to user interfaces, examples of which are shown in Fig. 13 to Fig. 35. [Data processing by introduction processing unit 41]

[0032] Figure 2 is a chart illustrating the flow of data processing by the introduction processing unit 41 of the proxy processing server 4 shown in Figure 1. Note that the payer users who operate the payer PCs 1-1 to 1-N are assumed to be the persons in charge on the corporate side. Note that in this specification, the name of the payment service provided by the proxy processing server 4 is referred to as ToBPay.

[0033] First, to introduce the ToBPay system, a ToBPay representative from a payment service management company will propose the introduction of ToBPay to the paying user (corporate accounting staff) via Internet Network I or through sales activities.

[0034] Here, the paying user and the ToBPay representative discuss the benefits and the paying user agrees to introduce ToBPay. Next, the paying user consults with an executive at the paying corporation, decides to officially introduce the system, and enters the necessary information (terms and conditions) into an application form (provided as a PDF file, for example).

[0035] At this time, when the paying corporation signs a document (including a digitally signed document) containing the terms and conditions, the document (PDF file) is notified to the ToBPay system via the Internet network I. In response to this, the ToBPay system performs an acceptance process to accept the paying corporation into the ToBPay system. Specifically, the introduction processing unit 41 displays a UI screen for entering an email address for new registration, as shown in FIG. 12, on the display device of the paying PC 1-1. On this screen (SIGN UP), the email address is entered. In response, the introduction processing unit 41 sends a registration email to the email address to confirm the email (UI screen for new registration shown in FIG. 13), and furthermore, the necessary information such as the password, password re-entry, name, telephone number, and registered account company information, such as the company name (corporate name), job type, and telephone number, is entered into the UI screen for new registration shown in FIG. 14. Here, as shown in the UI screen in Figure 15, by correcting the information entered before the actual registration in the new registration and clicking the registration button, the UI screen shown in Figure 16 will be displayed on the display device of the payer PC1-1, and the new registration process will be completed.

[0036] Next, when the ToBPay system operator issues a serial number (control number) to the paying corporation that has received the management screen, the official management screen issuance process for the paying corporation that has accepted the assignment is executed. More specifically, the URL of the management screen, an example of which is shown in the UI screen in Figure 17, is sent to the paying corporation's registered address, and the paying user (accounting staff) is asked to register their ID / PASS on that management screen. Next, the ToBPay system sends a management screen installation guide to the paying user of the paying corporation via the Internet network I. This allows paying corporations to operate payment agency services using the ToBPay system. [BM Acquirer Registration Process]

[0037] Fig. 3 is a chart illustrating the flow of data processing by the BM acquirer registration unit 42 of the proxy processing server 4 shown in Fig. 1. Here, "acquirer" means affiliated store registration. Below, the BM acquirer registration process by the BM acquirer registration unit 42 will be explained with reference to the UI screens shown in Figs. 18 to 23.

[0038] First, the ToBPay system notifies the paying corporation of BM (Business Mile) acquirer information via Internet Network I. When the paying corporation receives the BM acquirer information notification (e.g., email) sent from the ToBPay system, the representative or person in charge of the paying corporation enters the necessary information into the BM application form (PDF file) and sends it via Internet Network I to the management server of the BM management company.

[0039] In response to this, the management server of the BM management company (BM management server 8) accepts and processes the application of the paying corporation that has introduced the ToBPay system. Here, the mileage issuance processing unit 81 of the BM management server 8 issues a new user account on the BM operator screen, and when a paying corporation user account is issued to the BM user (acquirer screen) displayed by the paying corporation that has introduced the ToBPay system, BM account processing for the paying corporation that has introduced the ToBPay system is completed. Specifically, the BM acquirer registration unit 42 displays the UI screen shown in Fig. 18 on the display device of the payer PC 1-1. Here, the operator (client) of the payer PC 1-1 clicks the login button or the new registration button to proceed to the new registration and login process. Here, when a client who has already completed BM registration enters the registered email address on the UI screen shown in Fig. 19 and clicks the approve button, the UI screen shown in Fig. 20 is displayed on the display device of the operator (client) of the paying PC1-1. Then, the BM acquirer registration unit 42 presents the UI screen shown in Fig. 20 to the paying PC1-1. Here, when the operator (client) of the paying PC1-1 follows the message displayed on the screen and confirms that the authentication email has been received, the login process is completed. Note that if the authentication email has not been received, the same process is repeated by clicking the resend button to have the authentication email resent. On the other hand, when the client clicks the new registration button on the UI screen shown in Fig. 18, the BM acquirer registration unit 42 presents the UI screen shown in Fig. 21 to the payer PC1-1. The new registration format displayed on the UI screen shown in Fig. 21 is an example, and items other than those on this screen may be included. After the client has finished entering their name, address, and corporate information on the UI screen, they click the member registration completion button. The BM acquirer registration unit 42 then presents the UI screen shown in Fig. 22 to the payer PC 1-1. Here, an overview of the business miles provided by the ToBPay system and the service details (earning miles, sharing miles, using miles) are presented to the client. When the Next button is clicked here, the BM acquirer registration unit 42 presents the UI screen shown in Fig. 23 (Business Miles My Page screen) to the payer PC 1-1. On this screen, the client can check the mile balance, the sharable mile balance, news, and the contents of the digital mile card. Also, the confirmation button, use button, save button, and share button are located at the bottom of the UI screen shown in Figure 23.

[0040] [Payment destination registration process] Fig. 4 is a flowchart illustrating the flow of the payee registration process by the payer PCs 1-1 to 1-N shown in Fig. 1. The payee registration process will be described in detail below with reference to the UI screens shown in Figs. The payee registration unit 43 of the agent processing server 4 sends a payee registration request email to the payer PCs 1-1 to 1-N.

[0041] Here, the payer PCs 1-1 to 1-N display the https: registration screen in their web browsers and enter the address and contact details of the payees and their own BM accounts (acquirer registration number, etc.) one by one.

[0042] This completes the payee corporation request form, which is then sent to the agent processing server 4 (UI screen shown in Fig. 25). The UI screen shown in Fig. 24 prompts payees 7-1 to 7-N to log in to the ToBPay system or to register as a new user. When the register button is clicked, the UI screen shown in Fig. 25 is displayed on the display device of payees 7-1 to 7-N, allowing them to join the company with a simple operation.

[0043] Next, when the payee registration unit 43 of the agent processing server 4 receives a payee corporation introduction request form (PDF file) from the payer PC1-1 to PC1-N, the payee registration unit 43 issues a payee registration form and sends the issued payee registration form to the payee PC7-1 to PC7-N of the payee corporation.

[0044] In response to this, the person in charge of the payee PC7-1 to PC-N of the payee corporation considers whether to accept the payment proposed by the ToBPay system, and if the person in charge of the payee PC7-1 to PC-N of the payee corporation agrees to the proposal, he / she enters the necessary information (including the bank name, branch name, account type, account number, etc. for payment) into the application form (PDF file) provided by the ToBPay system, and sends the application form with the necessary information entered to the agent processing server 4 that constitutes the ToBPay system via the Internet network I.

[0045] In response to this, the payee registration unit 43 of the proxy processing server 4 accepts the received application form, issues a management screen provided by the proxy processing server 4, and sends a URL on the TP payee corporation screen to the registered address.

[0046] As a result, the ToBPay system notifies the users of the payee PCs 7-1 to 7-N of the issued introduction guide for the management screen.

[0047] On the other hand, when the payee registration unit 43 of the proxy processing server 4 accepts the received application form, the BM management server 8 receives a notification of acceptance of the payee registration from the payee registration unit 43 of the proxy processing server 4, and sends a registration completion notification to the payer on the acquirer screen provided by the BM management server 8 indicating that the registration of the payee has been completed, and sends the issued registration completion notification indicating that the registration of the payee has been completed by email to one of the payer PCs 1-1 to 1-N via the Internet network I.

[0048] When any of the payer PCs 1-1 to 1-N receives a registration completion notice indicating that the registration of the payee has been completed from the mileage issuance processing unit 81 of the BM management server 8, the payee registration process is completed.

[0049] [First invoice upload process] Fig. 5 is a chart illustrating the flow of the invoice upload process by the payee PCs 7-1 to 7-N shown in Fig. 1. The invoice upload process will be described in detail below with reference to the UI screens shown in Figs.

[0050] The invoice upload unit 44 of the proxy processing server 4 accepts and processes invoice data according to the invoice to be paid by the paying corporation in the current month, which is entered by the accounting staff of the payee PCs 7-1 to 7-N on the web screen provided by the ToBPay system, according to a pre-set closing date.

[0051] Specifically, when a payee user operating a payee PC 7-1 to 7-N issues an invoice to a payer, the user enters the necessary billing details (including a code specifying the biller, billing details, and total billing amount) into a web page (upload page) provided by the ToBPay system, and a UI screen such as that shown in FIG. 26 is displayed on the display device of the payee PC 7-1 to 7-N. Clicking the + button displays a UI screen such as that shown in FIG. 27 on the display device of the payee PC 7-1 to 7-N as a billing category information input screen. Clicking the Edit button assigned to the business partner displays a UI screen such as that shown in FIG. 28 on the display device of the payee PC 7-1 to 7-N for entering invoice information. The person in charge of the payee PC 7-1 to 7-N can then enter necessary information, such as the billing date, payment deadline, orderer name, business partner name, business contact name, subject, billing amount (excluding tax), and remarks, into the UI screen shown in FIG. 28. Next, the person in charge of the payee PCs 7-1 to 7-N returns to the UI screen shown in Fig. 27 and clicks the Add Customer button, which causes the UI screen shown in Fig. 29 to be displayed on the display devices of the payee PCs 7-1 to 7-N. When the Save button is pressed here, the invoice upload unit 44 receives invoice data (PDF file) containing the invoice items for the specified invoice source entered by the payee user.

[0052] In response to this, the invoice upload unit 44 notifies the TP paying corporation screen and the TP operator screen that the invoice uploaded by the payee user has been received.

[0053] On the other hand, in the case of a separate upload, the payee users of the payee PCs 7-1 to 7-N issue bill data to the payer users of any of the payer PCs 1-1 to 1-N via the Internet network I.

[0054] When a payer user of any of the payer PCs 1-1 to 1-N receives this, he approves the bill data (PDF file) and uploads it to the bill upload unit 44 of the proxy processing server 4 via the Internet network I.

[0055] As a result, the invoice upload unit 44 of the agent processing server 4 notifies the TP payee corporation screen of the payee PCs 7-1 to 7-N that the invoice has been registered, notifies the TP operator screen of the invoice registration, and notifies the TP payee corporation screen of the invoice registration.

[0056] In response, the payment recipient user of one of the payment recipient PCs 7-1 to 7-N is asked to confirm the invoice via the TP payment recipient company screen, and an approval instruction for the contents is awaited. The TP payment recipient company screen has an approval button for approving the uploaded invoice. Here, the approval button is applicable when there are multiple approvers, so the payment recipient user corresponding to the superior may give the final approval. The UI screen shown in Figure 30 shows the detailed invoice information screen displayed on the payer's PC. The UI screen shown in Figure 31 corresponds to the state where a list of registered invoices related to the current TBP initial development is displayed, with a tab assigned to each project. The UI screens shown in Figures 32 and 33 are configured to allow the user to check the payment status and whether payment has been completed. In addition, the UI screens shown in Figures 34 and 35 are configured to allow the payment status and transfer status of invoices related to the registered "XXX Project" to be confirmed.

[0057] [Proxy payment processing to payee] FIG. 6 is a chart illustrating the flow of processing by the proxy payment unit 45 to the payee of the proxy processing server 4 shown in FIG.

[0058] In the invoice upload process shown in Figure 5, when the payee proxy payment unit 45 of the proxy processing server 4 receives a notification that the payee user has completed invoice confirmation and approval, it accepts the payment information stated on the invoice and updates and displays the payment information on the TP operator screen based on the accepted payment information.

[0059] Next, the invoice amount is paid to the payee based on the payment information updated on the TP operator screen. Here, payment based on the payment information means the process of transferring the amount to one of the banks 51-1 to 51-N designated by the payee via the agent bank 5 with which the ToBPay system has a contract.

[0060] In this way, when the proxy payment unit 45 to the payee completes payment to the payee, it sends a transfer confirmation notice to the TP operator screen, which displays the completion of the transfer on the TP operator screen and updates the contents of the TP operator screen to reflect the contents on the TP payee corporation screen.

[0061] When the payee PCs 7-1 to 7-N receive the transfer completion notification, the transfer completion is displayed on the TP Payee Corporation screen displayed on the display devices of the payee PCs 7-1 to 7-N. The payee user operating the payee PCs 7-1 to 7-N can then confirm via the TP Payee Corporation screen that the transfer by the ToBPay system has been completed, and can issue instructions to update the information on the displayed screen. In response to this, the information on the TP payee corporation screen displayed on the display device of the proxy processing server 4 is updated to indicate that proxy payment for one bill has been completed.

[0062] As a result, the display device of the agent processing server 4 updates the information of one bill on the TP payee corporation screen to indicate payment has been completed. Similarly, the information on the TP payee corporation screen displayed on the display device provided in the payee PCs 7-1 to 7-N is updated to indicate payment has been completed.

[0063] [Billing process to payer] FIG. 7 is a flowchart illustrating the flow of processing by the billing processor 46 for the payer of the proxy processing server 4 shown in FIG. When the proxy payment unit 45 to the payee shown in FIG. 6 updates the payment information, processing by the billing processing unit 46 to the payer in the ToBPay system is started.

[0064] First, the billing processor 46 for the payer receives the payment completion notice and performs billing processing to one of the payer PCs 1-1 to 1-N for the amount transferred on behalf of the payer. As a result, billing information is notified to the TP payer corporation screen displayed on the display device of the proxy processing server 4.

[0065] In this way, when the payer user of payer PC1-1 to 1-N receives the bill from payer billing processor 46, the payer pays the billed amount by bank transfer to the account specified in agent bank 5 designated by the ToBPay system. When the ToBPay system confirms the transfer by the payer user of payer PC1-1 to 1-N, payer billing processor 46 updates the information indicating the payment progress corresponding to the payer corporation on the TP operator screen to payment confirmation, and updates the information indicating the payment status on the TP payer corporation screen to transaction completion.

[0066] [Mileage issuing process] FIG. 8 is a flowchart illustrating the flow of processing by the mileage issuance processing unit 81 of the proxy processing server 4 shown in FIG.

[0067] When the payer user shown in FIG. 7 causes the payer billing processor 46 to update the TP payer corporation screen to indicate transaction completion, the mileage issuance processor 81 of the BM management server 8 starts processing.

[0068] The mileage issuance processing unit 81 refers to a mileage management table (not shown), reads out the mileage awarding information set for the paying corporation that has completed the payment based on the linkage information, confirms the number of miles for this payment, and issues an instruction to approve the number of miles to be awarded on the BM operator screen.

[0069] As a result, the mileage issuance processing unit 81 adds the approved number of miles to the current number of miles on the acquirer screen of the BM user. Accordingly, the paying user of the paying corporation can confirm that they have received the number of miles awarded for this payment via the corporation login screen.

[0070] [Mileage issuing process] Fig. 9 is a chart illustrating the flow of processing by the mile exchange processing unit 82 of the proxy processing server 4 shown in Fig. 1. The mile issuance processing will be described below with reference to the UI screens shown in Figs.

[0071] When the paying user of the paying corporation logs in to the BM management server 8 from the management screen, a mileage confirmation screen is displayed. Here, the paying user of the paying corporation can check the current mileage. If it is determined that the number of miles has reached the appropriate number of exchange points, an instruction to exchange the current number of miles for purchasing a product or the like can be input.

[0072] Then, the mile exchange processing unit 82 of the BM management server 8 subtracts the instructed points from the total number of points immediately before based on the instructed points to be exchanged, and completes the exchange process.

[0073] Next, the mile exchange processing unit 82 of the BM management server 8 notifies the content of the exchange instruction and the point balance (see UI screen shown in Figure 37), which is the point balance obtained by subtracting the points instructed to be exchanged from the previous total number of points, to the paying user of one of the corporations, paying PCs 1-1 to 1-N, via the Internet network I, and ends the processing (see UI screen shown in Figure 36).

[0074] [Effects of the first embodiment] According to the first embodiment, a paying corporation using the ToBPay system can receive business miles (points) based on the amount of the proxy payment, and can use the accumulated business miles to fund product purchases and travel expenses.

[0075] Business miles can also be used to cover fees paid when using the ToBPay system described below.

[0076] Second Embodiment Figure 10 is a flowchart explaining the fee payment process in the electronic payment agency business system according to this embodiment. Note that (1) to (19) indicate each step. Note that this process is initiated after a payment agency contract is concluded between the contract manager of the ToBPay system and the payer (corporation).

[0077] Each step is realized by the CPU of the controller of the proxy processing server 4 reading and executing the ToBPay system program stored in the memory. The ToBPay system program is configured so that it can be updated as needed to prepare for revisions to regulations, tax rates, etc.

[0078] First, when the proxy processing server 4 that constitutes the ToBPay system receives a registration request from one of the payer PCs 1-1 to 1-N (1), and the accounting staff of the payer PCs 1-1 to 1-N receive approval from the payee PCs 7-1 to 7-N, which are the transaction parties for monthly payments, through the ToBPay system (2), it determines whether all registrations (K=N) have been completed (3).

[0079] If it is determined that all registrations are complete, the invoice information for the closing date, for example, from the accounting staff of Corporation A who operates the payment source PC1-1, is uploaded to the ToBPay system (4).

[0080] Next, it determines whether today is the payment closing date for the currently processing corporation A (5). If it determines that today is not the payment closing date, it returns to step (3). If it determines that today is the payment closing date, it notifies one of the payment source PCs 1-1 to 1-N corresponding to the payment source of the payment confirmation document compiled by the ToBPay system, and determines whether approval has been received from the accounting officer of that corporation (6).

[0081] Next, the ToBPay system refers to the payment contract conditions and determines whether the terms of the proxy payment with the payment source are Condition 1 (where the commission for the proxy payment is shared between the payment source and the payment recipient) (7).

[0082] Here, if the ToBPay system determines that the proxy payment conditions with the payer are condition 1, it proceeds to step (8), where the ToBPay system waits to receive an approval instruction for the payment confirmation from one of the payers PC1-1 to 1-N, and when it receives an approval instruction for the payment confirmation from one of the payers PC1-1 to 1-N, the ToBPay system compares the payment confirmation with the payee registered at the time of signing the contract with the ToBPay system, and transfers the money to the respective bank accounts specified by the payee.

[0083] Next, the ToBPay system notifies one of the payer PCs 1-1 to 1-N that the proxy payment based on the payment confirmation has been completed (9). This allows payments to be completed on a monthly basis for each corporate contract holder, significantly reducing the burden on corporate accounting staff in processing transfers.

[0084] On the other hand, if it is determined in step (7) that the condition for the proxy payment with the payer is condition 2 (the payer bears the fee for the proxy payment), the process proceeds to step (10).

[0085] In step (10), the ToBPay system notifies one of the payment source PCs 1-1 to 1-N corresponding to the payment source of the payment confirmation document compiled by the ToBPay system, and determines whether approval has been received from the accounting officer of the corporation.

[0086] Here, when an approval instruction for the payment confirmation is received from one of the payer PCs 1-1 to 1-N, the ToBPay system compares the payment confirmation with the payee registered at the time of signing the contract with the ToBPay system, and transfers the money to the respective bank accounts specified by the payee (11).

[0087] Next, the ToBPay system reads out from the memory the conditions for charging fees for this payment (12) and determines whether the fee sharing ratio between the payer and the payee is 100%:0% (13).

[0088] If the ToBPay system determines that the fee sharing ratio between the payer and the payee is 100%:0%, it calculates the fee for this proxy payment and sends an invoice to one of the payer PCs 1-1 to 1-N (14). Then, once payment of the fee is confirmed by one of the payer PCs 1-1 to 1-N (19), the system ends this process.

[0089] On the other hand, if in step (13) the ToBPay system determines that the fee sharing ratio with the payee is not 100%:0%, the ToBPay system further determines whether the fee sharing ratio between the payer and the payee is 50%:50% (15).

[0090] If it is determined that the fee sharing ratio between the payer and the payee is 50%:50%, the fee for the total payment is calculated, the fees to be charged to both the payer and the payee are calculated, and a payment invoice is sent (18). Next, the process proceeds to step (19).

[0091] On the other hand, if the ToBPay system determines in step (15) that the fee sharing ratio between the payer and the payee is not 50%:50%, it reads the fee sharing ratio registered in the memory unit, calculates the fee to be charged to each payee (16), and sends a fee payment invoice to the payer and the payee according to the ratio (17).Then, it proceeds to step (19).

[0092] This allows the payer and the payee who use the ToBPay system to share the agency fee, and the miles provided by the ToBPay system can be awarded to both the payer and the payee.As a result, as the number of corporations using the ToBPay system increases, the number of corporate accounting staff can be reduced, which reduces the expenses of the corporation itself. In addition, by utilizing the ToBPay system, both parties will be awarded and accumulate miles.

[0093] Regarding miles, corporations that enter into a contract with the ToBPay system may be configured to prioritize cashback to the corporation over mileage redemption, either in place of awarding miles at the time of signing the contract or in combination with them at an appropriate time.

[0094] In addition, the system may be configured to individually lower the fees associated with proxy payments than usual if conditions specified by the ToBPay system are met (such as accepting business negotiations with designated vendors or introducing the services of designated vendors).

[0095] In this embodiment, when the proxy processing server 4 executes a proxy payment, it executes a step of calculating a commission for the proxy payment using the ToBPay system (16).

[0096] At this time, the proxy processing server 4 notifies the first data terminal, which is the payer, or the second data terminal, which is the payee, of the calculated fee as a share invoice (17).

[0097] On the other hand, the proxy processing server 4 may calculate the fee for the proxy payment so that the payer bears the entire fee.

[0098] In this case, the proxy processing server 4 notifies the first data terminal of the calculated fee.

[0099] In addition, this embodiment is configured to be flexibly applicable when the proxy processing server 4 calculates the fee for the first data terminal that is the source of the payment or the second data terminal that is the recipient of the payment based on a preset sharing ratio (see steps (13) to (15) shown in Figure 10).

[0100] [Effects of the second embodiment] According to the second embodiment, a payment environment can be created in which the payment source bears the cost of the proxy payment fee paid to the ToBPay system, or the cost can be shared between the payment source and the payment recipient, thereby increasing the convenience of the payment source and the payment recipient using the ToBPay system.

[0101] Third Embodiment FIG. 11 is a flowchart illustrating the fee payment process in the electronic payment agency business system according to this embodiment. Note that (21)~ indicate each step. Note that this process is initiated after a payment agency contract is concluded between the contract clerk of the ToBPay system and the payer (corporation). Furthermore, each step is realized by the CPU of the controller of the agency processing server 4 reading and executing the ToBPay system program stored in the memory.

[0102] First, based on the contract with the payer, the ToBPay system analyzes the invoices uploaded by the payer on the monthly closing date and calculates the total amount to be paid by the payer to the payee (21).

[0103] Next, the ToBPay system installed on the proxy processing server 4 determines whether the contractual conditions between the payer and the ToBPay system regarding the proxy payment are proxy payment conditions 1 (conditions under which the ToBPay system makes an advance payment to the payee without waiting for the payment from the payer before transferring the proxy payment amount from the payer to the ToBPay system) (22).

[0104] If the ToBPay system determines that the proxy payment condition is 1, the ToBPay system sends a proxy payment statement to one of the payment source PCs 1-1 to 1-N via the Internet I (23).

[0105] Next, the ToBPay system waits for an instruction to approve the proxy payment statement sent by the payer (24), and when it receives an instruction to approve the proxy payment statement sent by the payer, it makes an advance remittance (prepayment remittance) from proxy bank 5 managed by the ToBPay system to the designated account of the bank designated by the registered payee (25).

[0106] Next, the ToBPay system notifies the payer who made the advance payment of a payment request for the total amount of the advance payment (26), and when the payer confirms that the payment has been deposited into the designated account of the agent bank 5 designated by the ToBPay system (27), the ToBPay system records the details of this payment in the payer ledger managed in the memory unit, updates the payer information (28), and then terminates this process.

[0107] On the other hand, if the ToBPay system determines in step (22) that the condition is not agent payment condition 1, the ToBPay system sends an agent payment statement to one of the payer PCs 1-1 to 1-N via the Internet network I (29). After confirming that the payer has transferred the total amount of payment stated on the statement to the agent bank 5 designated by the ToBPay system (30), the system proceeds to step (26).

[0108] As a result, the accounting staff of the paying corporation can select either a prepayment method, in which the total amount of the agent payment is paid in advance to the agent bank 5 of the ToBPay system in step (29), or an advance payment method, in which the ToBPay system pays the total amount of the agent payment in advance in step (25), depending on the usage history of the ToBPay system.

[0109] In this way, the electronic payment agency system frees the payer from having to perform the individual and troublesome payment procedures in the payment process between the paying user (corporation) who has a contract with the ToBPay system and the payee user (corporation), and allows the payment to be completed in a single lump-sum payment.

[0110] On the other hand, as mentioned above, the payee can earn points as business miles by sharing the fees for using the ToBPay system with the payer.

[0111] [Effects of the third embodiment] According to the third embodiment, corporate payments can be made using a method that is innovative compared to conventional electronic payment operations, and a significant reduction in labor costs at the payer's side can be expected.

[0112] [Fourth embodiment] In the above embodiment, payment operations between corporations (BtoB) have been described in detail, but the ToBPay system may be expanded by adding a factoring function (accounts receivable purchasing function).

[0113] Fifth Embodiment 38 to 43 are diagrams showing examples of UI screens for BM processing in the electronic payment agency business system according to this embodiment. Each BMUI screen can be displayed by either the payer or the payee.

[0114] In the mileage issuance process shown in Figure 8, users who are registered with BM on the payment source PC and payment destination PC receive notifications on demand or periodically from the BM management server 8 (UI screen displays shown in Figures 38 and 43).

[0115] In this embodiment, the following tabs are set: My Page, Check, Use, Save, and Share. By selecting any of the tabs, the mileage issuance processing unit 81 and the mileage exchange processing unit 82 will work together to perform the BM process.

[0116] Here, when the user of the payment source PC or payment destination PC selects the tab for using miles, the UI screen shown in Fig. 39 is displayed on the display device of the payment source PC or payment destination PC. This example is an operation example in which the miles accumulated by the user of the payment source PC or payment destination PC are exchanged for a gift certificate that can be used on a shopping site, such as Amazon (registered trademark).

[0117] When the next button is clicked on this screen display, the mile exchange processing unit 82 controls the UI screen content on the display device of the payer PC or payee PC to switch to the UI screen shown in FIG.

[0118] Here, you can confirm that the current mileage status will be updated by issuing the gift certificate. Furthermore, when you click the Next button, the mileage exchange processing unit 82 controls so that the contents of the UI screen on the display device of the payer PC or payee PC are switched to the UI screen shown in Figure 41.

[0119] Here, when each user of the payer PC or payee PC clicks the Apply button to approve the displayed exchange contract, the mile exchange processing unit 82 controls the contents of the UI screen on the display device of the payer PC or payee PC to switch to the UI screen shown in Figure 42.

[0120] Sixth Embodiment In the first embodiment described above, when the proxy processing server 4 processes billing transactions between the payer PC and the payee PC on behalf of the payer, if the invoice upload process shown in Figure 5, the proxy payment process to the payee shown in Figure 6, and the billing process to the payer shown in Figure 7 are processed in chronological order, if the person in charge of the payer PC (accounting staff) repeats the invoice upload process, for example, by a specific date at the end of the month, they are required to repeat the invoice confirmation and approval process shown in Figure 5 each time, which has raised the issue that proxy payment instructions to the payee cannot be processed with a single approval.

[0121] Therefore, the payment source PC may be configured to approve payment once a month to complete the proxy payment to the payee.

[0122] [Second invoice upload process] Figures 44 and 45 are charts explaining the flow of one-tap processing by the proxy processing server shown in 1. Note that this system is configured to support the following methods for registering invoices: (1) registering invoice information, (2) uploading the invoice and then performing OCR (automatic registration using image recognition), and (3) automatically reading and registering the invoice information by sending a PDF of the invoice to a dedicated address. Also, if there are multiple invoice data, (1) it is possible to set "approval" or "denial" for each individually in the system. Also, (2) in case it would be troublesome to do it individually, it is also possible to set "approval" or "denial" for all of them collectively in the system. In either case (1) or (2) above, you will receive a notification via the method you specify (chat such as LINE (registered trademark) or email), and with just one tap of "Approve," automatic bank withdrawal will be made. This is the unique feature of the second invoice upload process. When issuing a flow for the invoice upload process by the payee PCs 7-1 to 7-N shown in Figure 1, the necessary billing items (including a code specifying the biller, billing details, and total bill amount) are entered into the web page (upload page) provided by the ToBPay system, and a UI screen such as that shown in Figure 26 is displayed on the display device of the payee PCs 7-1 to 7-N. When the + button is clicked, a UI screen such as that shown in Figure 27 is displayed on the display device of the payee PCs 7-1 to 7-N as a billing category information input screen. Here, when the edit button assigned to the business partner is clicked, a UI screen for entering invoice information such as that shown in Figure 28 is displayed on the display device of the payee PCs 7-1 to 7-N.

[0123] Here, the person in charge of the payee PCs 7-1 to 7-N can enter the necessary information, such as the billing date, payment deadline, ordering company name, trading partner name, name of person in charge of the transaction, subject, billing amount (excluding tax), and notes, into the UI screen shown in Figure 28.

[0124] Next, the person in charge of the payee PCs 7-1 to 7-N returns to the UI screen shown in Fig. 27 and clicks the Add Customer button, which causes the UI screen shown in Fig. 29 to be displayed on the display devices of the payee PCs 7-1 to 7-N. When the Save button is pressed here, the invoice upload unit 44 receives invoice data (PDF file) containing the invoice items for the specified invoice source entered by the payee user.

[0125] This process is repeated until the scheduled closing date of the month, and the invoice upload unit 44 notifies the TP paying corporation screen and the TP operator screen once that all invoices uploaded by the payee users have been received.

[0126] Similarly, in the case of a separate upload, the payee users of the payee PCs 7-1 to 7-N issue bill data to any of the payer users of the payer PCs 1-1 to 1-N via the Internet network I.

[0127] After all the individual bills from each of these payees are tallied, when a payer user from one of payer PCs 1-1 to 1-N receives invoice data requesting approval for the total amount, the user approves one piece of invoice data (PDF file) with a single tap, which instructs a proxy payment to the payee as shown in Figure 44. When this is received by the proxy processing server 4, as shown in Figure 45, the proxy processing server 4 executes the payment via the above-mentioned proxy BK5 based on the payment information approved with one tap.

[0128] From this point on, the flow of invoices is reversed from that of the first embodiment, and after the proxy payment to the payee is completed, the process is executed to send the information of each invoice for which the payee has been notified to the payer's PC via network I, as shown in Figure 44. This allows the details of the invoices uploaded by each payee for the month to be received after the fact.

[0129] Here, an example of the data processing sequence in the second invoice upload process will be described in detail. The payee registers the invoice data in the system by email, uploading, or entering information (1). Next, ToBPay compiles the invoice data registered by the payee into billing information (2). Next, the paying user is notified of the billing information in step (2) primarily via LINE (registered trademark) or email (3). This allows the paying user to check the detailed invoice information. Next, the paying user issues an operational instruction to approve or deny the billing information notified via LINE (registered trademark) or email (4). If the paying user issues an operational instruction to approve, an automatic withdrawal request will be made. Next, ToBPay makes a proxy payment to the payee, and the payment is automatically debited from the payer to ToBPay (5). After the transaction is complete, both the payer and the payee can connect to the system to check on their screen the usage details, showing how much was paid to which company (if a payment was made) (6). In this way, with ToBPay payments via the second invoice upload process, the paying user can complete payment instructions not only via their PC but also via their smartphone (with just one tap on the notification). This allows the paying user to make payments via their PC, and also to complete payment instructions via their smartphone when they are out, dramatically improving operability. Furthermore, in terms of reducing the workload for ToBPay users, it eliminates the need for tasks such as (1) consolidating invoices, (2) creating transfer data from invoices, (3) transferring funds, (4) reconciliation, (5) journal entries, and (6) checking (2) to (5), resulting in a significant reduction in work hours. In addition, payment procedures, which previously had to be done by mail, will now be digitized, significantly reducing the amount of work required for payment recipients.

[0130] [Effects of the Sixth Embodiment] According to the sixth embodiment, the number of payment approvals on the payer's PC can be reduced to one approval per month to complete proxy payments to the payee, significantly reducing the approval work required of the person operating the payer's PC for invoices uploaded by each payee.

[0131] Each step of the present invention can also be realized by executing software (programs) acquired via a network or various storage media on a processing device (CPU, processor) such as a personal computer (computer).

[0132] The present invention is not limited to the above-described embodiments, and various modifications (including organic combinations of the respective embodiments) are possible based on the spirit of the present invention, and these are not excluded from the scope of the present invention. [Industrial Applicability]

[0133] For example, if a medical institution were to introduce the ToBPay system, they would be able to eliminate the need to register business partners, perform billing, and make payments at the end of each month or on a specified date for small expenses such as purchasing medicines for treatment, medical equipment, and consumables, which would be expected to significantly reduce the amount of work required.

[0134] Furthermore, by introducing the ToBPay system, nursing care and welfare businesses can create an environment where they can understand at a glance the total amount billed and paid, as well as the breakdown of individual expenses, when it comes to expenses such as the cost of meals provided at the facility, the cost of purchasing nursing care supplies, equipment installation costs, and printing costs incurred in administrative work.

[0135] The disclosure of the present invention described above can be summarized at least as follows. (1) An electronic payment agency service system that provides a payment agency service by communicating with a plurality of first data terminals that perform accounting processing for the payer, a plurality of second data terminals that perform accounting processing for the payee, a bank system that performs payment processing, and an agency processing server that performs billing and payment operations between each corporation, wherein the agency processing server receives data uploaded from any of the first data terminals of the payer. The payment destination is the sameAnalyze multiple invoice data to calculate total payment amount For each payee A calculation means for calculating the For each payee The calculated payment statement data Summary of payment statement data a sending means for sending the payment statement data to any one of the first data terminals of the payers; an agent payment means for executing an agent payment via the bank system to a payment bank account according to the payment destination information registered from the data terminal of the payer in response to receiving payment authentication for the payment statement data from any one of the first data terminals of the payers; and a notifying means for notifying any one of the first data terminals of the completion of payment based on the agent payment amount data executed by the agent payment means. The first data terminal is provided with an approval screen display means for displaying a one-tap approval screen for making a lump-sum payment of the combined payment statement data containing a mixture of different payees presented by the transmission means, and after receiving a one-tap approval instruction on the one-tap approval screen from the first data terminal, the proxy payment means executes proxy payments via the bank system to different payment bank accounts according to the payee information registered from the data terminal of the payer. It is characterized by:

[0136] (2) The proxy processing server is characterized by having a calculation means for calculating a fee for the proxy payment executed by the proxy payment means, and a first fee notification means for notifying the first data terminal corresponding to the payer or the second data terminal corresponding to the payee of the fee calculated by the calculation means as a share claim.

[0137] (3) The proxy processing server is characterized by having a calculation means for calculating a fee for the proxy payment executed by the proxy payment means, and a second fee notification means for notifying the first data terminal, which is the source of payment, of the fee calculated by the calculation means.

[0138] (4) The calculation means is characterized in that it calculates the fee for the first data terminal that is the source of payment or the second data terminal that corresponds to the destination of payment based on a preset sharing ratio.

[0139] (5) The proxy processing server is characterized by communicating with a business mile management server that includes a business mile storage means for storing the number of business miles, a mile issuance processing means for issuing business miles to the paying corporation according to the amount of payment made by the first data terminal, and a mile exchange processing means for exchanging the number of business miles for the required payment in accordance with instructions from the first data terminal.

[0141] ( 6 ) The first data terminal is The proxy payment means can be set in advance whether to pay the combined payment statement data, which includes a mixture of different payees, presented by the payment statement provider in a lump sum or to pay each payee individually. It is characterized by:

[0142] ( 7 ) A payment agency processing method for an electronic payment agency business system that provides a payment agency service by communicating among a plurality of first data terminals that perform accounting processing for the payer, a plurality of second data terminals that perform accounting processing for the payee, a bank system that performs payment processing, and an agency processing server that performs billing and payment operations between each corporation, wherein the agency processing server receives data uploaded from any of the first data terminals of the payer. The payment destination is the same Analyze multiple invoice data to calculate total payment amount For each payee a calculation step of calculating For each payee The calculated payment statement data Summary of payment statement data a sending step of sending the payment statement data to any one of the first data terminals of the payers; a proxy payment step of executing a proxy payment via the bank system to a payment bank account according to the payee information registered from the data terminal of the payer in response to receiving payment authentication for the payment statement data from any one of the first data terminals of the payers; and a notification step of notifying any one of the first data terminals of the completion of payment based on the proxy payment amount data executed in the proxy payment step. The first data terminal includes an approval screen display step for displaying a one-tap approval screen for making a lump-sum payment of the combined payment statement data containing a mixture of different payees presented in the sending step, and after receiving a one-tap approval instruction on the one-tap approval screen from the first data terminal, the proxy payment step executes proxy payments via the bank system to different payment bank accounts according to the payee information registered from the data terminal of the payer. It is characterized by: [Explanation of symbols]

[0144] 1-1~1-N Payment source PC 4. Proxy Processing Server 5. Agent Bank 7-1~7-N Payment PC 8 BM Management Server

Claims

1. An electronic payment agency business system that provides a payment agency service by communicating among a plurality of first data terminals that perform accounting processing for the payer, a plurality of second data terminals that perform accounting processing for the payee, a bank system that executes payment processing, and an agency processing server that executes billing and payment operations between each corporation, The proxy processing server a calculation means for analyzing a plurality of bill data items for the same payee uploaded from any one of the first data terminals of the payment source and calculating a total payment amount for each payee; a transmitting means for transmitting payment statement data that is a compilation of the payment statement data calculated for each payee by the calculating means to any one of the first data terminals of the payers; an agent payment means for executing an agent payment via the bank system to a payment bank account according to the payment destination information registered from the data terminal of the payment source in response to receiving payment authentication for the payment statement data from any first data terminal of the payment source; notification means for notifying any one of the first data terminals of the completion of payment based on the proxy payment amount data executed by the proxy payment means; an electronic payment agency business system, characterized in that the first data terminal is equipped with an approval screen display means for displaying a one-tap approval screen for making a lump-sum payment of the combined payment statement data presented by the transmission means, which contains a mixture of different payees; and after receiving a one-tap approval instruction on the one-tap approval screen from the first data terminal, the proxy payment means executes proxy payments via the bank system to different payment bank accounts according to the payee information registered from the data terminal of the payer.

2. The proxy processing server includes a calculation means for calculating a fee for the proxy payment executed by the proxy payment means; a first fee notification means for notifying a first data terminal that is the payer or a second data terminal that is the payee of the fee calculated by said calculation means; 2. The electronic settlement agent business system according to claim 1, further comprising:

3. The proxy processing server includes a calculation means for calculating a fee for the proxy payment executed by the proxy payment means; a second fee notification means for notifying the first data terminal, which is the payer, of the fee calculated by the calculation means; 2. The electronic settlement agent business system according to claim 1, further comprising:

4. The electronic payment agency business system according to claim 2, characterized in that the calculation means calculates the fee for the first data terminal that is the payment source or the second data terminal that corresponds to the payment recipient based on a predetermined sharing ratio.

5. The proxy processing server a business mile storage means for storing the number of business miles; a mileage issuing processing means for issuing business miles corresponding to the payment amount of the first data terminal to the corporation that is the payment source; The electronic payment agency business system according to claim 1, characterized in that it communicates with a business mile management server equipped with a mile exchange processing means for exchanging the number of business miles to be applied to the required payment in accordance with instructions from the first data terminal.

6. 2. The electronic payment agency business system according to claim 1, wherein the first data terminal is capable of setting in advance to the proxy payment means whether to pay the combined payment statement data presented by the transmission means, which includes a mixture of different payees, in one lump sum or to pay each payee individually for each same payee.

7. A payment agency processing method for an electronic payment agency business system that provides a payment agency service by communicating among a plurality of first data terminals that perform accounting processing for the payer, a plurality of second data terminals that perform accounting processing for the payee, a bank system that executes payment processing, and an agency processing server that executes billing and payment operations between each legal entity, comprising: The proxy processing server a calculation step of analyzing a plurality of bill data items for the same payee uploaded from any one of the first data terminals of the payment source and calculating a total payment amount for each payee; a sending step of sending payment statement data that summarizes the payment statement data calculated for each payee in the calculation step to any one of the first data terminals of the payers; an agent payment step of executing an agent payment via the bank system to a payment bank account according to the payment destination information registered from the data terminal of the payment source in response to receiving payment authentication for the payment statement data from any first data terminal of the payment source; a notification step of notifying any one of the first data terminals of the completion of payment based on the proxy payment amount data executed in the proxy payment step, a payment agent processing method for an electronic payment agent business system, characterized in that the first data terminal comprises an approval screen display step of displaying a one-tap approval screen for making a lump-sum payment of the combined payment statement data presented in the sending step, which includes a mixture of different payees; and after receiving a one-tap approval instruction on the one-tap approval screen from the first data terminal, the proxy payment step executes proxy payments via the bank system to different payment bank accounts according to the payee information registered from the data terminal of the payer.

Images