Information provision device, information provision method and program

JP2024143989A5Pending Publication Date: 2026-06-22PAYPAY CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
PAYPAY CO LTD
Filing Date
2023-08-08
Publication Date
2026-06-22

AI Technical Summary

Technical Problem

Conventional techniques do not provide suitable invoice support for member stores that use electronic payment as providers of products or services.

Method used

An information providing device and method that calculates consumption tax amounts and rounds fees for electronic payments, creating invoices that meet invoice requirements, and provides an interface for member stores to manage and issue qualified invoices.

Benefits of technology

Enables suitable handling of invoices for member stores using electronic payment, reducing accounting burdens and ensuring compliance with tax regulations.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 00000000_0000_ABST
    Figure 00000000_0000_ABST
Patent Text Reader

Abstract

To provide an information provision device capable of providing a qualified invoice to affiliated stores using electronic settlement as providers of products or services, information provision method and program.SOLUTION: An information provision device used by affiliated stores using an electronic settlement service as providers of products or services and providing information to the affiliated stores via an interface for the affiliated stores, includes: an acquisition part for acquiring information of a fee for every settlement that an electronic settlement service provider acquires from each affiliated store; and a processing part for calculating a consumption tax amount by multiplying the fee by a consumption tax rate and creating an invoice satisfying invoice requirements by performing fraction processing for every invoice of settlement within a prescribed range.SELECTED DRAWING: Figure 4
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to an information providing device, an information providing method, and a program. [Background technology]

[0002] Conventionally, a technology has been disclosed that makes it possible to easily determine whether or not a trading partner is an invoice business operator (Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2022-179153 A Summary of the Invention [Problem to be solved by the invention]

[0004] The prior art has not provided suitable invoicing support for merchants who use electronic payments as providers of goods or services.

[0005] The present invention has been made in consideration of the above circumstances, and one of its objectives is to provide an information provision device, information provision method, and program that can provide suitable invoice handling for affiliated stores that use electronic payment as providers of goods or services. [Means for solving the problem]

[0006] One aspect of the present invention is an information providing device used by an affiliated store that uses an electronic payment service as a provider of goods or services, and provides information to the affiliated store via a member store interface, the information providing device comprising: an acquisition unit that acquires information on fees for each payment that the electronic payment service operator acquires from the affiliated store; and a processing unit that multiplies the fee by a consumption tax rate to calculate the amount of consumption tax, and creates an invoice that meets invoice requirements by performing rounding for each invoice for payments within a specified range. Effect of the Invention

[0007] According to one aspect of the present invention, it is possible to provide suitable invoice handling for affiliated stores that use electronic payment as providers of goods or services. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram showing an example of a configuration for realizing an electronic payment service. [Diagram 2] This is a sequence diagram (part 1) illustrating the general flow of electronic payment. [Diagram 3] This is a sequence diagram (part 2) illustrating the general flow of electronic payment. [Figure 4] 1 is a configuration diagram of a payment server 100 according to a first embodiment. [Diagram 5] FIG. 13 is a diagram showing an example of the contents of user information 172. [Figure 6] FIG. 13 is a diagram showing an example of the contents of affiliated store / store information 176. [Figure 7] FIG. 13 is a diagram showing an example of the contents of payment details information 178 for each affiliated store. [Figure 8] FIG. 1 is a diagram showing an example of the flow of sales etc. in an electronic payment service. [Figure 9] This is a figure showing an example of a qualified invoice issuance menu screen IM1 provided by the member store interface 72. [Figure 10]This figure shows an example of an interface screen IM2 when the closing date is selected as the range of payments to be included in eligible invoices. [Figure 11] FIG. 13 is a diagram for explaining how to correct a qualified invoice. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, with reference to the drawings, an embodiment of an information providing device, an information providing method, and a program of the present invention will be described. The information providing device provides information to affiliated stores via an interface for affiliated stores, which is used by affiliated stores that use the electronic payment service as a provider of goods or services. Focusing on the general user side, the electronic payment service is provided by cooperation between an application program and a payment server, and in the following description, the application program is referred to as a payment application. The electronic payment service is a service that supports payments related to the purchase of goods or services at a store. The store is, for example, a physical store (real store) that exists in the real world, but may also include a virtual store for electronic commerce. The virtual store may include a store provided by an entity different from the operator of the electronic payment service. In that case, when making a payment for shopping at the virtual store, the screen is controlled to transition to an interface screen of the electronic payment service. In the electronic payment service, the store is treated as belonging to, for example, an affiliated store (brand), and processing such as payment when a purchase is made at a store is mainly performed between the user and the affiliated store. Hereinafter, the electronic payment service provided to the user side will be described first, and then the interface for affiliated stores will be described.

[0010] [Electronic payment service] Fig. 1 is a diagram showing an example of a configuration for realizing an electronic payment service. The electronic payment service is realized mainly by a payment server 100. The payment server 100 communicates with, for example, one or more user terminal devices 10, one or more first store terminal devices 50, one or more second store terminal devices 70, and one or more employee terminal devices 80 via a network NW. The network NW includes, for example, the Internet, a LAN (Local Area Network), a wireless base station, a provider device, and the like.

[0011] The user terminal device 10 is, for example, a portable terminal device such as a smartphone or a tablet terminal. The user terminal device 10 is a computer device having at least an optical reading function, a communication function, a display function, an input reception function, and a program execution function. In the following description, components for realizing these functions are referred to as a camera, a communication device, a touch panel, a CPU (Central Processing Unit), etc. In the user terminal device 10, a processor such as a CPU executes a payment application 20, thereby operating to provide an electronic payment service to a user in cooperation with a payment server 100. The payment application 20 is installed in the user terminal device 10 from, for example, an application store, and controls the camera, communication device, touch panel, etc.

[0012] The first store terminal device 50 is installed, for example, in a store. The first store terminal device 50 is a computer device having at least a product price acquisition function, an optical reading function, a program execution function, and a communication function. The first store terminal device 50 includes a so-called POS (Point of Sale) device, and the product price acquisition function and the optical reading function may be realized by the POS device. The store code image 60 is placed in the store, and is a code image such as a QR code (registered trademark) printed on a paper or plastic medium. The store code image 60 may be displayed on a display placed in the store (which may be the display of a terminal device such as a smartphone).

[0013] The second store terminal device 70 is used by the operator of the affiliated store. The second store terminal device 70 is a smartphone, a tablet terminal, a personal computer, or the like. An interface 72 for affiliated stores runs on the second store terminal device 70. The interface 72 for affiliated stores may be an app for affiliated stores or a browser. The interface 72 for affiliated stores accepts coupon settings and the like made by the operator of the affiliated store and transmits them to the payment server 100. The second store terminal device 70, which is a smartphone, has the function of displaying a code image corresponding to a store code image and reading a code image displayed by the user terminal device 10 by executing the app for affiliated stores.

[0014] The employee terminal device 80 is used by an employee of the electronic payment service provider. The employee terminal device 80 is a smartphone, a tablet terminal, a personal computer, or the like. An employee interface 82 runs on the employee terminal device 80. The employee interface 82 may be an employee app or a browser. The employee interface 82 performs processes such as accepting corrections made by employees to invoices that have already been issued.

[0015] The payment server 100 realizes electronic payment based on payment information received from the user terminal device 10 or the first store terminal device 50. The first store terminal device 50 may include a POS device and an affiliated store server, in which case the payment information is sent from the POS device via the affiliated store server to the payment server 100. In the following explanation, no distinction is made between these two and it is assumed that the payment information is sent from the first store terminal device 50.

[0016] 2 and 3 are sequence diagrams illustrating the general flow of electronic payment. There may be two patterns of electronic payment: pattern 1 and pattern 2.

[0017] In the case of pattern 1 (hereinafter referred to as user scan) shown in FIG. 2, the user terminal device 10 with the payment application 20 activated decodes the store code image 60 by the optical reading function (S1). The store code image 60 includes store URL (Uniform Resource Locator) information. This store URL is an electronic payment service domain to which store-identifying information is added, and is associated with an affiliated store ID, a store ID, etc. in the payment server 100 (described later). The payment application 20 transmits the first payment information including the store URL and the account ID to the payment server 100 (S2). The payment server 100 searches for store information (described later) from the affiliated store ID and the store ID corresponding to the store URL, acquires the affiliated store name and the store name information (S3), and transmits it to the payment application 20 (S4). The user inputs the payment amount into the user terminal device 10 on the screen on which the affiliated store name and the store name are displayed (S5). Then, the user terminal device 10 generates second payment information including at least the payment amount, and transmits it to the payment server 100 (S6). The payment server 100 performs electronic payment based on the received second payment information (S7). The payment server 100 then transmits a payment completion notice (information for displaying a payment completion screen) to the payment application 20 (S8), and the payment application 20 displays the payment completion screen (S9). Note that when the store code image 60 is displayed on a display installed in the store, the store code image 60 may include not only the store URL but also information on the payment amount. In this case, the step of the user inputting the payment amount is omitted, and the information on the payment amount is included in the first payment information and transmitted to the payment server 100. Information on the affiliated store name and the store name may be included in the payment completion screen and displayed.

[0018] In the case of pattern 2 (hereinafter referred to as store scan) shown in FIG. 3, when the payment application 20 is started, when a payment operation is performed in the payment application 20, when an automatic update timing (e.g., every minute) occurs, and at other timings, the payment application 20 transmits a request for issuing a one-time code to the payment server 100 (S11). The payment server 100 generates a one-time code (S12) and transmits it to the payment application 20 (S13). The payment application 20 displays a code image such as a QR code or a barcode generated based on the one-time code (S14). The user holds (presents) the display surface of the user terminal device 10 over the first store terminal device 50, and the first store terminal device 50 decodes the code image by an optical reading function and obtains the one-time code, etc. (S15). The first store terminal device 50 then generates payment information including the one-time code, payment amount, affiliated store ID, store ID, etc., and transmits it to the payment server 100 (S16). The payment amount information is acquired in advance by reading a barcode or manually entering it. The payment server 100 identifies the user corresponding to the one-time code based on the received information and performs electronic payment (S17). The payment server 100 then transmits a payment completion notice to the payment application 20 (S18), and the payment application 20 displays a payment completion screen (S19).

[0019] Note that electronic payment may be performed using only one of the above patterns. Furthermore, the "account ID" described in FIG. 2 may be other information (e.g., a phone number) that can be used as user identification information. Furthermore, issuance of a one-time code may be omitted in the store scan, and the payment application 20 may display a code image generated based on the user's account ID. In this case, the payment server 100 identifies the user corresponding to the account ID instead of identifying the user corresponding to the one-time code.

[0020] [Payment server] FIG. 4 is a configuration diagram of the payment server 100 according to the first embodiment. The payment server 100 includes, for example, a communication unit 110, a payment content providing unit 120, a payment processing unit 130, an information management unit 140, a content providing unit for affiliated stores 150, and a storage unit 170. The content providing unit for affiliated stores 150 includes an acquisition unit 152 and a processing unit 154. The components other than the communication unit 110 and the storage unit 170 are realized, for example, by a hardware processor such as a CPU executing a program (software). Some or all of these components may be realized by hardware (including circuitry) such as an LSI (Large Scale Integration), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a GPU (Graphics Processing Unit), or may be realized by cooperation between software and hardware. The program may be stored in advance in a storage device (a storage device with a non-transient storage medium) such as an HDD (Hard Disk Drive) or flash memory, or may be stored in a removable storage medium (non-transient storage medium) such as a DVD or CD-ROM, and installed in the storage device by inserting the storage medium into a drive device.

[0021] The storage unit 170 is a HDD, a flash memory, a RAM (Random Access Memory), etc. The storage unit 170 may be a NAS (Network Attached Storage) device that the payment server 100 can access via a network. The storage unit 170 stores information such as user information 172, payment content information 174, affiliated store / shop information 176, payment details information for each affiliated store 178, and invoice information for each affiliated store 180.

[0022] The communication unit 110 is a communication interface for connecting to the network NW. The communication unit 110 is, for example, a network interface card.

[0023] The payment content providing unit 120 has, for example, a function of a Web server, and provides information (content) for displaying various screens of the electronic payment service to the user terminal device 10. The payment content providing unit 120 appropriately reads necessary content from the payment content information 174 and provides it to the user terminal device 10. The user terminal device 10 accepts various inputs by the user while the content is being played by the payment application 20, and transmits the above-mentioned payment information and the like to the payment server 100.

[0024] The payment processing unit 130 performs payment processing based on the payment information transmitted by the user terminal device 10 or the first store terminal device 50. The payment processing unit 130 performs payment processing while referring to the user information 172.

[0025] FIG. 5 is a diagram showing an example of the contents of the user information 172. The user information 172 is an example of the registration information of a user. The user information 172 is, for example, a user URL, an account ID, a telephone number, a password, as well as information associated with an email address, a user ID, a name, an address, a date of birth, a registration date, a charge balance, a post-payment setting, a post-payment limit, a post-payment usage amount, a post-payment available amount, a payment method setting, a bank account, a credit card number, a charge history information, and a payment history information. The user URL is used for a remittance process between users. When registering for the electronic payment service, it is necessary to register a telephone number and a password. The account ID is issued to the user by the payment server 100, and the user ID is an ID that can be set by the user at will (does not have to be set). Similarly, the email address, and the name, address, and date of birth are information that can be set by the user at will (does not have to be set). The registration date is the date on which the user registered for the electronic payment service (the date on which the account was created). Hereinafter, the user's instance (electronic payment account) to which this information is associated will be referred to as an account.

[0026] The charge balance is information indicating the balance of electronic money that is set by a user by transferring money to an account in advance. Methods of transfer include transfer from an ATM (Automatic Teller Machine) of a designated business (bank) and transfer from a registered bank account. The deferred payment setting is information indicating whether or not the setting for enabling deferred electronic payment has been completed, and is set to either "completed" or "not completed." The payment method setting is setting information indicating whether the user will make electronic payment from the charge balance or deferred payment at that time. The bank account and credit card number are information on a bank account or credit card number (account number, card number) that can be deposited into an electronic payment service. The charge history information is a history of the user transferring money to an electronic payment service in advance to increase the charge balance. The payment history information is information indicating the details of the payment made by the user (date and time, store ID of the store where the purchase was made, payment amount, payment method, etc.) for each payment.

[0027] 6 is a diagram showing an example of the contents of affiliated store / store information 176. The affiliated store / store information 176 includes, for example, a first table 176A in which an affiliated store ID and a store ID are associated with a store URL, a second table 176B in which an affiliated store name and sales amount (described above) are associated with an affiliated store ID, and a third table 176C in which a store ID is associated with a store ID. In addition to this information, the affiliated store / store information 176 may also include information such as the category of the affiliated store or store, the location of the store, and payment patterns.

[0028] The information management unit 140 manages user information 172 and affiliated store / store information 176 based on information acquired from the user terminal device 10 and the second store terminal device 70. The information management unit 140 adds new records to, edits, and deletes the user information 172 and affiliated store / store information 176.

[0029] [Electronic payment] When payment information is acquired from the user terminal device 10 or the first store terminal device 50, the payment processing unit 130 refers to the user information 172 to acquire the "payment method setting" of the user. For a user whose "payment method setting" is set to "charge balance", the payment processing unit 130 performs electronic payment as follows. For example, the payment processing unit 130 performs electronic payment by decreasing the charge balance managed in association with the user ID and increasing the item value of the affiliated store's sales. The item value of the affiliated store's sales is not used as electronic money itself, for example, and an amount corresponding to the item value of the sales is transferred to a bank account in a cycle according to an agreement between the affiliated store and the electronic payment service.

[0030] The payment processing unit 130 performs electronic payment for users whose "setting information" is set to "deferred payment" as follows. Deferred payment is set separately from "credit payment" in cooperation with a credit card company, which is a separate entity from the operator of the electronic payment service, and the operator of the electronic payment service acts as a creditor and allows electronic payment that is not dependent on the charge balance within the deferred payment limit. In order to receive the deferred payment service, a credit card provided by the operator of the electronic payment service may be required. The amount used for deferred payment is settled on the payment date of the following month, for example, by debiting from a bank account, for one month. In this case, the payment processing unit 130 performs provisional payment by adding the payment amount to the deferred payment amount and subtracting the same amount from the available deferred payment amount, and when the closing date comes, it performs processing to debit the payment for the current month on the payment date of the following month as described above, or requests the operator of the credit card company to perform such processing. In addition, if the payment amount exceeds the available deferred payment amount at the time of provisional payment, an error notification is returned to the payment application 20.

[0031] [Services for affiliated stores] The member store content providing unit 150 provides information to member stores via the member store interface 72. The member store content providing unit 150, which performs processing while referring to the member store-specific payment details information 178 and the member store-specific invoice information 180, is an example of an information providing device. In FIG. 4, the information providing device is a function of the payment server 100, but the information providing device may be a device separate from the payment server 100.

[0032] The acquisition unit 152 of the member store content providing unit 150 refers to the member store-specific payment details 178 and acquires information on the fee for each payment acquired by the electronic payment service provider from the member store. The acquisition unit 152 does not acquire information every time a payment is made (although this may be the case), but acquires information on the fee for each payment within the target range when the processing unit 154 is about to create an invoice. FIG. 7 is a diagram showing an example of the contents of the member store-specific payment details 178. The member store-specific payment details 178, for example, associates the service plan to which the member store subscribes, the closing date (meaning the date on which the amount to be deposited in the electronic payment service provider or the amount to be deposited by the provider is determined, and the deposit date is slightly later), and the payment details with the member store ID. The service plan is defined by the upper limit of the total payment amount and the fee rate, and one member store can select multiple service plans. The payment details are information for each payment, and correspond to information such as the date (or date and time) of the payment, the store ID, and the payment amount with the payment ID that can identify the payment. The acquisition unit 152 acquires information on the fee for each payment by multiplying the payment amount by a predetermined commission rate (e.g., several percent) that the affiliated store pays to the electronic payment service provider.

[0033] The processing unit 154 multiplies the fee acquired by the acquisition unit 152 by the consumption tax rate to calculate the consumption tax amount, and performs rounding for each invoice for settlement within a predetermined range to create an invoice that satisfies the invoice requirements (hereinafter, a qualified invoice). For rounding, the issuer of the invoice can select any method from rounding up, rounding down, rounding to the nearest digit, etc.

[0034] FIG. 8 is a diagram showing an example of the flow of sales and the like in an electronic payment service. First, an affiliated store provides a product or service to a user. The fee excluding tax is assumed to be 10,000 yen. The user pays the electronic payment service operator 11,000 yen, consisting of the fee of 10,000 yen and consumption tax of 1,000 yen, by debiting the charge balance or the like. The electronic payment service operator records the fee received from the affiliated store (assuming the fee rate is 5% and the fee is 500 yen) and the 50 yen consumption tax on the fee as the affiliated store's sales, totaling 10,450 yen. At this time, if the affiliated store has received a qualified invoice (payment notice) for the fee from the electronic payment operator, it can receive a consumption tax deduction for the 50 yen consumption tax on the fee, but if it has not received the invoice, it cannot receive a consumption tax deduction. Invoice requirements include the name or title and registration number of the business issuing the invoice, the transaction date, transaction details, the total amount excluding or including tax for each tax rate and the tax rate, the consumption tax amount divided by tax rate (rounding must be done for each invoice), the name or title of the business (affiliated store) to which the document is to be delivered, etc. Since all of this information is available to the settlement server 100, the processing unit 154 creates a qualified invoice based on that information.

[0035] The processing unit 154 also creates a total invoice that lists at least the total amount of consumption tax on one or more invoices together with the one or more invoices. The total invoice may also list the total amount of invoices on one or more invoices. Since the consumption tax amount on the total invoice is the total amount of rounding, the total invoice itself does not meet the requirements for a qualified invoice. However, since the number of qualified invoices may become enormous if accounting is done only using qualified invoices, the total invoice is provided to the affiliated store because it is convenient to have something that lists the amounts of money to be deposited and withdrawn between the electronic payment business operator and the affiliated store in a simple manner. The affiliated store can store the qualified invoices in-house in preparation for tax investigations, etc., and can easily process deposits and withdrawals using the total invoice. This will be described later.

[0036] The processing unit 154 allows the affiliated store to select the issuance mode of the qualified invoice via the affiliated store interface 72. FIG. 9 is a diagram showing an example of the qualified invoice issuance menu screen IM1 provided by the affiliated store interface 72. The qualified invoice issuance menu screen IM1 is provided with a first switch SW1 for selecting which service plan the qualified invoice is to be issued for, and a second switch SW for selecting whether the range of payments to be included in the qualified invoice is to be per closing date (from the day after the closing date set for each affiliated store to the next closing date), per payment ID specified by the affiliated store (multiple payment IDs may be selected), or another range. The processing unit 154 issues the qualified invoice within the range according to the switch selected by the operator of the affiliated store.

[0037] 10 is a diagram showing an example of the interface screen IM2 when a closing date is selected as the range of payments to be included in a qualified invoice. When the third switch SW is operated on the interface screen IM2, the processing unit 154 creates a total invoice for the displayed period in a format such as PDF (Portable Document Format) and makes it available for download from the affiliated store interface 72. When the fourth switch SW4 is operated on the interface screen IM2, the processing unit 154 creates a qualified invoice for the operated period in a format such as PDF and makes it available for download from the affiliated store interface 72. A similar interface screen may also be provided when "By payment ID" is selected on the qualified invoice issuance menu screen IM1.

[0038] Here, we will explain rounding again. Let's assume that the consumption tax amounts on fees for each closing date shown in Figure 10 are as follows. In this case, because rounding (rounding up in this case) is necessary on the qualified invoices for each closing date, the rounded consumption tax amount for each target period will be as shown on the right. The total invoice will show 2,270 yen, which is the total of the consumption tax amounts after rounding. Note that the total invoice does not show information for each target period, but instead shows information including the "total of rounded consumption tax amounts for each target period" and the "grand total" for each service plan and tax rate.

[0039] Target period: Consumption tax amount (simple calculation): Consumption tax amount (after rounding) 20221025~20221101: 450.3 : 451 20221102~20221108: 842.4 : 843 20221109~20221116: 715.2 : 716 20221117~20221124: 259.6 : 260 Total: 2267.5: 2270

[0040] The "simple calculation" described above is simply multiplying the tax rate for each payment and adding them up, and the total of 2267.5 yen is never actually presented to the affiliated store. If, in the above example, we were to round up the total invoice for the entire period (20221025~20221124) and issue a qualified invoice, the consumption tax amount would be 2268 yen, which is 2267.5 yen rounded up. This is not a problem for the affiliated store (because the difference of 2 yen is assumed to be "rounded up," and the profit and loss relationship changes depending on the method of rounding), but since various calculations for affiliated stores in electronic payment services are performed for each "closing date," doing so would increase the cost of system modification. On the other hand, if the affiliated store is sent only the qualified invoice for each closing date, it may be necessary to add up the amount according to the accounting period, which would increase the burden on accounting processing. Therefore, in this embodiment, an existing system is used to create a qualified invoice for each closing date, and a total invoice is also created and provided to the affiliated store in order to avoid increasing the accounting burden on the affiliated store. This allows the affiliated store to receive a consumption tax deduction without increasing the accounting burden on the affiliated store. In other words, an optimal invoice response can be provided.

[0041] The following describes how to correct a qualified invoice in response to instructions transmitted from the employee interface 82. FIG. 11 is a diagram for explaining how to correct a qualified invoice. The employee interface 82 displays an interface screen IM3 for inputting an affiliated store ID and a service plan. When an employee inputs an affiliated store ID and a service plan, the processing unit 154 refers to invoice information by affiliated store 180 and displays, via the employee interface 82, a list screen IM4 of already-issued qualified invoices that correspond to the entered affiliated store ID and service plan. The invoice information by affiliated store 180 is information in which already-issued qualified invoices are associated with the affiliated store ID and service plan. When an employee selects one of the qualified invoices shown in the list of already-issued qualified invoices and specifies a process such as correcting an erroneous invoice (correction request), the processing unit 154 corrects the qualified invoice based on the entered information.

[0042] According to the embodiment described above, it is possible to provide suitable invoice handling for affiliated stores that use electronic payment as providers of goods or services.

[0043] The above describes the form for carrying out the present invention using an embodiment, but the present invention is not limited to such an embodiment, and various modifications and substitutions can be made within the scope that does not deviate from the gist of the present invention. [Explanation of symbols]

[0044] 10 User terminal device 20. Payment App 70 Second store terminal device 72 Merchant Interface 80 Employee terminal equipment 82 Employee Interface 100 Payment Server 120 Payment Contents Provider 130 Payment processing unit 140 Information Management Department 150 Contents for Affiliated Stores Department 152 Acquisition Department 154 Processing section 178 Payment details for each participating store 180 Invoice information for each affiliated store

Claims

1. An information provision device that provides information to a merchant via a merchant interface, used by a merchant that uses an electronic payment service as a provider of goods or services, A processing unit that calculates the amount of consumption tax for each invoice for multiple payments based on the transaction fee for each payment obtained by the electronic payment service provider from the merchant, and creates multiple qualified invoices by rounding off the amount for each invoice. A total invoice creation unit that creates a total invoice including a total consumption tax amount obtained by summing the consumption tax amounts of the multiple qualified invoices that have been rounded by the processing unit, An information-providing device equipped with the following features.

2. The processing unit calculates the consumption tax amount by multiplying the fee by the consumption tax rate and performs the rounding process for each invoice for settlements within a predetermined range to create a qualified invoice that satisfies the invoice requirements. The information providing device according to claim 1.

3. The settlements within the aforementioned predetermined range are those made from the day following the closing date determined for each participating merchant until the next closing date. The information providing device according to claim 2.

4. The settlements within the aforementioned predetermined range are settlements specified by a settlement ID that can identify the settlement. The information providing device according to claim 2.

5. The aforementioned processing unit, Create a qualified invoice for each merchant ID that can identify the merchant and each pricing plan. The qualified invoice is modified in response to a correction request received via an employee interface used by an employee of the electronic payment service provider, specifying the merchant ID and the fee plan. The information providing device according to claim 1.

6. An information provision device that provides information to a merchant via a merchant interface, used by a merchant that uses an electronic payment service as a provider of goods or services, Based on the transaction fees obtained by the electronic payment service provider from the merchants, the provider calculates the consumption tax amount for each invoice for multiple transactions, and creates multiple qualified invoices by rounding down each invoice. To create a total invoice that includes the total consumption tax amount obtained by summing the consumption tax amounts of the aforementioned multiple qualified invoices after rounding, Information provision method.

7. A processor in an information provision device that provides information to a merchant via a merchant interface, used by a merchant who uses an electronic payment service as a provider of goods or services, Based on the transaction fees that the electronic payment service provider obtains from the merchants for each transaction, the provider calculates the consumption tax amount for each invoice for multiple transactions and creates multiple qualified invoices by rounding off the fractional amount for each invoice. To create a total invoice that includes the total consumption tax amount obtained by summing the consumption tax amounts of the aforementioned multiple qualified invoices after rounding, A program for that purpose.