JP7804263B2 - Electronic payment agency business system and payment agency processing method for electronic payment business system - Google Patents

Description

The present invention relates to an electronic payment system and a payment agent processing method for the electronic payment system.

In recent years, electronic payment systems have evolved, corporate payment methods have become increasingly electronic, and there has been a noticeable trend toward the easy use of credit card payments to reduce payment workloads.

In addition, 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.

Each of these agency systems has its own unique agency processing system, ensuring convenience for contracted companies regarding business payments and providing services that make inter-company payment processing more efficient. This reduces the burden of complicated tasks such as payment processing on the seller's side and credit checks, payment confirmation, and payment collection on the buyer's side.

Japanese Patent Application Laid-Open No. 2021-33939

However, the price of using these payment processing systems is primarily to reduce operational costs, and the value of their use is uniform, so there is no clear difference between the different payment processing systems.

The present invention has been made to solve the above problems, and its object is to provide an electronic payment system and a payment agency processing method for an electronic payment system that can provide high-value-added payment services to companies that use the payment agency system.

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.

One or more embodiments of the electronic payment system according to the present invention can provide high-value-added bank payment services to corporations that use the payment agency system.

The drawings illustrate particular embodiments of the present invention, including essential features of the invention as well as alternative and preferred embodiments.
1 is a block diagram illustrating the configuration of an electronic settlement agency business system according to an embodiment of the present invention. 1. FIG. 4 is a chart illustrating the flow of data processing by an introduction processing unit of the proxy processing server shown in FIG. 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. 1. FIG. 4 is a flowchart illustrating the flow of a payment destination registration process performed by the payment source PC shown in FIG. 1. FIG. 4 is a flowchart illustrating the flow of an invoice upload process by the payer's PC shown in FIG. 1. FIG. 4 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. 4 is a chart illustrating the flow of processing by the billing unit for the payer of the proxy processing server shown in FIG. 1. FIG. 4 is a chart illustrating the flow of processing by a mileage issuance processing unit of the proxy processing server shown in FIG. 1. FIG. 4 is a chart illustrating the flow of processing by a mile exchange processing unit of the proxy processing server shown in FIG. 10 is a flowchart illustrating a fee payment process in the electronic settlement agency business system according to the present embodiment. 10 is a flowchart illustrating a fee payment process in the electronic settlement agency business system according to the present embodiment. FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. FIG. 2 is a diagram showing an example of a user interface in the electronic payment agency business system according to the present embodiment. 1. FIG. 4 is a chart illustrating the flow of one-tap processing by the proxy processing server shown in FIG. 1. FIG. 4 is a chart illustrating the flow of one-tap processing by the proxy processing server shown in FIG.

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 payment processing system shown in FIGS. 1 to 11, and include not only essential configurations of the invention but also optional and preferred embodiments.
<System configuration explanation>
First Embodiment
Next, the best mode for carrying out the present invention will be described with reference to the drawings.

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 payee 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 PCs 1-1 to 1-N) that perform accounting processing for the payer, a plurality of second data terminals (payment destination PCs 7-1 to 7-N) that perform 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.

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.

In addition, logic that cannot be expressed using Appsync and GraphQL is implemented using Lambda as the Appsync resolver, and is run as a disposable volatile process, fundamentally preventing the introduction of viruses and malware.

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

In Figure 1, 1-1 to 1-N are payer 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 and installed from the proxy processing server 4.
Here, the payer PCs 1-1 to 1-N are assumed to be PCs managed by various corporations (for example, 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, thereby enabling the execution of 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 the accounting staff at the payer's PC and the payee's PC to view the web screens provided by the TobePay system and enter the necessary information and perform approval work with good visibility via a common, highly operable screen.

4 is 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 diagram) 5. The agent bank system 5 is connected to payment-designated bank systems 51-1 to 51-N, including bank systems across the country and around the world.

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 to the payee unit 45, and a billing processing unit 46 for the payer, and a main control unit (made up of various processors) controls communication processing and executes data processing for various services.

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 for payer 46 will be described in detail with reference to the drawings described below.

The BM management server 8 is composed of a mileage issuing processor 81 and a mileage exchange processor 82, and uses a memory unit (not shown) to issue business miles according to the payment amount via the ToBPay system and manage the business mileage balance. The mileage management process and mileage exchange process via the ToBPay system will be described later.

In this embodiment, the BM management server 8 is equipped with a business mile storage means for storing the number of business miles, and the mile issuance processing unit 81 performs a process of issuing business miles to the paying corporation according to the payment amount of the paying PC serving as the first data terminal. Furthermore, the mile exchange processing unit 82 performs a process of exchanging the business miles 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.

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 billing 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.

The proxy processing server 4 also has a controller unit equipped with a CPU, ROM, RAM, etc., and a communications unit that communicates with the payer PCs 1-1 to 1-N and the payee PCs 7-1 to 7-N via the Internet I, enabling transactions to be encrypted to ensure security.

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 via email or other means, an electronic certificate is attached to prevent damage such as the leakage of customer data due to phishing scams or hacking.

It is assumed that each of 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 is equipped with a communications processing unit that communicates with the Internet network I, providing an environment for encrypted communications.

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.

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

In an electronic payment agency business system configured in this way, the calculation function of the proxy payment unit 45 to the payee on the proxy processing server 4 analyzes multiple invoice data uploaded from any of the payer's PCs 1-1 to 1-N to calculate the total payment amount.

Furthermore, the communication function of the agent processing server 4 transmits the payment statement data calculated by the payee proxy payment unit 45 to one of the first data terminals of the payer. Furthermore, in response to receiving payment authentication for the payment statement data from one of the payer PCs 1-1 to 1-N, the payee proxy payment unit 45 executes a proxy 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.

Furthermore, the communication function of the proxy processing server 4 notifies 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.

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 a 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]

Figure 2 is a chart explaining 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 corporate personnel. Note that in this specification, the name of the payment service provided by the proxy processing server 4 is referred to as ToBPay.

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 the Internet Network I or through sales activities.

At this point, 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, for example, as a PDF file).

At this time, once the paying corporation signs the document containing the terms and conditions (including the digitally signed document), the document (PDF file) is notified to the ToBPay system via the Internet network I. In response, the ToBPay system performs an acceptance process to accept the paying corporation into the ToBPay system. Specifically, the introduction processing unit 41 displays the UI screen for entering an email address for new registration shown in Figure 12 on the display device of the paying PC 1-1. An email address is entered on this screen (SIGN UP). 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 Figure 13), and then the required information such as password, password re-entry, name, telephone number, and registered account company information, such as company name (corporate name), job type, and telephone number, is entered into the UI screen for new registration shown in Figure 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 payer PC1-1, completing the new registration process.

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 accepting paying corporation 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 registered address of the paying corporation, and the paying user (accounting officer) 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]

Figure 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 Figure 1. Here, "acquirer" refers to 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 Figures 18 to 23.

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

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 payer PC 1-1. The BM acquirer registration unit 42 then presents the UI screen shown in Fig. 20 to the payer PC 1-1. Here, when the operator (client) of the payer PC 1-1 follows the message displayed on the screen and confirms that the authentication email has been received, the login process is complete. If the authentication email has not been received, the operator clicks the resend button to have the authentication email resent, and the same process is repeated.
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 PC 1-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 the name, address, and corporate information on the UI screen, the client clicks 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 its service details (earning miles, sharing miles, and using miles) are presented to the client. When the Next button is clicked, the BM acquirer registration unit 42 presents the UI screen (Business Miles My Page screen) shown in Fig. 23 to the payer PC 1-1. On this screen, the client can check their mileage balance, shareable mileage balance, news, and the contents of their digital mile card.
Also, a confirmation button, a use button, a save button, and a share button are arranged at the bottom of the UI screen shown in FIG.

[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 payment destination registration unit 43 of the agent processing server 4 sends a payment destination registration request email to the payment source PCs 1-1 to 1-N.

At this point, the payer PCs 1-1 to 1-N open the https: registration screen in their web browsers and enter the payee's address and contact information, as well as their own BM account (acquirer registration number, etc.) for each payment.

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

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 PCs 1-1 to 1-N, the payee registration unit 43 issues a payee registration form and sends the issued payee registration form to the payee PCs 7-1 to 7-N of the payee corporation.

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. If the person in charge of the payee PC of the payee corporation agrees to the proposal, they enter 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 send the application form with the necessary information entered to the agent processing server 4 that makes up the ToBPay system via the Internet network I.

In response, 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.

The ToBPay system then notifies the users of the payee PCs 7-1 to 7-N of the installation instructions for the issued management screen.

Meanwhile, when the payee registration unit 43 of the agent 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 agent 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 payee registration has been completed.Then, the issued registration completion notification indicating that the payee registration has been completed is sent by email to one of the payer PCs 1-1 to 1-N via the Internet network I.

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

[First invoice upload process]
Fig. 5 is a flowchart 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. 26 to 31.

The invoice upload unit 44 of the proxy processing server 4 accepts and processes invoice data according to the invoice that the paying corporation is to pay that month, 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.

Specifically, when a payee user operating a payee PC 7-1 through 7-N issues an invoice to a payer, the payee 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 through 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 through 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 through 7-N for entering invoice information. The person in charge of the payee PC 7-1 through 7-N can then enter necessary information, such as the billing date, payment deadline, orderer name, business partner name, transaction contact name, subject, billing amount (excluding tax), and remarks, on 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 Business Partner 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, the invoice upload unit 44 receives invoice data (PDF file) containing the invoice items for the specified invoice source entered by the payee user.

In response, 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.

On the other hand, if a separate upload is used, the payee user of the payee PCs 7-1 to 7-N issues the bill data to one of the payer users of the payer PCs 1-1 to 1-N via the Internet network I.

When a paying user of any of the paying PCs 1-1 to 1-N receives this, they approve the invoice data (PDF file) and upload it to the invoice upload unit 44 of the proxy processing server 4 via the Internet network I.

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.

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 corporation screen, and an approval instruction for the contents of the invoice is awaited. The TP payment recipient corporation screen also has an approval button for approving the uploaded invoice. The approval button is used when there are multiple approvers, so the payment recipient user corresponding to the superior may give the final approval.
The UI screen shown in Fig. 30 shows a detailed screen of invoice information displayed on the payer's PC. The UI screen shown in Fig. 31 corresponds to a state in which a tab is assigned to each registered invoice project, and a list of invoices currently related to the initial development of the TBP is displayed. The UI screens shown in Figs. 32 and 33 are configured to allow confirmation of the payment status and completion of payment.
The UI screens shown in Figures 34 and 35 are configured to enable confirmation of the payment status and transfer status of invoices related to the registered "XXX project."

[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.

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

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 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.

In this way, once the payee proxy payment unit 45 has completed 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.

As a result, 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. Here, the payee user operating the payee PCs 7-1 to 7-N confirms via the TP payee corporation screen that the transfer by the ToBPay system has been completed, and gives 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 the proxy payment for one bill has been completed.

As a result, the display device of the agent processing server 4 updates the information for 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 devices of payee PCs 7-1 to 7-N is updated to indicate payment has been completed.

[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 of the ToBPay system is started.

First, the payer billing processing unit 46 receives a payment completion notification and performs billing processing to one of the payer PCs 1-1 to 1-N for the amount transferred on its behalf. This notifies the billing information on the TP payer corporation screen displayed on the display device of the proxy processing server 4.

In this way, when the paying user of paying PC 1-1 to 1-N receives the bill from the paying user billing processor 46, the billing amount is paid by bank transfer to the account specified at the agent bank 5 designated by the ToBPay system. Once the ToBPay system confirms the transfer by the paying user of paying PC 1-1 to 1-N, the paying user billing processor 46 updates the information indicating the payment progress for the paying corporation on the TP operator screen to "deposit confirmation," and updates the information indicating the payment status on the TP paying corporation screen to "transaction completed."

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

When the payer user shown in Figure 7 updates the TP payer corporation screen to transaction completion by the payer billing processing unit 46, the mileage issuance processing unit 81 of the BM management server 8 starts processing.

The mileage issuance processing unit 81 references a mileage management table (not shown), reads the mileage award information set for the paying corporation that 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.

As a result, the mileage issuing 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.

[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.

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 goods or the like can be input.

The mile exchange processing unit 82 of the BM management server 8 then subtracts the instructed points from the previous total number of points based on the instructed points to complete the exchange process.

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 the UI screen shown in Figure 37), 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 on paying PCs 1-1 to 1-N via the Internet network I, and then ends the process (see the UI screen shown in Figure 36).

[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 payment made on its behalf, and can use the accumulated business miles to fund product purchases and travel expenses.

In addition, business miles can also be used to cover fees paid when using the ToBPay system, which will be described later.

Second Embodiment
10 is a flowchart illustrating the fee payment process in the electronic payment agency business system according to this embodiment. (1) to (19) indicate the individual steps. This process begins after a payment agency contract is concluded between the ToBPay system contract manager and the payer (corporation).

Furthermore, each step is realized by the CPU of the controller unit of the proxy processing server 4 reading and executing the ToBPay system program stored in the memory unit. The ToBPay system program is also configured to be updated as needed to prepare for changes in regulations, tax rates, etc.

First, when the proxy processing server 4 that makes up the ToBPay system receives a registration request from one of the payer PCs 1-1 to 1-N (1), the accounting staff of the payer PCs 1-1 to 1-N receive approval from the payee via the ToBPay system from one of the payee PCs 7-1 to 7-N that are the monthly payment counterparties (2), and it is determined whether all registrations (K=N) have been completed (3).

If it is determined that all registrations are complete, the invoice information requested by, for example, the accounting staff of Company A operating the payment source PC 1-1 will be uploaded to the ToBPay system in accordance with the closing date (4).

Next, it determines whether today is the payment closing date for Corporation A currently being processed (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 payer 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).

Next, the ToBPay system refers to the payment contract terms and determines whether the terms of the proxy payment with the payer are Condition 1 (where the commission for the proxy payment is shared between the payer and the payee) (7).

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 payer PCs 1-1 to 1-N. Once it receives an approval instruction for the payment confirmation 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 contracting with the ToBPay system, and transfers the money to the respective bank accounts specified by the payee.

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.

On the other hand, if it is determined in step (7) that the proxy payment conditions with the payment source are condition 2 (where the payment source bears the fee for the proxy payment), proceed to step (10).

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, and determines whether approval has been received from the corporation's accounting officer.

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 contract with the ToBPay system, and transfers the funds to the respective bank accounts specified by the payees (11).

Next, the ToBPay system reads the fee billing conditions for this payment from the memory unit (12) and determines whether the fee sharing ratio between the payer and the payee is 100%:0% (13).

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 process ends.

On the other hand, if in step (13) the ToBPay system determines that the fee sharing ratio between the payer and 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).

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

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).

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 more corporations use the ToBPay system, 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 the payee and the payee will receive and accumulate miles.

Regarding miles, corporations that enter into a contract with the ToBPay system may choose to prioritize cashback to the corporation over mileage redemption, either in lieu of mileage awarding at the time of signing the contract or in combination with it at any time.

In addition, the system may be configured to individually lower 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).

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

At that 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 claim (17).

In contrast, the proxy processing server 4 may calculate the fee for the proxy payment so that the payer bears the entire cost.

In that case, the proxy processing server 4 notifies the first data terminal of the calculated fee invoice.

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 pre-set sharing ratio (see steps (13) to (15) in Figure 10).

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

Third Embodiment
11 is a flowchart illustrating the fee payment process in the electronic payment agency business system according to this embodiment. (21) onwards indicate each step. This process is initiated after a payment agency contract is concluded between the ToBPay system contract manager and the payer (corporation). Each step is implemented by the CPU in the controller of the agency processing server 4 reading and executing the ToBPay system program stored in the memory.

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

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

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 network I (23).

The ToBPay system then waits for an instruction to approve the proxy payment statement sent by the payer (24), and upon receiving the instruction to approve the proxy payment statement sent by the payer, the system sends an advance remittance (prepayment remittance) from the proxy bank 5 managed by the ToBPay system to the designated account of the bank specified by the registered payee (25).

Next, the ToBPay system notifies the payer who made the advance payment of a payment request for the total amount advanced (26), and once the payer confirms that the payment has been deposited into the designated account at 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.

On the other hand, if in step (22) the ToBPay system determines that the proxy payment condition is not 1, the ToBPay system sends the proxy payment statement to one of the payer PCs 1-1 to 1-N via the Internet network I (29). Once the system confirms that the payer has transferred the total payment amount listed on the statement to the proxy bank 5 designated by the ToBPay system (30), it proceeds to step (26).

As a result, depending on the ToBPay system's usage history, 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 ToBPay system's agent bank 5 in step (29), or a reimbursement method, in which the ToBPay system pays the total amount of the agent payment in advance in step (25).

In this way, the electronic payment agency system frees the payer from having to perform the cumbersome, individual payment procedures when it comes to payments between a paying user (corporation) and a paying user (corporation) who have signed a contract with the ToBPay system, and allows payments to be completed in a single, consolidated payment.

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.

[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 can be expected.

Fourth Embodiment
In the above embodiment, the payment process between corporations (B2B) has been described in detail, but the ToBPay system may be expanded by adding a factoring function (accounts receivable purchasing function).

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 BM UI screen can be displayed for either the payer or the payee.

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

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

Here, when the user of the payer PC or payee PC selects the tab for using miles, the UI screen shown in Figure 39 is displayed on the display device of the payer PC or payee PC. This example shows an operation in which the user of the payer PC or payee PC exchanges the miles they have accumulated for a gift certificate that can be used on a shopping site, such as Amazon (registered trademark).

When the Next button is clicked on this screen display, the mile exchange processing unit 82 controls the UI screen on the display device of the payer PC or payee PC to switch to the UI screen shown in Figure 40.

Here, you can confirm that issuing the gift certificate will update your current mileage status. Furthermore, when you click the Next button, the mile exchange processing unit 82 controls the UI screen on the display device of the payer PC or payee PC to switch to the UI screen shown in Figure 41.

Here, when the 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.

Sixth Embodiment
In the first embodiment described above, when the proxy processing server 4 processes billing processes 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.

Therefore, the payment source PC may be configured to approve payments once a month so that proxy payments to the payee can be completed.

[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. This system is configured to accommodate the following methods for registering invoices: (1) registering invoice information, (2) uploading the invoice and then automatically registering it using OCR (image recognition), and (3) automatically reading the invoice information by sending a PDF of the invoice to a dedicated address. Furthermore, if there are multiple invoice data, (1) each can be individually set to "approved" or "rejected" in the system. Furthermore, (2) in case individual approval or rejection is too tedious, it is also possible to collectively set "approved" or "rejected" in the system.
In either case (1) or (2) above, the second invoice upload process is characterized in that a notification is sent via the specified method (chat such as LINE (registered trademark) or email), and with a single tap on "Approve," automatic bank withdrawal is made.
When issuing the flow of the invoice upload process by the payee PCs 7-1 to 7-N shown in Figure 1, the necessary invoice items (including a code specifying the invoice source, invoice details, and total invoice 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 screen for inputting invoice category information. Here, when the edit button assigned to the business partner is clicked, a UI screen for inputting invoice information such as that shown in Figure 28 is displayed on the display device of the payee PCs 7-1 to 7-N.

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, business partner name, transaction person name, subject, billing amount (excluding tax), and notes, into the UI screen shown in Figure 28.

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

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 TP operator screen once that all invoices uploaded by the payee users have been received.

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

After all of these individual bills from each payee are tallied, when a payer user on one of payer PCs 1-1 to 1-N receives invoice data requesting approval for the total amount, they approve 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 aforementioned proxy BK5 based on the payment information approved with one tap.

From this point on, the flow of invoices is reversed from the first embodiment, and after the proxy payment to the payee is completed, a process is executed to send information about each invoice for which the payee has been notified to the paying PC via network I, as shown in Figure 44. This allows the details of each invoice uploaded by each payee for the monthly closing to be received in a post-approval format.

Here, an example of the data processing sequence in the second invoice upload process will be described in detail.
The payee registers invoice data in the system by email, uploading, or inputting information (1).
Next, ToBPay compiles the invoice data registered by the payee into billing information (2). Next, the billing information in step (2) is notified to the paying user mainly 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 is initiated.
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 the screen the usage details, showing how much was paid to which company (if a payment was made) (6).
In this way, with ToBPay payments using the second invoice upload process, the paying user can complete payment instructions not only through PC operation but also through smartphone operation (simply tapping on the notification). Therefore, the paying user can perform payment operations using a PC, and can also complete payment instructions through smartphone operation when away from home, significantly improving operability.
Furthermore, in terms of reducing the workload for ToBPay users, (1) consolidating invoices, (2) creating transfer data from invoices, (3) transferring money, (4) clearing, (5) accounting entries, and (6) checking (2) to (5) will no longer be necessary, 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 payees.

[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 for the person operating the payer's PC regarding invoices uploaded by each payee.

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

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

For example, if a medical institution were to introduce the ToBPay system, they could 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 could result in a significant reduction in labor hours.

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, for expenses such as meals provided at the facility, nursing care supplies for purchasing equipment, equipment installation costs, and printing costs incurred in administrative work.

The disclosure of the present invention described above can be summarized at least as follows.
(1) An electronic payment agency business system that provides payment agency services through communication between 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 legal entity, wherein the agency processing server comprises: a calculation means that analyzes a plurality of invoice data for the same payee that are uploaded from any of the first data terminals of the payer, and calculates a total payment amount for each payee; a transmission means that transmits payment statement data that summarizes the payment statement data calculated by the calculation means for each payee to any of the first data terminals of the payer; and a payment authentication for the payment statement data from any of the first data terminals of the payer, The system comprises: a proxy payment means for executing a proxy payment via the bank system to a payment bank account in accordance with payment destination information registered from the data terminal of the paying party; and a notification means for notifying a first data terminal of the completion of payment based on the proxy payment amount data executed by the proxy payment means , wherein the first data terminal comprises 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 includes a mixture of different payment destinations; and after receiving a one-tap approval instruction on the one-tap approval screen from the first data terminal, the proxy payment means executes a proxy payment via the bank system to each of the different payment bank accounts in accordance with the payment destination information registered from the data terminal of the paying party .

(2) The proxy processing server is characterized by comprising 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 request.

(3) The proxy processing server is characterized by comprising 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 the payment, of a request for the fee calculated by the calculation means.

(4) The calculation means is characterized in that it 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 preset sharing ratio.

(5) The proxy processing server communicates 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 payment amount from the first data terminal, and a mile exchange processing means for exchanging the business miles for the number of business miles to be applied to the required payment in accordance with instructions from the first data terminal.

( 6 ) The first data terminal is characterized in that it is possible to set in advance to the proxy payment means whether to pay the combined payment statement data presented by the transmission means, which contains a mixture of different payees, in a lump sum or to pay each of the same payees individually .

( 7 ) A payment agency processing method for an electronic payment agency business system that provides payment agency services 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 legal entity, wherein the agency processing server includes a calculation step of analyzing a plurality of invoice data with the same payee uploaded from any of the first data terminals of the payer and calculating a total payment amount for each payee ; a transmission step of transmitting payment statement data that summarizes the payment statement data calculated for each payee in the calculation step to any of the first data terminals of the payer; and a payment authentication for the payment statement data from any of the first data terminals of the payer, The method comprises: a proxy payment step of executing a proxy payment via the bank system to a payment bank account in accordance with the payment destination information registered from the data terminal of the paying party; and a notification step of notifying any first data terminal of the completion of payment based on the proxy payment amount data executed by the proxy payment step , wherein 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 containing a mixture of different payment destinations 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 the different payment bank accounts in accordance with the payment destination information registered from the data terminal of the paying party .

1-1 to 1-N Payment source PC
4 Agent processing server 5 Agent banks 7-1 to 7-N Payment destination PC
8. BM management server

Claims (7)

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 . 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: 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: The electronic payment agency business system described in 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. 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. 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 . 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 .