Information processing apparatus, information processing system, and program

Abstract

To automatically create a document based on the law, or store data.SOLUTION: An information processing apparatus includes a processing circuit. The processing circuit specifies a payer based on a billing request from a biller, presents a bill addressed from the biller to the payer, the bill including necessary matters, sends, when the biller makes a request to send the generated bill, the bill to the payer or notifies the payer that the bill has been issued, and stores the bill in a database.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present disclosure relates to an information processing device, an information processing system, and a program. [Background technology]

[0002] When invoicing for a transaction, the items that must be recorded vary greatly depending on the laws that apply at the time of the transaction or settlement. For example, as of 2024, the number of required items will increase due to the invoice system that was introduced in October 2023, and it will also be necessary to retain data that can be referenced for those items.

[0003] There are cloud services and other similar services that automatically calculate and store invoice items and tax rates, but automated services that support the invoice system, for example, are still in their infancy. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Publication No. 2019-109555 Summary of the Invention [Problem to be solved by the invention]

[0005] Therefore, one non-limiting problem that the embodiments of the present disclosure aim to solve is to automatically create legal documents or store data. The problem that the embodiments of the present disclosure aim to solve can also be, as some further non-limiting examples, a problem corresponding to the effects described in the embodiments. In other words, a problem that corresponds to at least one of the effects described in the description of the embodiments of the present disclosure can be the problem that the present disclosure aims to solve. [Means for solving the problem]

[0006] The information processing device includes a processing circuit that identifies a billing destination based on a request from a billing source, presents an invoice addressed to the billing destination from the billing source and including necessary information, and, upon a request from the billing source to send the generated invoice, sends the invoice to the billing destination or notifies the billing destination that the invoice has been issued, and stores the invoice in a database. [Brief explanation of the drawings]

[0007] [Figure 1] FIG. 1 is a diagram showing an example of the configuration of an information processing system according to an embodiment. [Figure 2] 10 is a flowchart illustrating an example of processing of an information processing system according to an embodiment. [Figure 3] 10 is a flowchart illustrating an example of processing of an information processing system according to an embodiment. [Figure 4] 10 is a flowchart illustrating an example of processing of an information processing system according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0008] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. The drawings are used for explanation purposes, and the shape, size, and size ratio of each component in an actual device do not necessarily have to be the same as those shown in the drawings. Furthermore, since the drawings are simplified, components necessary for implementation other than those shown in the drawings are also assumed to be appropriately provided.

[0009] <Management of contracts and qualified invoices>

[0010] 1 is a diagram schematically illustrating an information processing system according to an embodiment. The information processing system 1 includes a server 10 provided in a cloud and a client 20 that can access the server 10 in the cloud. The information processing system 1 may be configured as a system that executes various processes in the server 10 on the cloud in response to a request from the client 20.

[0011] The information processing system 1 may be configured to include one or more servers 10. The one or more servers 10 may be configured to include a processing server that executes processing and a file server that stores files.

[0012] The client 20 is a terminal used by a user, and the user can use the services provided by the server 10 via the client 20. The client 20 is, for example, a computer, smartphone, tablet terminal, etc. owned by the user, but is not limited to these.

[0013] In this disclosure, the term "information processing device" may refer to a server 10 or a client 20. The information processing device includes at least a storage unit and / or a processing unit. These components may be separate or integrated semiconductor devices. The processing unit may include a processing circuit that executes processing in the information processing device.

[0014] The processing circuit may include a general-purpose processor (such as a CPU (Central Processing Unit) or a GPU (Graphics Processing Unit)) or a dedicated processor (such as an ASIC (Application Specific Integrated Circuit)). At least a portion of these processors may include analog and / or digital circuits. At least a portion of these processors may be formed of rewritable circuits such as an FPGA (Field Programmable Gate Array).

[0015] Furthermore, when the term "program" is used, it indicates a program for specifically realizing software-based information processing using any of the information processing devices in the information processing system 1, which is a hardware resource. At least a part of the processing circuit can be realized by referencing an executable file or the like stored in the memory unit.

[0016] The information processing system 1 can provide the information processing of the present disclosure as a cloud service. The information processing system 1 can provide the service using a method such as SaaS (Software as a Service), or can provide the service in a form where a server is accessed via a browser or the like.

[0017] 2 is a flowchart showing an example of processing of the information processing system 1 according to an embodiment. The processing in FIG. 2 shows processing between a seller client 20 and the server 10. It is assumed that data about seller users is stored in the server 10 in advance. If user data does not exist in the server 10, the server 10 can acquire and generate the necessary data about a new user in response to a request from the client 20.

[0018] The client 20 transmits a billing request to the server 10 based on input from the user (S100). The client 20 accepts requests that specify at least the billing destination. The user inputs data required for billing via a UI (User Interface, including GUI: Graphical User Interface) displayed on a browser or software (hereinafter referred to as a browser, etc.) as a cloud service, and the client 20 transmits a bill based on the input data to the server 10.

[0019] As a non-limiting example, the information processing system 1 may be configured to provide an invoice template or the like in the client 20 and accept input of necessary information such as the billing destination, billing item name, and billing amount (including quantity) from the user. Data such as the billing destination and billing items can be registered in advance in the server 10 by the user, and can be set in a selective format based on this registered information. The user can also set billing items and the like using a template or the like that is prepared in advance by the server 10.

[0020] As a non-limiting example, the information processing system 1 may be configured to accept data of an invoice separately created by a user via the interface of the client 20. In this case, the client 20 may appropriately extract the invoice recipient, invoice items, invoice amount, etc. based on OCR or metadata embedded in the document. Alternatively, the client 20 may transmit the invoice data to the server 10, and the server 10 may extract the invoice recipient, invoice items, invoice amount, etc.

[0021] The client 20 may also be configured to present information on other users who are registered as business partners of the user from the user. In other words, the user may use the information processing system 1 to select a billing destination that is registered in advance as a business partner.

[0022] Furthermore, the information processing system 1 can transmit to the server 10 the specification of the contract related to the billing input by the user via the client 20. The input of the contract by the user can also be configured so that the client 20 can select a contract, memorandum, etc. related to an already concluded contract by referring to a database related to both parties in the server 10. In the case where the billing destination is selected as described above, the server 10 can also be configured to present a contract, etc. related to the business partner selected by the user as the billing destination based on a request from the client 20.

[0023] In addition, the user-related information may be stored in the server 10 or in a memory area within the client 20. In this case, customer information and the like is not released to the outside, and input from the user is accepted within the client 20 and encrypted, thereby realizing safer communication.

[0024] The client 20 may also be configured to have the user select billing items, etc. based on past transaction records based on the specified billing information received from the user. The client 20 may also be configured to present an invoice that lists billing items, billing amounts, etc. based on past records based on the billing information received from the user and have the user confirm them.

[0025] In addition, the client 20 can provide the user with various processes based on past transaction records. For example, the client 20 may present candidate business partners to the user, or may suggest transaction items, transaction amounts, etc. after identifying a business partner. The user can select from the options proposed by the client 20, or can create a new invoice for the business partner via the client 20.

[0026] The client 20 may be configured to accept input of the transaction date from the user. If the user does not input the transaction date, the client 20 may set the invoice issue date as the transaction date.

[0027] The server 10 receives a billing request from the client 20, acquires information on the billing source and billing recipient related to the bill accepted by the client 20, and checks whether a contract has been concluded between the billing source and billing recipient that allows them to settle the billing item (S200).

[0028] The contract does not exclude the inclusion of contracts for transactions other than the invoiced items. The contract also allows for business in accordance with the items within the scope described. In general, contracts are often concluded according to the actual circumstances of the transaction. The contract in this disclosure may also correspond to this general actual circumstances of the transaction.

[0029] That is, the billing user can conclude a contract with the billed user that includes various services in line with the business via the client 20. In this case, the billing user can not only make a claim related to the billing items limited to the content of the contract concluded via the client 20, but also realize a claim related to the business between the billing user and the billed user, within or outside the scope of the contract.

[0030] In other words, the information processing system 1 is capable of issuing, settling, and managing invoices for items related to work outside the contract, as well as items related to work within the contract concluded between the two users.

[0031] As described above, when the client 20 receives a specification of the contract related to the accepted claim, the server 10 may extract the contract related to the claim from the database in which it is stored. If extraction is not possible, the server 10 may perform processing equivalent to S202: NO shown below.

[0032] If a contract relating to the billing item between the biller and the billee exists in the database (S202: YES), the process moves to branch A, which indicates processing for the billee.

[0033] The contract is not limited to one stored in the database, but may be a contract already concluded between the requester and the requestee, or some electronic document in lieu of the contract that the requester has sent to the server 10 in the processing of S100. In this case, the server 10 also proceeds to the processing of branch A.

[0034] 3 is a flowchart showing the processing in branch A according to one embodiment. After the server 10 has confirmed the existence of a contract concluded for the billing item, it issues an invoice based on the received billing request.

[0035] The server 10 issues an invoice based on the information acquired from the client 20 (S204). The server 10 can create an invoice that includes legally required information. The server 10 can, for example, create an invoice that complies with the invoice system. For example, the server 10 can include information on the invoice it creates, including the issuer's name (which may be replaced with a trade name), registration number, transaction date, transaction details (transaction items), transaction price, applicable tax rate, consumption tax amount, and recipient's name.

[0036] If the server 10 cannot find the registration number associated with the user in the database, it can request the user to input the registration number via the client 20. The user inputs the registration number via the client 20, and the client 20 notifies the server 10 of the registration number input by the user, and the server 10 can associate this registration number with the user and register it in the database.

[0037] Depending on instructions from the user via the client 20, the server 10 may create an invoice that conforms to the legal system, listing the applicable tax rate but not the amount of consumption tax. The server 10 may also create an invoice that does not list the recipient's name. The server 10 may also list all invoices for a certain period of time together. In this case, the server 10 may request the user to provide invoices, statements, etc. showing transactions during this period, and after receiving the documents from the user via the client 20, issue a combined invoice.

[0038] If there is any missing information about the other party (billing destination), the server 10 can notify the other party's client 20 to request the input of the information. When the information about the other party is complete, the server 10 can finalize the invoice.

[0039] Regarding other missing information, the server 10 can notify the user of the missing information via the client 20, which can be operated and viewed by the user as needed, and an invoice can be created when all the information is collected.

[0040] The server 10 notifies and sends the issued invoice to the billing destination client 20. At this time, the server 10 can also send the client 20 a link for making payment related to the invoice.

[0041] The server 10 can also send information about the contract together with the invoice to the client 20 to whom the invoice is issued. The server 10 can notify the client 20 to whom the invoice is issued of information about the concluded contract linked to the invoice to be issued, for example, a link to view the contract.

[0042] The server 10 can also set a billing deadline. The billing deadline may be set by the user via the client 20. If the content is not submitted by the billing deadline or the payment is not completed by the billing deadline, the server 10 or the client 20 can send a reminder to the billing destination via the client 20 as appropriate. In addition, the server 10 or the client 20 can also remind the user via the billing destination client 20 at a set timing before the set billing deadline.

[0043] The server 10 can store information about issued invoices in a database, and can store and manage the invoices as invoices for which payment has not yet been completed.

[0044] The client 20 presents the user with a link (hyperlink) for making payment along with the contents of the invoice (S310). The client 20 may transition to a state where it is waiting for approval of the payment from the user. The user can also temporarily suspend the payment presented to the client 20 and transition to the above-mentioned state where it is waiting for approval, and then execute the payment at any timing.

[0045] The client 20 may record that the content has been presented. If the content has not been presented to the user within a predetermined period, the client 20 may notify the user again. The record of the content confirmation may be managed on the server 10 side. The fact that the content has been presented to the billing destination may also be in a form that can be referenced by the client 20 that made the request.

[0046] If the client 20 also notifies information about the contract in S210, the client 20 can present the information about the contract together with the information on the issued invoice. Also, the client 20 to be invoiced can present the contract in the database selected by the user via the client 20 from which the invoice was made.

[0047] The user can refer to data such as bills stored in the server 10 via the client 20 by following a hyperlink or the like presented to the client 20 on a browser or application, for example.

[0048] The client 20 may present the issued invoice to the user, or may present information related to the issued invoice in an appropriate data format. For example, the client 20 may provide data to the user in a database format, a file format such as CSV, other text file format, a format for any application (accounting software, tax software, or other software for referencing or editing data), any other binary file format, or any description language format such as MHT or XML.

[0049] The client 20 accepts whether or not the user approves (agrees) to the payment related to the issued invoice (S312). If the user does not approve (agree) (S312: NO), the client 20 notifies the server 10 that the payment has not been approved.

[0050] The server 10 notified that the request was not approved notifies the requester that the request was not approved (S212). Subsequent processing, for example, allows the users to resolve the issue and reissue an invoice that the users have agreed upon, which can be performed according to the processing in Figure 2. As a non-limiting example, the subsequent flow may be the same as the flow from branch B in Figure 2.

[0051] In other words, both users may execute the contract conclusion process via the information processing system 1, or they may conclude the contract outside the information processing system 1 and notify the information processing system 1 of this, thereby realizing the re-billing and settlement process.

[0052] If approved (S312: YES), the client 20 accepts the payment method from the user and requests the server 10 to make the payment using that payment method (S314). The server 10 executes the payment based on the request from the client 20 (S214). Details of the payment method will be described later.

[0053] If the settlement cannot be executed, the server 10 notifies the user via the client 20 that the settlement could not be executed, and can request the user to change the means so that the settlement can be executed and to execute the settlement again.

[0054] After the settlement is completed, the server 10 can link the information indicating that the settlement has been completed and manage the invoice related to the claim (S216). The server 10 can present the invoice, linked with the information indicating that the settlement has been completed, at any timing based on a request from the user (the biller and / or the billee) via the client 20 or an agent who is legally permitted to view invoices, etc. and can refer to the user's information (for example, a tax accountant, certified public accountant, etc. authorized by the user).

[0055] As described above, the information processing system 1 enables smooth electronic processing of invoice issuance, settlement, etc. based on billing requests. These processes can be completed on the cloud, improving user convenience. Furthermore, document management can be automatically performed electronically, enabling annual processing, settlement, etc. to be performed with high efficiency and accuracy.

[0056] Next, a case where the contract cannot be confirmed in S202 will be described.

[0057] 4 is a flowchart illustrating a non-limiting example of the process for branch B according to one embodiment. If the server 10 is unable to confirm the existence of a contract concluded for the billing item, it can notify both users of the contract-related process required to claim the received billing request.

[0058] The server 10 requests the contract pertaining to the claim from the client 20 that made the claim (S220). Although not shown in the flowchart, if an concluded contract that already exists in the database can be used or invoked at this stage, the client 20 accepts the user's selection of the contract to be used or invoked and notifies the server 10, and the server 10 can execute the process of branch A shown in Figure 3 based on the contract.

[0059] Although not shown in the flowchart, a contract is not a required component of the process. The billing client 20 can also request the issuance of an invoice for work outside the contract that has been concluded. The client 20 may obtain a flag for billing items related to work outside the contract and notify the server 10. Conversely, the client 20 may obtain a flag for billing items related to the concluded contract and notify the server 10.

[0060] Based on information that the requested claim can be processed even outside the contract, the information processing system 1 can skip the processes from S220 to S222 and proceed to branch A. In this case, upon request from the claimant user, the information processing system 1 can automatically execute the process of branch A even in the absence of a contract.

[0061] For example, the information processing system 1 can continue the invoice issuance process without checking for ongoing contracts from the biller to the billee, contracts for related items, or contracts for different items to the same billee.

[0062] In addition, it is also possible to process additional charges from the billing source, additional invoices, etc. By omitting the processing of these contract requests, for example, it becomes possible to more smoothly realize ongoing business transactions, etc.

[0063] When the client 20 receives a request for a contract from the server 10, it notifies the user of this. After receiving this notification, the client 20 accepts input from the user regarding the contract and transmits the contract to the server 10 (S120). The client 20 can have the user select whether or not the contract has been concluded between the billing party and the billed party, and transmit the selection result together with the contract to the server 10.

[0064] The client 20 may notify the user that a contract will be uploaded. The contract to be uploaded may be a contract (such as a memorandum of understanding) for an already concluded contract.

[0065] The client 20 may also display a contract template to the user to assist in creating the contract. In this case, the client 20 may transmit the contract created according to the template to the server 10.

[0066] When the client 20 receives an unsigned contract from a user, the client 20 may also acquire information related to the electronic signature. By acquiring information related to the certificate of the electronic signature, etc., it becomes possible to proceed with the contract signing process in the cloud service. In addition, a user who has previously used an electronic signature in the information processing system 1 can store information related to the electronic signature in the server 10 or the client 20 and reuse it.

[0067] The server 10 that has received the contract stores the contract in association with both parties and checks whether the contract has already been concluded between the billing party and the billed party (S222). If the contract has already been concluded between the billing party and the billed party (S222: YES), the server 10 can execute the process from branch A.

[0068] If the received contract is an unsigned contract (S222: NO), the server 10 transmits information related to this contract to the client 20 to be billed (S224). The server 10 transmits the information related to the contract to, for example, the client 20 to be billed. As in the above, the information related to the contract may be information such as a hyperlink for accessing the contract in the server 10. The server 10 may also notify the user to be billed to encourage them to conclude the contract.

[0069] The billing client 20 can present a contract to the user based on the received information (S320).

[0070] After presenting the information, the client 20 receives a decision from the user as to whether or not to conclude the contract (S322). That is, the user can confirm the information in the presented contract and then decide whether or not to conclude the contract, and notify the server 10 of this decision via the client 20.

[0071] When the client 20 to be billed receives input from the user that the contract can be concluded, the client 20 to be billed can also obtain a certificate of the electronic signature, etc., related to the user to be billed and send it to the server 10. The server 10 or the client 20 can also manage information related to the electronic signature, etc., related to the user to be billed, in the same way as the information of the requester.

[0072] Furthermore, the billing destination client 20 may store information on the electronic signature of the billing destination user, and in this case, when it receives input from the user that the conclusion is possible as described above, it may automatically transmit a certificate of the electronic signature or the like to the server 10. As another example, when it receives notification from the billing destination client 20 that the conclusion is possible, the server 10 may be implemented to search for information on the certificate of the billing destination user's electronic signature or the like by referring to a database, and if it exists, to automatically conclude the contract based on the information on this certificate.

[0073] The server 10, having received the notification from the client 20, determines whether or not a contract can be concluded based on the response from the client 20 to which the billing was made (S226). If the server 10 determines that the contract can be concluded (S226: YES), for example, if both parties' electronic signatures, etc. are obtained, the server 10 can conclude the contract on the memorandum, i.e., complete the electronic contract.

[0074] As described above, the electronic signature etc. may be automatically extracted by the server 10 or automatically sent to the server 10 by the client 20, and the server 10 can conclude an electronic contract based on the obtained certificate.

[0075] Note that, according to the information processing system 1 of this embodiment, electronic contracts can be made using digital signatures, etc., but the present disclosure does not exclude other methods. For example, the information processing system 1 can receive a contract signed by a non-digital signature from a requesting user and prompt the requesting user to sign a non-digital signature to conclude the contract. For example, the requesting client 20 can notify the user to print the acquired contract, sign it, digitize it, and upload it. Also, only one party can use a digital signature.

[0076] If the contract cannot be concluded (S226: NO), the server 10 notifies the requesting client 20 of that fact and can repeat the process of branch B. When the client 20 receives the notification, it notifies the user of that fact (S122). Also, the server 10 and the client 20 can notify the user that the contract could not be concluded in addition to the process of branch B.

[0077] Also, although not shown in the flowchart, if the billing destination client 20 receives an input indicating that the billing destination client will conclude the transaction, but the billing destination client 20 is unable to conclude the transaction using the means selected by the user, the server 10 can notify the user via the billing destination client 20 that the billing destination client 20 will review or correct the means of concluding the transaction.

[0078] The server 10 stores the contract for the concluded contract, linking it to both parties. It can also store the items related to the invoice received in S100, linking them to the contract. As a result, from the next time onwards, the user can select the invoice items for the invoice recipient via the client 20 and request an invoice, and the server 10 will automatically refer to the contract.

[0079] In addition, the billed user can complete settlement of the same billing item from the same billing source received via the client 20 on the cloud service of the information processing system 1.

[0080] Furthermore, the user can refer to and receive the contract document stored in the server 10 at any time as needed.

[0081] As described above, the information processing system 1 makes it possible to not only settle invoices but also conclude contracts for cloud services.

[0082] The notification to both users can be sent to the accounts registered by both users, for example, by email, SNS, SMS, or push notification to the device on which the software is installed.

[0083] When a user who is registered as a qualified invoice issuing business issues a qualified invoice according to the above procedure, the other user can properly receive input tax credit. Qualified invoices issued by the information processing system 1 are properly stored on the server 10. Therefore, transactions related to such qualified invoices can be subject to input tax credit.

[0084] Furthermore, by issuing the qualified invoice, the user who issues the invoice can avoid being victimized by the other user negotiating a price reduction for the consumption tax.

[0085] As described above, according to this embodiment, the information processing system 1 can properly manage contracts and qualified invoices. As a result, users can carry out proper transactions while eliminating concerns about invoices.

[0086] The above is not particularly limited to the billing method. For example, the server 10 or the client 20 can create a bill for the same amount more quickly based on a fixed-amount bill created by the user. The server 10 or the client 20 can also set the number of payments for the bill at the user's request. The server 10 or the client 20 can also issue a simple bill that does not fall under the category of a qualified bill.

[0087] The user may set a deadline for a claim via the information processing system 1. In this case, the information processing system 1 may notify the billing recipient and the billing source of a claim that is past its deadline. Also, a reminder may be automatically sent to the billing recipient a predetermined number of days before the billing deadline expires.

[0088] <About payment>

[0089] The information processing system 1 can employ, as a payment method, a credit card, a designated bank account to transfer or withdraw funds, or a transaction using virtual currency implemented by blockchain or the like. The information processing system 1 may also have a wallet function. A user indicates their intention to make a payment by selecting any method presented by the information processing system 1 via the client 20, and the client 20 can notify the server 10 of the accepted payment method.

[0090] The server 10, having received the approval of the payment and the notification of the payment method, executes the payment based on the payment method received from the client 20 (S214). If the payment cannot be made, the server 10 can return the payment to the client 20 to select a payment method or to approve the payment. If the payment is returned, the client 20 can notify the user of this and notify the user to select an appropriate payment method again or to approve the payment again.

[0091] When the server 10 is notified by the client 20 that payment is to be made by credit card, the server 10 may inquire with the credit card company and immediately determine whether or not payment can be made. In this case, if payment is not possible, the server 10 may immediately notify the user via the client 20 that payment was not possible. If the user's credit card is not registered, the server 10 may prompt the user to notify the user of credit card information via the client 20.

[0092] When the server 10 is notified by the client 20 of a payment request by depositing money from a bank account, it can inquire about this to the bank and determine whether the payment has been completed based on whether the deposit has been made. Also, when the server 10 is notified by the client 20 of a payment by transfer from a bank account, it can notify the user of the transfer destination to an account related to the information processing system 1 and determine whether the transfer has been executed at the appropriate time. Also, it may be configured to accept transfers from a bank account by any means, such as Pay-easy (registered trademark).

[0093] This implementation may be implemented using the functionality of a virtual bank, which allows the server 10 to automatically perform processes such as depositing and clearing.

[0094] As another example, the server 10 may have an interface that allows the client 20 to transfer funds directly to the bank account of the biller. In this case, the transfer is directly made from the billing recipient to the biller, and the information processing system 1 may determine that the settlement has been made when the biller or the transfer recipient notifies the information processing system 1 of a transfer confirmation.

[0095] As another non-limiting example, the deposit can be made by debiting a bank account designated by the user.

[0096] If debit from a bank is selected and the user's bank account is not registered, the server 10 may request the client 20 to obtain information related to the user's bank account, and the client 20 may obtain the information related to the bank account from the user by presenting this request to the user.

[0097] Alternatively, payments may be made using any electronic currency, or may be made using virtual currency using a blockchain.

[0098] Information relating to IDs such as credit cards, bank accounts, or electronic currencies from billing destinations may be registered in the server 10 at the user's discretion (by opting in or out). In this case, from the next payment opportunity, prompt payment can be realized using a method linked to the user.

[0099] As another non-limiting example, when funds or equivalent information are transferred to the biller after settlement from the billing destination, the information processing system 1 can store the user's funds in its own account and present an amount indicating the transfer amount in the user's wallet. In other words, the information processing system 1 may virtually set up a user's account.

[0100] A user can withdraw the amount registered in the wallet to their own bank account, etc., at any time. As another example, a user can use the amount registered in the wallet to settle another invoice to which the user is designated as the billing recipient. A user can also charge the wallet at any time. As another example, a user may manually or automatically deposit a missing amount into the wallet from a bank account, credit card, etc. designated by the user.

[0101] That is, when a bill is received, the client 20 presents the user with the option of making a settlement from the wallet, and can make a settlement based on the wallet balance at the user's request. At this time, the client 20 may be able to select whether to make the entire bill amount from the wallet, or to make a portion of the bill amount from the wallet.

[0102] <Regarding the submission of written claims>

[0103] The information processing system 1 can present documents and information that are appropriately stored and managed through the above processing to the user or the user's agent (a qualified tax accountant, certified public accountant, etc.) at any time.

[0104] By using this system, users can store and check data related to electronic transactions. The information processing system 1 may also have functions as an analysis tool, an accounting tool, and a tax tool.

[0105] The information processing system 1 can, for example, analyze a claim and present various statistics upon request from a user.

[0106] For example, the information processing system 1 can calculate legally required accounting information for a claim upon request from a user and present it to the user.

[0107] For example, the information processing system 1 can execute tax processing for a claim in response to a request from a user and present the calculated results to the user.

[0108] If necessary, the information processing system 1 can issue a receipt to both or one of the users. This receipt can also be sent automatically after the payment is completed. For example, the information processing system 1 can provide a receipt to the user via the billing client 20. In addition, the information processing system 1 can provide a copy of the receipt to the user via the billing client 20.

[0109] <Modification>

[0110] The information processing system 1 can also accept requests based on purchase orders, etc., rather than on billing requests. A user may initiate billing and / or contract processing based on purchase orders, etc., to the information processing system 1 via the client 20.

[0111] In S100, the client 20 can execute an order request from the ordering party, rather than a bill from the billing party, to the server 10. After that, the flow of the contract conclusion is the same.

[0112] The server 10 can realize the above-mentioned processing based on requests and / or processing related to the ordering source and / or the ordering recipient via the client 20. In this case, the user can decide whether to settle the transaction. For example, if an advance payment fee is included at the time of ordering, an invoice for the advance payment fee can be issued and processing between both parties can be carried out according to the contract.

[0113] Furthermore, upon request from one or both users, the information processing system 1 can also execute a prepayment process. This prepayment process can be implemented in any process of the information processing system 1 initiated by a purchase order or an invoice.

[0114] As described above, the information processing system 1 can also start processing related to billing and / or settlement by accepting a purchase order instead of an invoice. For example, if a user wants to perform simple processing, a simpler system can be provided that can perform everything from ordering to billing and management by executing processing that starts from this purchase order.

[0115] As described above, according to the present disclosure, it is possible to realize an information processing system 1 that executes processes such as issuing contracts, issuing invoices (including qualified invoices), issuing receipts, customer management, product management, analysis and reporting, document management and presentation, settlement, and wallet functions. By using this information processing system 1, customers can centrally manage the necessary information related to electronic settlement, and settlement companies can use a system that automatically handles various functions and that realizes easy-to-understand settlement for BtoB as well as BtoC.

[0116] The present disclosure may also be implemented in the following forms.

[0117] (1) processing circuitry; The processing circuitry Identifying the billing recipient based on a billing request from the billing source; The billing source presents a bill to the billing destination, including necessary details, When a request for sending the generated invoice is received from the invoice source, the invoice is sent to the invoice destination or a notice is given that the invoice has been issued; storing the invoice in a database; Information processing device.

[0118] (2) The necessary items are at least: The invoice registration number of the requester; Information indicating the date of the transaction; Transaction items, Transaction amount, and Consumption tax amount, The information processing device according to (1),

[0119] (3) The processing circuitry Referencing information on a contract concluded between the billing source and the billing recipient from a database, or referencing information on a contract transmitted from the billing source together with the billing request; An information processing device according to (1) or (2).

[0120] (4) The processing circuitry If there is no information related to the contract, notify the requester that the contract has not been concluded; (3) An information processing device according to the present invention.

[0121] (5) The processing circuitry If a contract relating to the claim has not been concluded, notify the claimant that no contract has been concluded; (3) An information processing device according to the present invention.

[0122] (6) The processing circuitry If no contract has been concluded, the conclusion of the contract relating to said invoice is effected electronically; (3) An information processing device according to the present invention.

[0123] (7) The processing circuitry When the payment for the invoice is completed, the payment is linked to the invoice and stored in a database. An information processing device according to any one of (1) to (6).

[0124] (8) The processing circuitry providing the user with information relating to at least one of the invoice for which settlement has been completed, the contract relating to the invoice, or the receipt relating to the invoice; (7) An information processing device according to (7).

[0125] (9) processing circuitry; The processing circuitry Identify the supplier based on the request from the client, The ordering party presents an invoice to the ordering party, containing necessary information; When a request for sending the generated invoice is received from the ordering party, the invoice is sent to the ordering party or a notice is given that the invoice has been issued; storing the invoice in a database; Information processing device.

[0126] (10) The processing circuitry Providing wallet functionality for making payments; An information processing device according to any one of (1) to (9).

[0127] (11) The information processing device according to any one of (1) to (10), which is a server.

[0128] (12) The processing circuit Identify the billing recipient based on the billing source's request; The billing source presents a bill to the billing destination, including necessary details, When a request for sending the generated invoice is received from the invoice source, the invoice is sent to the invoice destination or a notice is given that the invoice has been issued; storing the invoice in a database; Information processing methods.

[0129] (13) The processing circuit Identify the supplier based on the request from the client, The ordering party presents an invoice to the ordering party, containing necessary information; When a request for sending the generated invoice is received from the ordering party, the invoice is sent to the ordering party or a notice is given that the invoice has been issued; storing the invoice in a database; Information processing methods.

[0130] (14) A processing circuit is caused to execute the information processing method according to any one of (1) to (11). program.

[0131] (15) A client and a server, The client: A billing request including at least a billing destination is sent from the billing source to the server; The server: The billing source sends an invoice to the billing destination via the client, the invoice including necessary details; When a request for sending the generated invoice is received from the billing source via the client, the billing destination is sent the invoice via the client, or a notice is given that the invoice has been issued; storing the invoice in a database; Information processing system.

[0132] (16) In the information processing system according to (15), causing the client to perform an action on the client; program.

[0133] (17) In the information processing system according to (15), causing the server to perform an action on the server; program.

[0134] In the above, the program may be recorded on a non-transitory computer-readable medium, and the program may be distributed by the computer-readable medium or via a network.

[0135] The aspects of the present disclosure are not limited to the above-described embodiments and include various conceivable modifications, and the effects of the present disclosure are not limited to the above-described contents. The components in each embodiment may be appropriately combined and applied. In other words, various additions, modifications, and partial deletions are possible within the scope of the conceptual idea and intent of the present disclosure, which is derived from the content defined in the claims and their equivalents. [Explanation of symbols]

[0136] 1: Information processing system, 10: Server, 20: Client

Claims

1. processing circuitry; The processing circuitry Identifying the billing recipient based on a billing request from the billing source; The billing source presents a bill to the billing destination, including necessary details, When a request for sending the generated invoice is received from the invoice source, the invoice is sent to the invoice destination or a notice is given that the invoice has been issued; storing the invoice in a database; Information processing device.

2. The necessary items are at least: The invoice registration number of the requester; Information indicating the date of the transaction; Transaction items, Transaction amount, and Consumption tax amount, The information processing device according to claim 1 ,

3. The processing circuitry Referencing information on a contract concluded between the billing source and the billing recipient from a database, or referencing information on a contract transmitted from the billing source together with the billing request; The information processing device according to claim 1.

4. The processing circuitry If there is no information related to the contract, notify the requester that the contract has not been concluded; The information processing device according to claim 3.

5. The processing circuitry If a contract relating to the claim has not been concluded, notify the claimant that no contract has been concluded; The information processing device according to claim 3.

6. The processing circuitry If no contract has been concluded, the conclusion of the contract relating to said invoice is effected electronically; The information processing device according to claim 3.

7. The processing circuitry When the payment for the invoice is completed, the payment is linked to the invoice and stored in a database. The information processing device according to claim 1.

8. The processing circuitry providing the user with information relating to at least one of the invoice for which settlement has been completed, the contract relating to the invoice, or the receipt relating to the invoice; The information processing device according to claim 7.

9. processing circuitry; The processing circuitry Identify the supplier based on the request from the client, The ordering party presents an invoice to the ordering party, containing necessary information; When a request for sending the generated invoice is received from the ordering party, the invoice is sent to the ordering party or a notice is given that the invoice has been issued; storing the invoice in a database; Information processing device.

10. The processing circuitry Providing wallet functionality for making payments; 10. The information processing device according to claim 1.

11. 10. The information processing device according to claim 1, which is a server.

12. The processing circuit Identify the billing recipient based on the billing source's request; The billing source presents a bill to the billing destination, including necessary details, When a request for sending the generated invoice is received from the invoice source, the invoice is sent to the invoice destination or a notice is given that the invoice has been issued; storing the invoice in a database; Information processing methods.

13. A client and a server, The client: A billing request including at least a billing destination is sent from the billing source to the server; The server: The billing source sends an invoice to the billing destination via the client, the invoice including necessary details; When a request for sending the generated invoice is received from the billing source via the client, the billing destination is sent the invoice via the client, or a notice is given that the invoice has been issued; storing the invoice in a database; Information processing system.

14. 14. The information processing system according to claim 13, causing the client to perform an action on the client; program.

15. 14. The information processing system according to claim 13, causing the server to perform an action on the server; program.

Images