Electronic document exchange support method, support device and computer program

Abstract

To provide an electronic document exchange support method for simplifying exchange of electronic documents about a transaction, a support device, and a computer program.SOLUTION: An electronic document exchange support method makes a computer receive exchange data for exchanging an electronic document from a client device of a user being a transmission source of the exchange data, convert the received exchange data into an electronic document in a format compliant with Peppol, establish communication with a Peppol access point of a transmission destination of the electronic document, transmit the converted electronic document to the transmission destination by a Peppol network, and stores the exchange data in a storage part when the transmission is successful.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to an electronic document exchange support method, an electronic document exchange support device, and a computer program for simplifying the exchange of electronic documents relating to a transaction. [Background technology]

[0002] When using the Peppol (Pan European Public Procurement Online, non-patent document 1) network, which is the standard specification for electronic documents such as digital invoices and purchase orders in transactions, an access point that complies with Peppol is required (non-patent documents 1 and 2). In addition, the exchange of electronic documents on the Peppol network requires processing via a certified Peppol service provider, and accounting management systems and accounting management software that incorporate a linking option with Peppol service providers have been proposed. [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] “About OpenPeppol”, OpenPeppol, [online], 2008, [Retrieved August 9, 2023], Internet<URL:https: / / peppol.org / about / > [Non-Patent Document 2] “JP PINT”, Digital Agency, [online], January 14, 2022, [Retrieved August 9, 2023], Internet<URL: https: / / www.digital.go.jp / policies / electronic_invoice> Summary of the Invention [Problem to be solved by the invention]

[0004] However, not all companies and individuals have purchased the above-mentioned accounting management systems or accounting management software, and these companies and individuals would incur significant costs if they were to newly introduce the above-mentioned accounting management systems, etc., in order to send and receive electronic documents via the Peppol network. Therefore, there is a need for a system that is independent of accounting management systems or accounting management software and that easily realizes the sending and receiving of electronic documents via the Peppol network.

[0005] The present disclosure aims to provide an electronic document exchange support method, an assistance device, and a computer program that simplify the exchange of electronic documents related to a transaction. [Means for solving the problem]

[0006] (1) In one embodiment of the electronic document exchange support method disclosed herein, a computer receives data for exchanging an electronic document from a client device of a user who is a sender of the data, converts the received data for exchange into an electronic document in a format that complies with Peppol, establishes communication with a Peppol access point that is a destination of the electronic document, transmits the converted electronic document to the destination via the Peppol network, and, if the transmission is successful, stores the data for exchange in a memory unit.

[0007] In the electronic document exchange support method disclosed herein, even if a user's client device is not compatible with the Peppol network, the user can send data to be exchanged from the client device to a computer, thereby sending an electronic document compatible with the Peppol network to a destination and obtaining a record of the transmission.

[0008] (2) In the electronic document transfer support method described above in (1), the data to be transferred may be data in the format of a spreadsheet software program.

[0009] The electronic document exchange support method disclosed herein enables the transmission of electronic documents via the Peppol network by uploading data to be exchanged in the form of a spreadsheet software program, which is widely used for accounting management of invoices, etc., to a computer (support device), eliminating the need to install special software, etc.

[0010] (3) In the electronic document transfer support method of (1) or (2) above, the file name of the data to be transferred is created to include an identification code of the destination, and prior to transmitting the converted electronic document to the destination, the computer may determine whether the identification code included in the file name of the received data to be transferred matches an identification code included in the data portion of the data to be transferred, and if it determines that they do not match, output an error.

[0011] In the electronic document transfer support method disclosed herein, an error check is performed on the billing destination. A double check is provided for the file name of the data to be transferred and the items to be included in the data portion of the data to be transferred, improving the function of preventing erroneous transmission.

[0012] (4) In the electronic document exchange support method of (1) or (2) above, the file name of the data to be exchanged is created to include the name of the destination, and prior to transmitting the converted electronic document to the destination, the computer may determine whether the name included in the file name of the received data to be exchanged matches a name corresponding to the destination's identification data in a specified number management system, and if it determines that they do not match, output an error.

[0013] In the electronic document exchange support method disclosed herein, error checks regarding billing destinations can also be performed based on whether or not they are registered in a number management system provided by a country or specific institution, further improving the function of preventing erroneous transmissions.

[0014] (5) In any one of the electronic document exchange support methods (1) to (4) above, if the computer is successful in transmitting the converted electronic document, the computer may compress the data to be exchanged before conversion and store it in the memory unit.

[0015] In the electronic document exchange support method disclosed herein, preservation in accordance with the Electronic Bookkeeping Act is automatically performed, making it possible to reduce the management burden on the user.

[0016] (6) In any one of the electronic document exchange support methods (1) to (5) above, the computer establishes communication with a Peppol access point that is the sender of the electronic document, and when it receives an electronic document that complies with Peppol via the Peppol network, it converts the document into data for exchange and stores it in the memory unit, and transmits the data for exchange stored in the memory unit to a client device to which the electronic document is to be sent.

[0017] In the electronic document exchange support method disclosed herein, it is possible to receive electronic documents even if the client device is not compatible with the Peppol network. The received electronic document is in the same format as the data used for sending, and the user can handle it in the same way when sending and receiving.

[0018] (7) An embodiment of the support device of the present disclosure includes a processing unit that receives data for transmitting and receiving an electronic document from a client device of a user who is the sender of the data for transmission, converts the received data for transmission into an electronic document in a format that complies with Peppol, establishes communication with a Peppol access point to which the electronic document is to be sent, transmits the converted electronic document to the destination via the Peppol network, and, if the transmission is successful, stores the data for transmission in a memory unit.

[0019] (8) A computer program according to an embodiment of the present disclosure causes a computer to receive data for transmitting and receiving an electronic document from a client device of a user who is a sender of the data, convert the received data for transmission into an electronic document in a format that complies with Peppol, establish communication with a Peppol access point to which the electronic document is to be sent, transmit the converted electronic document to the destination via the Peppol network, and, if the transmission is successful, store the data for transmission in a memory unit. Effect of the Invention

[0020] According to the present disclosure, electronic documents can be easily exchanged via the Peppol network. [Brief description of the drawings]

[0021] [Figure 1] 1 is a schematic diagram of an electronic document exchange support system according to an embodiment of the present invention; [Diagram 2] FIG. 2 is a block diagram showing a configuration of a client device. [Diagram 3] FIG. 2 is a block diagram showing a configuration of the support device. [Figure 4] FIG. 11 is a diagram showing an example of data to be exchanged; [Diagram 5] 10 is a flowchart illustrating an example of a processing procedure for transmitting an electronic document from a client device. [Figure 6] 10 is a flowchart illustrating an example of a processing procedure for transmitting an electronic document from a client device. [Figure 7] 11 is a flowchart showing an example of a process for transmitting an electronic document by a support device via a Peppol network. [Figure 8] 11 is a flowchart showing an example of a process for transmitting an electronic document by a support device via a Peppol network. [Figure 9] 10 is a flowchart illustrating an example of a procedure for receiving an electronic document. [Figure 10] 10 is a flowchart showing an example of a processing procedure until an electronic document reaches a client device. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0022] The present disclosure will be specifically described with reference to the drawings showing the embodiments thereof.

[0023] FIG. 1 is a schematic diagram of an electronic document transfer support system 100 according to this embodiment. The electronic document transfer support system 100 is a system that supports the transfer of electronic documents (e.g., electronic invoices) via a Peppol network NP. The electronic document transfer support system 100 includes a client device 1 used by a user, a support device 2, a network N, and a Peppol network NP. The client device 1 is a personal computer (PC) used by the user. The support device 2 is a Web server that accepts logins from the client device 1 and provides authenticated users with a Web service that enables the transfer of electronic documents via the Peppol network NP.

[0024] The network N is what is known as the Internet. Client devices 1 used by multiple users can communicate with the support device 2 via the network N. The Peppol network NP is a medium for communication on the network N using the IP-based Peppol protocol. The support device 2 can communicate with other Peppol access points (APs in FIG. 1) via the Peppol network NP and send and receive electronic documents.

[0025] In the electronic document transfer support system 100, a user uses a client device 1 to upload (send) transfer data, in which data to be included in an electronic document is described in a predetermined format, to a Web service provided by a support device 2. This allows the user to send an electronic document to a trading partner in accordance with the Peppol network NP, even if the client device 1 does not have a communication function based on the protocol of the Peppol network NP. In the same way, the user can download an electronic document received from a trading partner via the Peppol network NP from the Web service provided by the support device 2 in the form of transfer data, even if the client device 1 is not connected to the Peppol network NP.

[0026] The support device 2 is implemented as a so-called cloud server consisting of one server computer or multiple server computers connected to each other for communication. The support device 2 performs a Web server function via the network N and also functions as an access point of the Peppol network NP.

[0027] By being issued an account for the electronic document exchange support system 100, a user can easily exchange Peppol-compatible electronic documents via Web services even if the client device 1 used by the user is in a state in which communication via the Peppol network NP is not possible.

[0028] The configuration and processing procedures of each device that realizes the transmission and reception of electronic documents using the electronic document transmission support system 100 will be described below.

[0029] 2 is a block diagram showing the configuration of the client device 1. The client device 1 is a laptop or desktop personal computer capable of communicating via a network N. The client device 1 may be a smartphone or a tablet terminal. The client device 1 includes a processing unit 10, a storage unit 11, a communication unit 12, a display unit 13, and an operation unit 14.

[0030] The processing unit 10 is a processor using a CPU (Central Processing Unit) and / or a GPU (Graphics Processing Unit). The processing unit 10 executes processing corresponding to a Web service provided by the support device 2 using a Web browser program stored in the storage unit 11.

[0031] The storage unit 11 uses a non-volatile memory such as a hard disk, a flash memory, or an SSD (Solid State Drive). The storage unit 11 stores data referenced by the processing unit 10. The storage unit 11 stores various programs including a Web browser program and a spreadsheet software program. The storage unit 11 may store an electronic certificate for logging in to a Web application program provided by the support device 2.

[0032] The communication unit 12 realizes communication with the support device 2 via the network N. The communication unit 12 is, for example, a network card. The communication unit 12 may be a wireless communication device for carrier communication. The processing unit 10 can transmit and receive data to and from the support device 2 via the communication unit 12.

[0033] The display unit 13 is a display such as a liquid crystal display, an organic EL (Electro Luminescence) display, etc. The display unit 13 displays a GUI (Graphical User Interface) of a Web application program presented from the support device 2 based on a Web browser program. The processing unit 10 displays a screen on the display unit 13 based on data provided from the support device 2.

[0034] The operation unit 14 is a user interface such as a keyboard and a mouse capable of inputting and outputting data to and from the processing unit 10. The operation unit 14 may be a touch panel built into the display unit 13. The operation unit 14 may be a physical button, or the operation unit 14 may be an audio input / output unit including a microphone.

[0035] 3 is a block diagram showing the configuration of the support device 2. In this embodiment, the support device 2 is described as being one server computer, but it may be configured with multiple server computers that can communicate with each other, and the processing may be distributed. The support device 2 includes a processing unit 20, a storage unit 21, and a communication unit 22.

[0036] The processing unit 20 is a processor using a CPU or a GPU. The processing unit 20 uses built-in memories such as ROM and RAM to control each component and execute processing. The processing unit 20 executes communication and information processing based on an assistance program P2 (an application program that supports the transmission and reception of electronic documents) stored in the storage unit 21. The assistance program P2 includes a Web server program and Web setting data, and the processing unit 20 functions as a Web server that provides Web applications to the client device 1.

[0037] The storage unit 21 uses a non-volatile memory such as a hard disk, a flash memory, or an SSD. The storage unit 21 stores an assistance program P2 that is read by the processing unit 20. The assistance program P2 may be an assistance program P9 stored in a non-temporary storage medium 9 outside the device that is read and copied by the processing unit 20. The assistance program P9 may be a program that is distributed by a program distribution server device, which the processing unit 20 acquires via the communication unit 22 and stores in the storage unit 21.

[0038] A storage system 210, which is a large-capacity storage medium, is connected to the memory unit 21. The storage system 210 includes storage media connected to each other via a network N. The storage system 210 may be a database constructed in the memory unit 21. The storage system 210 may be a storage medium that uses a blockchain. The memory unit 21 can store in the storage system 210 electronic document data uploaded from the client device 1 and electronic document data downloadable from the client device 1 in association with a user ID.

[0039] User account data (user ID and authentication data) issued to each user is stored in the storage system 210. Data such as an address may also be stored in association with the user ID.

[0040] The communication unit 22 is a communication device that realizes communication based on IP. Specifically, the communication unit 22 is a network card compatible with the network N. The processing unit 20 can transmit and receive data with the client device 1 through Web communication via the communication unit 22. The processing unit 20 can also establish a communication connection based on the Peppol protocol with another Peppol access point AP through the communication unit 22, and transmit and receive data related to electronic documents in the Peppol network NP.

[0041] In the electronic document transfer support system 100 thus configured, a processing procedure in which the client device 1 transfers an electronic document to a business partner will be described below.

[0042] In order to transmit an electronic document (e.g., an electronic invoice) to a business partner via the support device 2 using the client device 1, the user creates data to be exchanged in a predetermined format required by a Web application program provided by the support device 2. The predetermined format is, for example, the format of a spreadsheet software program (e.g., Microsoft Excel (registered trademark)) that can be used as a standard format using the client device 1. The user inputs data to create data to be exchanged based on a template of data to be exchanged in a spreadsheet software program format provided by the support device 2. This allows the user to create data to be exchanged in a spreadsheet software program format that is widely used to create electronic documents, and does not require the installation of special software such as accounting management software. In addition, since data to be exchanged can be created in a spreadsheet software program format that the user is familiar with, the user's work efficiency can be improved. The predetermined format is not limited to a spreadsheet software program format, and may be a Web page format.

[0043] Data for transferring (sending and receiving) electronic documents such as electronic invoices is created according to several rules for processing, which will be described later. FIG. 4 is a diagram showing an example of data for transferring. The data for transferring is, for example, data in a table format corresponding to a spreadsheet software program, as shown in the upper part of FIG. 4. The data for transferring includes, as shown in the upper part of FIG. 4, an invoice number, a start date of a billing period, an end date of a billing period, a registration number of the biller, a name and address of the biller, and the like. Although not shown in the figure, the data for transferring includes an identification code of the billee, a name and address of the biller, and the like. The registration number is, for example, a qualified invoice issuing business number given to a business registered as a qualified invoice issuing business. The identification code is, for example, a corporate number designated in advance by the National Tax Agency. The identification code may be a qualified invoice issuing business number.

[0044] The data to be received contains, for each invoice, a number of lines of data corresponding to the number of items on the invoice, with each line containing the same invoice number. In the example shown in Figure 4, one invoice contains five items, so the data to be received contains five lines of data. If, for example, one invoice contains 15 items, the data to be received contains 15 lines of data. The lines for each item contain the product name, quantity, unit price, subtotal, classification code, and tax rate to be applied. The data to be received contains detailed amount information, including the invoice tax amount, total amount, and breakdown.

[0045] The data to be received includes data with an auto-fill script for creating the tabular data shown in the upper part of Fig. 4, as shown in the lower part. The data with the auto-fill script is written in a spreadsheet software format. When the user enters data into the input cells for each item, the auto-fill script creates the data to be received so that it is reflected in the tabular data shown in the upper part of Fig. 4. The auto-fill script is set to automatically calculate the tax base amount and consumption tax amount according to the tax classification set for the unit price, quantity, and tax-excluded subtotal of each entered item.

[0046] The data to be transferred in the format shown in FIG. 4 can be created by a simple operation in which the user opens the template data (file) based on a spreadsheet software program, inputs the items according to the auto-fill script and guide messages included in the template, and renames and saves the file. The file name of the data to be transferred is created by the user so that it includes the Peppol-ID that has been designated in advance for the destination in relation to the use of Peppol, and the name of the destination. The Peppol-ID includes the destination's identification code (here, the corporation number). As mentioned above, the Peppol-ID may include the qualified biller issuer number as the identification code, instead of the corporation number. It is preferable that an identifier indicating whether the corporation number or the qualified invoice issuer number is included is included in the Peppol-ID, and the corporation number or the qualified invoice issuer number included in the Peppol-ID is identified based on the identifier.

[0047] Using the client device 1, the user logs in to a Web application program provided by processing based on the assistance program P2 of the assistance device 2, and uploads the data to be exchanged that has been created in accordance with the rules in this manner.

[0048] 5 and 6 are flowcharts showing an example of a processing procedure when an electronic document is transmitted from the client device 1. The processing in Fig. 5 and Fig. 6 is executed by the client device 1 (the client device 1 that is the billing source) when issuing an electronic invoice, for example. The processing unit 10 of the client device 1 establishes a Web communication connection with the support device 2 via the network N by the communication unit 12 (step S101). The processing unit 10 requests the support device 2 to transmit a login page to a Web application program of the support device 2 (step S102).

[0049] The processing unit 20 of the support device 2 receives a request to transmit a login page (step S201), and transmits login page data to the client device 1 in response to the request (step S202). In steps S201-S202, the processing unit 20 may perform control so as to transmit the login page to the client device 1 on the condition that authentication based on the electronic certificate transmitted from the client device 1 is successful.

[0050] The processing unit 10 of the client device 1 receives the data of the login page (step S103), displays the login page on the display unit 13 (step S104), and accepts input of login data (e.g., a login ID and a password) by the user (step S105). The processing unit 10 transmits the login data input by the user to the support device 2 via the login page (step S106).

[0051] The processing unit 20 of the support device 2 receives the login data (step S203), and when login authentication based on the received login data is successful, transmits data of the upload screen to the client device 1 (step S204).

[0052] The processing unit 10 of the client device 1 receives the data of the upload screen (step S107), displays the upload screen on the display unit 13 (step S108), and accepts the designation of the data to be transferred (step S109). For example, the user selects the desired data to be transferred and performs a drag operation, and then performs a drop operation on the upload screen to designate the data to be transferred. Alternatively, a list of data stored in the client device 1 may be displayed, and the data to be transferred may be designated by selecting the data to be transferred from the data list. The processing unit 10 transmits the designated data to be transferred to the support device 2 (step S110 (FIG. 6)).

[0053] When the processing unit 20 of the support device 2 receives the data to be uploaded (converted) from the client device 1 (step S205), it stores the data in the storage system 210 (step S206) and executes a process of transmitting the electronic document via the Peppol network NP (step S207). The transmission process of step S207 will be described later.

[0054] The processing unit 20 of the support device 2 judges whether the result of the transmission process in step S207 is a success or not (step S208). If it is judged that the transmission is a success (S208: YES), the processing unit 20 stores a file indicating the transmission result in step S207 in the storage system 210 (step S209), and transmits a result screen of the transmission process (here, a result screen indicating that the transmission process is successful) to the client device 1 (step S210).

[0055] The processing unit 10 of the client device 1 receives the result screen of successful transmission (step S111), displays a screen indicating that the file of the transmission result has been stored in the storage system 210 as a transmission result screen (step S112), and ends the process.

[0056] If it is determined in step S208 that the transmission has failed (S208: NO), the processing unit 20 transmits a screen for re-uploading (re-upload screen) including the error content of the transmission failure to the client device 1 as a result screen of the transmission process (step S211).

[0057] The processing unit 10 of the client device 1 receives the re-upload screen (step S113), displays the re-upload screen as a transmission result screen on the display unit 13 (step S114), and returns the process to step S109. In this case, the user checks the error content and corrects the data to be exchanged as appropriate, and then specifies the corrected data to be exchanged as the data to be uploaded (step S109). Then, the above process from step S109 onwards is executed again.

[0058] 7 and 8 are flowcharts showing an example of a process for transmitting an electronic document via the Peppol network NP by the support device 2. The process shown in the flowcharts of Fig. 7 and 8 corresponds to details of step S207 of the process shown in Fig. 5 and Fig. 6.

[0059] The processing unit 20 acquires data to be transmitted that has been uploaded by a user from the storage system 210 (step S701). The processing unit 20 acquires the file name of the acquired data to be transmitted (step S702).

[0060] The processing unit 20 extracts the identification code (here, the corporate number corresponding to the destination) and the name of the destination included in the acquired file name (step S703). Specifically, the processing unit 20 extracts a predetermined number of digits included in the file name as the identification code, and extracts the character string input immediately after the identification code as the name of the destination.

[0061] The processing unit 20 provides the corporate number included in the identification code extracted in step S703 to a national reference service (number management system), obtains the name of the registered corporation corresponding to the corporate number, and judges whether the name obtained in step S703 (the name included in the file name) matches the name corresponding to the identification code in the number management system (step S704). If it is judged in step S704 that they do not match (S704: NO), the processing unit 20 notifies the client device 1 of an error result indicating "not registered" (step S705). The processing unit 20 ends the transmission process, and returns the process to the flowcharts of Figs. 5 and 6, proceeding to step S208. In this way, it is judged whether the name included in the file name matches the name specified based on the identification code. This makes it possible to prevent erroneous transmission of electronic documents such as electronic invoices.

[0062] If it is determined in step S704 that there is a match (S704: YES), the processing unit 20 reads out the name of the billing destination corporation or individual written in the data portion of the transfer data acquired in step S701 (step S706).

[0063] The processing unit 20 judges whether the name obtained from the file name in step S704 matches the name read from the data portion in step S706 (step S707). If it is judged in step S707 that the names do not match (S707: NO), the processing unit 20 notifies the client device 1 of an error result such as "unknown billing destination" for the electronic document destination (step S708). The processing unit 20 ends the transmission process, returns the process to the flowcharts of Figs. 5 and 6, and proceeds to step S208. In this way, it is judged whether the name included in the file name matches the name included in the data portion. This makes it possible to prevent erroneous transmission of electronic documents such as electronic invoices, and to check for errors in the destination, etc. more accurately. Note that here, two types of comparison processes are performed: a comparison process between the name included in the file name and the name specified based on the identification code, and a comparison process between the name included in the file name and the name included in the data portion, but this is not limited to this. Only one of the two types of comparison processes may be performed.

[0064] If it is determined that the names match (step S707: YES), the processing unit 20 performs a validation check of the data to be exchanged (step S709). The processing unit 20 determines whether or not there is a problem as a result of the validation check (step S710).

[0065] If it is determined in step S710 that there is a problem with the validation check (S710: YES), the processing unit 20 notifies the client device 1 of the error result of "validation error" (step S711). The processing unit 20 ends the transmission process, and returns the process to the flowcharts of Fig. 5 and Fig. 6, proceeding to step S208.

[0066] If it is determined in step S710 that there is no problem (S710: NO), the processing unit 20 converts the spreadsheet software format data acquired in step S701 to an electronic document in Peppol format (format conforming to Peppol) (step S712). The processing unit 20 performs a schema check on the converted electronic document in Peppol format (step S713). The processing unit 20 determines whether there is a problem as a result of the schema check (step S714), and if it is determined that there is a problem (S714: YES), notifies the client device 1 of the error including the error result of "schema error" (step S715). The processing unit 20 ends the transmission process, and returns the process to the flowcharts of Figs. 5 and 6 and proceeds to step S208.

[0067] If the processing unit 20 determines that there is no problem as a result of the schema check (S714: NO), it establishes communication with a Peppol access point to transmit the electronic document to the billing destination company or individual via the Peppol network NP (step S716).The processing unit 20 transmits the electronic document after conversion in step S711 to the Peppol access point of the communication partner (step S717).

[0068] The processor 20 judges whether there was a problem in the transmission in step S717 (step S718), and if it is judged that there was a problem (S718: YES), notifies the error result of "Peppol communication error" (step S719). The processor 20 ends the transmission process, and returns the process to the flowcharts of Figures 5 and 6, and proceeds to step S208.

[0069] When the processing unit 20 determines that there was no problem with the transmission in step S717 (S718: NO), it compresses the data to be exchanged acquired in step S701 before conversion and stores it in the storage system 210 (step S720). The processing unit 20 attaches the data of the electronic document transmitted in step S717 to a screen indicating the result of successful transmission, transmits it to the client device 1 (step S721), ends the transmission process, and returns the process to the flowcharts of Figures 5 and 6 and proceeds to step S208.

[0070] In this way, a user can realize the transmission of an electronic document via the Peppol network NP by simply creating data for transmission in a format for a standard (in other words, familiar) spreadsheet software program and uploading it to the electronic document transmission support system 100. That is, even if a special accounting management software or accounting management system incorporating a linkage option with a Peppol service provider is not used (introduced), an electronic document in a format conforming to Peppol can be transmitted to a recipient through a simple procedure. Furthermore, for a user who only needs to realize the transmission and reception of electronic documents via the Peppol network NP, there is no need to introduce a relatively expensive accounting management system incorporating a linkage option with a Peppol service provider, and it is possible to realize compatibility with Peppol at a relatively low cost.

[0071] The above describes the operation of the client device 1 when it acts as the sender of an electronic document and transmits the electronic document to a recipient. Next, the operation of the client device 1 when it acts as the recipient of the electronic document and receives an electronic document from a recipient (when it receives an electronic invoice from a biller) will be described. The electronic document exchange support system 100 allows a user to use the client device 1 to obtain the contents of an electronic document from a business partner via the support device 2. As described above, in the Peppol network NP, an electronic document is exchanged with a communication connection established between the sender (biller) and receiver (biller).

[0072] 9 is a flow chart showing an example of a procedure for receiving an electronic document. In the electronic document exchange support system 100, the support device 2 establishes communication with a Peppol access point for receiving an electronic document from a sender (a billing source of an electronic invoice) via the Peppol network NP (step S221). The processing unit 20 of the support device 2 receives the electronic document in Peppol format (format compliant with Peppol) via the Peppol network NP (step S222).

[0073] The processing unit 20 executes a schema check of the electronic document in Peppol format acquired in step S222 (step S223). The processing unit 20 judges whether or not there is a problem as a result of the schema check (step S224), and if it judges that there is a problem (S224: YES), stores an error result indicating a "schema error" (step S225).

[0074] If it is determined that there is no problem (S224: NO), the processing unit 20 reads out the registration number of the biller described in the electronic document acquired in step S222 (step S226). The processing unit 20 provides the read-out registration number to a national management reference service and determines whether the registration number is valid as a number of a qualified business (qualified bill issuing business number) (step S227).

[0075] If it is determined that the read registration number is valid as the number of a qualified business (S227: YES), the electronic document received in step S222 is converted into the format of data to be transmitted or received, that is, into the format of a spreadsheet software (step S228).

[0076] If it is determined in step S227 that the registered number is not valid as a number of a qualified business (S227: NO), the processing unit 20 adds a warning message (step S229) and then proceeds to step S228.

[0077] The processing unit 20 creates a download screen including a download link for the converted data to be exchanged (step S230). The processing unit 20 stores the converted data to be exchanged in the storage system 210 (step S231), disconnects the Peppol network NP (step S232), and ends the process. The support device 2 waits for the electronic document (electronic invoice) to be received from the client device 1, which is the invoice destination.

[0078] 10 is a flowchart showing an example of a processing procedure until an electronic document reaches the client device 1. When a user, thinking that an invoice addressed to him / her (his / her company) may have arrived, performs an operation to access a Web application program using a Web browser program, the following processing is executed.

[0079] The processing unit 10 of the client device 1 establishes a Web communication connection with the support device 2 via the network N by the communication unit 12 (step S121). The processing unit 10 requests the support device 2 for a login page to a Web application program of the support device 2 (step S122).

[0080] The processing unit 20 of the support device 2 receives the request for the login page (step S241), and transmits the login page data to the client device 1 in response to the request (step S242). In steps S241-S242, the processing unit 20 may perform control so that the login page is transmitted only when authentication based on the electronic certificate transmitted from the client device 1 is successful.

[0081] The processing unit 10 of the client device 1 receives the data of the login page (step S123), displays the login page on the display unit 13 (step S124), and accepts input of login data by the user (step S125). The processing unit 10 transmits the input login data to the support device 2 via the login page (step S126).

[0082] The processing unit 20 of the support device 2 receives the login data (step S243), and if the login authentication based on the received login data is successful, searches for data to be transmitted and received addressed to the target user in the storage system 210 (step S244). According to the flowchart of Fig. 9, when the support device 2 receives an electronic document via the Peppol network NP, the electronic document is converted into data to be transmitted and received and stored in the storage system 210 (steps S231, S232 (Fig. 9)).

[0083] If the search results in the existence of data to be exchanged addressed to the logged-in user, the processing unit 20 acquires data for a download screen for the searched data to be exchanged from the storage system 210 (step S245). The processing unit 20 transmits data for the download screen and a reference screen that allows the user to refer to the reception result as an electronic document to the client device 1 (step S246).

[0084] In step S244, if the search result indicates that there is no data to be exchanged addressed to the logged-in user, the processing unit 20 may transmit to the client device 1 data of a screen indicating that there is no electronic document addressed to the logged-in user.

[0085] When the processing unit 10 of the client device 1 receives the screen data transmitted from the support device 2 (step S127), it displays the screen on the display unit 13 (step S128), and ends the process.

[0086] In step S128, when data of a download screen for data to be exchanged is received, the processing unit 10 displays the download screen. The download screen includes link information to data to be exchanged of electronic documents, i.e., data in a spreadsheet format. When data of a reference screen for the reception result as an electronic document is received, a screen on which the contents of the preserved electronic document (invoice) can be referenced is displayed. Then, when the download button is pressed on the download screen, the processing unit 20 of the support device 2 transmits the data to be exchanged (data in a spreadsheet format) stored in the storage system 210 to the client device 1 in response to a download request (transmission request) from the client device 1.

[0087] In step S128, when data of a screen indicating that no electronic document addressed to the logged-in user exists is received, the processing section 10 displays a screen indicating that no electronic document exists.

[0088] In this way, users can exchange electronic documents via the Peppol network NP not only when sending electronic documents such as electronic invoices, but also when receiving them, without using (installing) special accounting management software or accounting management systems that incorporate integration options with Peppol service providers.

[0089] As shown in the flowcharts of Figures 5 to 10, in the support device 2, when sending and receiving an electronic document, the compressed data of the data to be exchanged is stored in the storage system 210, and processing conforming to the Electronic Bookkeeping Act is also executed. Therefore, the user of the client device 1 can confirm the saved data on a screen that can be referenced, and the operation is very simple, and electronic documents can be exchanged via the Peppol network NP.

[0090] The embodiments disclosed above are illustrative in all respects and are not restrictive. The scope of the present invention is defined by the claims, and includes all modifications within the meaning and scope of the claims. [Explanation of symbols]

[0091] 100 Electronic document exchange support system 1. Client device 2 Support equipment 20 Processing section of support device 21 Memory unit of the support device 210 Storage System 22 Communication unit of the support device P2 Support program (computer program)

Claims

1. The computer receiving data for transmitting and receiving an electronic document from a client device of a user who is a sender of the data; Converting the received data to be exchanged into an electronic document in a format conforming to Peppol; Establish communication with a Peppol access point to which the electronic document is to be sent; Transmitting the converted electronic document to the destination via the Peppol network; If the transmission is successful, the data to be transmitted is stored in a storage unit. Electronic document exchange support method.

2. The data to be exchanged is in the form of a spreadsheet software program. The electronic document exchange support method according to claim 1 .

3. The file name of the data to be transmitted is created so as to include the identification code of the destination. The computer includes: prior to transmitting the converted electronic document to the destination, determining whether an identification code included in a file name of the received data to be exchanged matches an identification code included in a data portion of the data to be exchanged; If it is determined that they do not match, an error is output.

3. The electronic document exchange support method according to claim 1.

4. The file name of the data to be transmitted is created so as to include the name of the destination. The computer includes: Prior to transmitting the converted electronic document to the destination, it is determined whether or not a name included in a file name of the received data to be exchanged matches a name corresponding to identification data of the destination in a predetermined number management system; If it is determined that they do not match, an error is output. The electronic document exchange support method according to claim 3.

5. The computer includes: If the transmission of the converted electronic document is successful, the data to be exchanged before the conversion is compressed and stored in the storage unit.

3. The electronic document exchange support method according to claim 1.

6. The computer includes: Establish communication with the Peppol access point from which the electronic document was sent, When a Peppol-compliant electronic document is received via the Peppol network, the electronic document is converted into the data to be exchanged and stored in the storage unit; The data to be exchanged stored in the storage unit is transmitted to a client device that is a destination of the electronic document.

3. The electronic document exchange support method according to claim 1.

7. receiving data for transmitting and receiving an electronic document from a client device of a user who is a sender of the data; Converting the received data to be exchanged into an electronic document in a format conforming to Peppol; Establish communication with a Peppol access point to which the electronic document is to be sent; Transmitting the converted electronic document to the destination via the Peppol network; If the transmission is successful, the data to be transmitted is stored in a storage unit. A support device that includes a processing unit that executes processing.

8. On the computer, receiving data for transmitting and receiving an electronic document from a client device of a user who is a sender of the data; Converting the received data to be exchanged into an electronic document in a format conforming to Peppol; Establish communication with a Peppol access point to which the electronic document is to be sent; Transmitting the converted electronic document to the destination via the Peppol network; If the transmission is successful, the data to be transmitted is stored in a storage unit. A computer program that executes a process.

Images