WO2023021572A1

WO2023021572A1 - Data processing system, data processing method, and data processing device

Info

Publication number: WO2023021572A1
Application number: PCT/JP2021/029995
Authority: WO
Inventors: 鴻鵬葛; 顕松田; 智小俣; 啓太郎森; 貴亮佐藤; 将和早川
Original assignee: ファーストアカウンティング株式会社
Priority date: 2021-08-17
Filing date: 2021-08-17
Publication date: 2023-02-23
Also published as: JP7072964B1; JPWO2023021572A1; JP2023027746A

Abstract

A data processing system S comprising an account processing device 1 in which a business operator issuing bills is registered, and a data processing device 2 for converting the billing data received from the account processing device 1 into an electronic invoice in prescribed format. The account processing device 1 has a storage unit 12 for account processing that stores business operator authentication information for authenticating the business operator, and a data transmission unit 134 for transmitting billing data that corresponds to the bill created by the business operator to the data processing device 2, on condition that the business operator has been authenticated using the business operator authentication information. The data processing device 2 has a storage unit 22 for account processing that stores device authentication information for authenticating the account processing device 1, a data reception unit 232 for receiving billing data from the account processing device 1, and an invoice creation unit 233 for transmitting, to an electronic invoice network, an electronic invoice having been created by converting the billing data received by the data reception unit 232 into a prescribed format, on condition that it was possible to authenticate the account processing device 1 using the device authentication information.

Description

DATA PROCESSING SYSTEM, DATA PROCESSING METHOD AND DATA PROCESSING APPARATUS

The present invention relates to a data processing system, a data processing method, and a data processing device.

Accounting processing devices that send and receive invoices online are known.

WO2017-73102

In recent years, standardization is underway to exchange electronic documents related to ordering and billing on the network. In Japan as well, it has been announced that PEPPOL (Pan-European Public Procurement Online), which is a new standard specification for electronic invoices, will be complied with. Before issuing a PEPPOL compliant electronic invoice, it is required to verify information (eg, name and address) about the business that issued the invoice.

Since existing accounting processors cannot issue electronic invoices that comply with the new standard specifications, it is necessary to convert the invoice data created by accounting processors into the format of electronic invoices. However, if the data processing device that converts to the format of the electronic invoice does not have the business information of the business that issues the invoice, the data processing device does not have the business information of the business operator that issues the electronic invoice. There was a problem that the information on the issuer could not be confirmed.

Therefore, the present invention has been made in view of these points. It aims to make it possible.

In the data processing system according to the first aspect of the present invention, an accounting processing device in which a business entity issuing an invoice is registered, and invoice data received from the accounting processing device are converted into an electronic invoice in a predetermined format. a data processing device that authenticates the business operator, wherein the accounting processing device comprises an accounting processing storage unit that stores business operator authentication information for authenticating the business operator; and a business operator authentication information using the business operator authentication information. a data transmission unit configured to transmit the invoice data corresponding to the invoice created by the business operator to the data processing device on condition that the data processing device has A data processing storage unit for storing device authentication information for authentication, a data receiving unit for receiving the invoice data from the accounting processing device, and the authentication of the accounting processing device using the device authentication information and an invoice creating unit configured to transmit an electronic invoice created by converting the invoice data received by the data receiving unit into the predetermined format, to an electronic invoice network.

The data processing storage unit stores the IP address of the accounting processing device as the device authentication information. An electronic invoice based on the invoice data may be transmitted on condition that the IP address matches the IP address stored in the data processing storage unit.

The invoice creation unit updates the device authentication information stored in the data processing storage unit within a predetermined period of time starting from the point in time when the data receiving unit receives the invoice data and before that point in time. An electronic invoice based on the invoice data may be transmitted on the condition that it has been received from the accounting processing device.

The data receiving unit receives user identification information, which is information identifying a user of an electronic invoice network through which electronic invoices are sent and received, corresponding to the business operator who issued the invoice corresponding to the invoice data. Acquired from the accounting processing device in association with the invoice data, and the invoice creating unit may create an electronic invoice including the user identification information acquired by the data receiving unit.

The data processing storage unit stores business identification information, which is a number for identifying the business, and user identification information, which is information for identifying a user of an electronic invoice network through which electronic invoices are transmitted and received. The data receiving unit acquires the business identification information of the business that issued the bill corresponding to the bill data from the accounting processing device in association with the bill data, and stores the information in association with the bill data. The voice creation section may create an electronic invoice including the user identification information stored in the data processing storage section in association with the business entity identification information acquired by the data reception section.

The data processing storage unit contains business identification information that identifies the business, and user identification information that identifies a user of an electronic invoice network through which electronic invoices are transmitted and received. , are stored in association with each other, the data receiving unit acquires the business identification information included in the invoice data, and the invoice creation unit stores the business identification information acquired by the data receiving unit. may create an electronic invoice including the user identification information stored in the data processing storage unit in association with.

If the acquired business identification information is not stored in the data processing storage unit, the data reception unit may notify the accounting processing device that the business is an unregistered business.

When the data included in the invoice data does not meet the requirements necessary for creating an electronic invoice, the invoice creation unit notifies the accounting processing device that the invoice data does not meet the requirements. may notify you.

The accounting processing device sends the invoice data by e-mail to the business terminal that transmits the invoice created by the business, or converts the invoice data into an electronic invoice and then sends the electronic invoice. A display processing unit for displaying a screen for selecting whether to transmit via a network, wherein the data transmission unit receives an instruction to convert the invoice data into an electronic invoice from the business terminal. On this condition, the invoice data may be transmitted to the data processing device.

In a data processing method according to a second aspect of the present invention, a computer processes an accounting processing device in which a business entity issuing an invoice is registered, and an electronic invoice in a predetermined format for bill data received from the accounting processing device. A data processing method executed by a data processing device that converts to and a step of authenticating the business operator using the business authentication information stored in the accounting device, on the condition that the business operator has been authenticated, responds to the invoice created by the business operator. transmitting the bill data to the data processing device; receiving the bill data from the accounting device by the data processing device; and storing device authentication information for authenticating the accounting device. a step of authenticating the accounting processing device using the device authentication information stored in the data processing storage unit; and providing the received invoice data in the predetermined format on condition that the accounting processing device has been authenticated. and sending the electronic invoice created by converting to an electronic invoice network.

In a data processing apparatus according to a third aspect of the present invention, a data processing storage unit for storing apparatus authentication information for authenticating an accounting processing apparatus in which a business entity issuing an invoice is registered; and the accounting processing apparatus. a data receiving unit for receiving the bill data corresponding to the bill from the data receiving unit, and the bill data received by the data receiving unit on the condition that the accounting processing device has been authenticated using the device authentication information. and an invoice creation unit that transmits the electronic invoice created by converting it into a predetermined format to an electronic invoice network.

According to the present invention, it is possible to issue an electronic invoice even if the device that creates the electronic invoice does not have information on the business operator that issued the invoice.

1 is a schematic diagram showing the configuration of a data processing system S; FIG. 3 is a diagram schematically showing the flow of data in the data processing system S; FIG. 2 is a block diagram showing the configuration of accounting processing device 1. FIG. FIG. 4 is a diagram showing an example of invoice data; 2 is a block diagram showing the configuration of a data processing device 2; FIG. 4 is a diagram showing an example of the data structure of device authentication information stored in a data processing storage unit 22; FIG. 4 is a diagram showing an example of a data structure of business operator information stored in a data processing storage unit 22; FIG. 4 is a sequence diagram showing the flow of processing in the data processing system S; FIG.

[Overview of data processing system S]
FIG. 1 is a schematic diagram showing the configuration of a data processing system S. As shown in FIG. The data processing system S is a system for online exchange and processing of invoice data between users participating in the electronic invoice network N. FIG. The data processing system S includes an electronic invoice network N, a plurality of accounting processors 1, a data processor 2, a plurality of business operator terminals 3, a plurality of relay devices 4, a plurality of SMPs (Service Metadata Publishers) 5 and SMLs (Service Metadata Locator) 6.

The electronic invoice network N is a network for sending and receiving electronic invoices that comply with PEPPOL specifications. The e-invoicing network N may include other networks such as the Internet or intranets.

The accounting processing device 1 is a device for issuing or receiving invoices, or performing accounting processing such as sorting. The data processing device 2 transmits an electronic invoice based on the invoice data issued by the accounting processing device 1 to the relay device 4 communicably connected to the accounting processing device 1 used by the business operator to which the invoice is addressed. It is a device. The data processing device 2 is communicably connected to one or more accounting processing devices 1 . The operator terminal 3 is a terminal operated by a user. The user operates the business operator terminal 3 to access the accounting processing device 1 . Note that the accounting processing device 1 may receive information necessary for issuing a bill from another accounting processing device 1 .

The relay device 4 is a device that relays the electronic invoice transmitted by the data processing device 2 so that it reaches the accounting processing device 1 used by the business operator to which the electronic invoice is addressed. The relay device 4 may have functions similar to those of the data processing device 2 .

The SMP 5 is a server for providing the data processing device 2 to which the electronic invoice is to be sent with the metadata assigned to the business operator of the destination of the electronic invoice. Metadata is information assigned to users who send and receive electronic invoices in the electronic invoice network N. FIG. The metadata provided by the SMP 5 includes, for example, the IP address of the data processing device 2 or the relay device 4 accessible by the user of the electronic invoice network N, the URL (Universal Resource Locator), the setting information related to security, and the information used by the user. Possible transaction details, etc.

SML6 is a server that has the function of registering the location information of SMP5, which stores the user's metadata, in a DNS (Domain Name System) server. Location information is, for example, an IP address, URL, or the like.

FIG. 2 is a diagram schematically showing the flow of data in the data processing system S. FIG. 2 shows the flow from when the business operator terminal 3 accesses the accounting processing device 1 to when the data processing device 2 transmits an electronic invoice to the invoice network N. As shown in FIG. The business operator terminal 3 transmits the business authentication information to the transaction processing device 1 ((1) in FIG. 2). The business authentication information is information for authenticating the business, for example, a business ID and password that are information assigned to the business to access the accounting processing device 1 .

The accounting processing device 1 verifies the business operator authentication information received from the business operator terminal 3. The transaction processing device 1 compares the pre-registered business operator authentication information with the received business authentication information, and verifies the received business operator authentication information. When determining that the received business operator authentication information is valid, the accounting processing device 1 transmits a response indicating that the authentication is completed to the business operator terminal 3 ((2) in FIG. 2). When the authentication is completed, the business operator terminal 3 transmits the invoice data to the accounting processing device 1 ((3) in FIG. 2).

The accounting processing device 1 transmits device authentication information to the data processing device 2 ((4) in FIG. 2). The data processing device 2 verifies the device authentication information received from the transaction processing device 1 . The device authentication information is information for authenticating the transaction processing device 1, such as an IP address assigned to the transaction processing device 1, a server certificate of the transaction processing device 1, and the like. The data processing device 2 compares the received device authentication information with pre-stored device authentication information to verify the received device authentication information. If the device authentication information is valid, the data processing device 2 transmits a response indicating that the authentication has been completed to the transaction processing device 1 ((5) in FIG. 2). The accounting processing device 1 transmits the invoice data to the data processing device 2 on condition that the authentication is completed ((6) in FIG. 2).

The data processing device 2 acquires user identification information corresponding to the business operator that issued the invoice ((7) in FIG. 2). The user identification information is information for identifying users in the electronic invoice network N, such as PEPPOL Participant Identifiers. The data processing device 2 acquires, for example, user identification information stored in advance in an internal storage medium.

Subsequently, the data processing device 2 creates an electronic invoice by converting the invoice data into a data format that can be transmitted and received via the invoice network N ((8) in FIG. 2). The data processing device 2 creates an electronic invoice containing the acquired user identification information. The data processing device 2 transmits the created electronic invoice to the relay device 4 ((9) in FIG. 2). Note that the authentication of the transaction processing device 1 performed by the data processing device 2 may be performed before the authentication of the business operator terminal 3 performed by the transaction processing device 1 .

By configuring the data processing system S so that the data processing device 2 authenticates the accounting processing device 1 and the accounting processing device 1 authenticates the business operator, the data processing system S as a whole can You can check information about As a result, it is possible to issue an electronic invoice even if the data processing device 2 does not have information on the company that issued the invoice.

[Configuration of accounting processing device 1]
FIG. 3 is a block diagram showing the configuration of the accounting processing device 1. As shown in FIG. The accounting processing device 1 has a communication unit 11 , an accounting processing storage unit 12 and a control unit 13 . The control unit 13 has an authentication unit 131 , a data reception unit 132 , an invoice data creation unit 133 , a data transmission unit 134 and a display processing unit 135 .

The communication unit 11 is a communication interface for communicating with the business terminal 3 and the data processing device 2 via the network. The accounting processing storage unit 12 is, for example, a storage medium such as ROM (Read Only Memory), RAM (Random Access Memory), SSD (Solid State Drive), hard disk, or the like. The accounting processing storage unit 12 stores various programs executed by the control unit 13 .

The accounting processing storage unit 12 stores business operator authentication information for authenticating the business operator. The transaction processing storage unit 12 stores, for example, a business ID and a password in association with each other as business authentication information. The transaction processing storage unit 12 may associate and store the business operator ID and the public key used for authentication.

The control unit 13 is, for example, a CPU (Central Processing Unit). By executing the control program stored in the storage unit 12 for accounting processing, the control unit 13 functions as an authentication unit 131, a data reception unit 132, an invoice data generation unit 133, a data transmission unit 134, and a display processing unit 135. Function.

The authentication unit 131 authenticates the business operator who accesses the accounting processing device 1 using the business operator terminal 3 . The authentication unit 131 verifies the business operator authentication information by comparing the business operator authentication information received from the business operator terminal 3 and the business operator authentication information stored in the accounting processing storage unit 12, thereby verifying the operator authentication information. authenticate legitimacy; The authentication unit 131 may authenticate the business by verifying the access token received as the business authentication information.

The data receiving unit 132 receives data for issuing invoices from the business operator terminal 3. For example, the data receiving unit 132 receives data input to an input screen displayed on the business terminal 3 by the display processing unit 135 . Data for issuing an invoice is data included in invoice data, which will be described later.

The data receiving unit 132 may receive data for issuing an invoice from another accounting device 1. In this case, the data receiving unit 132 receives an access token indicating that it has been authorized by the business operator from the other accounting processing device 1 at a timing prior to receiving the data for issuing the bill. .

The invoice data creation unit 133 creates invoice data based on the data received by the data reception unit 132 . FIG. 4 is a diagram showing an example of invoice data D created by the invoice data creation unit 133. As shown in FIG. The invoice data D includes, for example, a destination business name C1, a destination department name, a destination business identification number C2, a destination telephone number, an issuer business name C3, an issuer business identification number C4, an invoice number, an invoice This includes the date of issuance of the invoice, the name of the product or service subject to the invoice, the amount invoiced, the amount of tax, the bank account number for transfer, etc.

The business identification number C2 is, for example, a registration number assigned to a business registered as an eligible billing business. The invoice data D may be document data, image data, or text data. Note that the invoice data D may include user identification information corresponding to the destination business identification number C2.

Returning to FIG. 3, the data transmission unit 134 transmits bill data corresponding to the bill prepared by the business operator to the data processing device 2 on the condition that the business operator has been authenticated using the business authentication information. . When an unauthenticated user attempts to transmit bill data, the display processing unit 135 displays a screen requesting authentication from the user and prompts the user to enter business authentication information. When the authentication unit 131 authenticates the user based on the business operator authentication information input by the user, the data transmission unit 134 transmits bill data to the data processing device 2 .

The data transmission unit 134 determines whether to transmit the invoice data to the invoice destination via the invoice network N or to attach the invoice data to an e-mail and transmit the invoice data, according to the user's selection. You may Therefore, the display processing unit 135 sends the invoice data by e-mail to the business operator terminal 3 that transmits the invoice created by the business operator, or converts the invoice data into an electronic invoice and then sends the electronic invoice. A screen for selecting whether to transmit via the network may be displayed. The display processing unit 135 displays, for example, buttons labeled "Send by e-mail" and "Send by electronic invoice" on the invoice data input screen. Then, the user operates the business operator terminal 3 and selects a method of transmitting bill data.

The data transmission unit 134 may transmit the invoice data to the data processing device 2 on condition that an instruction to convert the invoice data into an electronic invoice has been received from the business operator terminal 3 . That is, when the button labeled “Send by electronic invoice” is pressed, the data transmission unit 134 transmits the invoice data to the data processing device 2 .

[Configuration of data processor 2]
FIG. 5 is a block diagram showing the configuration of the data processing device 2. As shown in FIG. The data processing device 2 has a communication section 21 , a data processing storage section 22 and a control section 23 . The control unit 23 has an authentication unit 231 , a data reception unit 232 and an invoice creation unit 233 . The communication unit 21 is a communication interface for communicating with the accounting processing device 1, relay device 4, SMP5 and SML6 via the network.

The data processing storage unit 22 is, for example, a storage medium such as a ROM, RAM, SSD, or hard disk. The data processing storage unit 22 stores device authentication information for authenticating the transaction processing device 1 . FIG. 6 is a diagram showing an example of the data structure of device authentication information stored in the data processing storage unit 22. As shown in FIG. The data processing storage unit 22 may store the IP address of the transaction processing device 1 as the device authentication information in association with the device ID, which is information for identifying the transaction processing device 1 .

The data processing storage unit 22 stores business identification information, which is information for identifying businesses, and user identification information, which is information for identifying users of an electronic invoice network through which electronic invoices are transmitted and received. and may be stored in association with each other. FIG. 7 is a diagram showing an example of the data structure of the business operator information stored in the data processing storage unit 22. As shown in FIG. The data processing storage unit 22 stores business identification information, business name, department name, telephone number, and user identification information in association with each other.

The data processing storage unit 22 is not limited to storing one operator identification number in association with one user identification number. good. In the example of FIG. 7, "Yamada Shoji" has user identification information corresponding to each of the management department and the manufacturing department.

Returning to FIG. 5, the control unit 23 is, for example, a CPU. The control unit 23 functions as an authentication unit 231 , a data reception unit 232 and an invoice creation unit 233 by executing control programs stored in the data processing storage unit 22 .

The authentication unit 231 authenticates the accounting processing device 1 that transmits bill data to the data processing device 2 . The authentication unit 231 authenticates the transaction processing device 1 by, for example, verifying a server certificate received as device authentication information from the transaction processing device 1 . Note that the authentication unit 231 may set the valid period so that the authentication is valid only for a predetermined period after the completion of the authentication.

Furthermore, the authentication unit 231 may authenticate the accounting processing device 1 by verifying the IP address of the accounting processing device 1 in addition to or instead of verifying the server certificate. The authentication unit 231 acquires from the communication unit 21 the source IP address included in the packet received by the data reception unit 232 . Also, the authentication unit 231 acquires the IP address corresponding to the transaction processing device 1 stored in the data processing storage unit 22 as device authentication information. The authentication unit 231 verifies whether the source IP address included in the packet received by the data reception unit 232 matches the IP address acquired from the data processing storage unit 22, thereby confirming the accounting processing device 1. Authenticate.

The data receiving unit 232 receives invoice data from the accounting processing device 1 . The data receiving section 232 may acquire the business identification information included in the invoice data. The data receiving unit 232 acquires the destination business identification number C2 included in the invoice data D as business identification information.

The business identification information may be stored in the header attached to the invoice data sent from the accounting processing device 1. Therefore, the data receiving unit 232 may acquire the business identification information of the business that issued the bill corresponding to the bill data from the accounting processing device 1 in association with the bill data. The data receiving unit 232 acquires business identification information by referring to the header attached to the invoice data D received from the accounting processing device 1 .

The data receiving unit 232 may determine whether the acquired business identification information is included in the business information stored in the data processing storage unit 22. If the acquired business identification information is not included in the business information, the data receiving section 232 does not notify the invoice creating section 233 of the received bill data. By configuring the data processing device 2 in this manner, electronic invoices are created based on invoice data issued by unregistered business operators, and electronic invoices that should not be transmitted are transmitted to the invoice network N. can be prevented.

Further, when the acquired business identification information is not stored in the data processing storage unit 22, the data reception unit 232 may notify the accounting processing device 1 that the business is unregistered. The data receiving unit 232, for example, associates a message indicating that the acquired business identification information is not registered and that user registration is required with the received invoice data, and to notify. By configuring the data receiving unit 232 in this way, the user can know that the content of the data transmitted to the accounting processing apparatus 1 is incomplete.

The invoice creation unit 233 creates an electronic invoice by converting the invoice data received by the data reception unit 232 into a predetermined format on the condition that the accounting processing device 1 has been authenticated using the device authentication information. to the e-invoicing network. The invoice creating unit 233 creates an electronic invoice when the data receiving unit 232 receives invoice data from the accounting processing device 1 authenticated by the authenticating unit 231 . An electronic invoice is invoice data converted into a data format conforming to PEPPOL BIS (Business Interoperability Specification).

The invoice creation unit 233 creates an invoice based on the invoice data on the condition that the source IP address sent by the data receiving unit 232 together with the invoice data matches the IP address stored in the data processing storage unit 22. You may send an electronic invoice. When the authentication unit 231 authenticates the accounting processing device 1 based on the IP address included in the header attached to the invoice data, the invoice creation unit 233 creates an electronic invoice based on the received invoice data. , the created electronic invoice is transmitted to the relay device 4 .

The invoice creation unit 233 performs accounting processing on the device authentication information stored in the data processing storage unit 22 within a predetermined period of time before the data reception unit 232 receives the invoice data. An electronic invoice based on invoice data may be sent on condition that it has been received from the device 1 . The predetermined time is a time corresponding to the validity period of the authentication result of the accounting processing device 1 by the authentication unit 231, and is, for example, one minute. The invoice creation unit 233 inquires of the authentication unit 231 whether or not the authentication result of the accounting processing apparatus 1 is valid at the time the data reception unit 232 receives the invoice data. If the time is within the validity period of the authentication result, the invoice creation unit 233 creates an electronic invoice based on the invoice data and transmits the created electronic invoice to the relay device 4 .

The invoice creation unit 233 may create an electronic invoice containing the user identification information stored in the data processing storage unit 22 in association with the business entity identification information acquired by the data reception unit 232 . The invoice creation unit 233 refers to the business operator information stored in the data processing storage unit 22 and acquires user identification information corresponding to the business operator identification information acquired by the data reception unit 232 . The invoice creation unit 233 creates an electronic invoice by inputting the acquired user identification information into the field indicating the destination user identification information in the electronic invoice.

If the data included in the invoice data do not meet the requirements for creating an electronic invoice, the invoice creation unit 233 notifies the accounting processing device 1 that the invoice data does not meet the requirements. , the invoice creation unit 233 determines whether the data included in the invoice data satisfies predetermined requirements. The invoice creation unit 233 determines that the requirements are not satisfied, for example, when the required items are not input, the data type of the input items does not satisfy the requirements, or the data value is an abnormal value.

For example, if the invoice data does not include the business name, business identification information, product name or service name to be invoiced, or billing amount, the invoice creation unit 233 does not enter the required items. , determine that the invoice data does not meet the requirements. By configuring the invoice creation unit 233 in this manner, it is possible to prevent invoice data that does not meet the requirements from leaking to the invoice network.

[Flow of processing in data processing system S]
FIG. 8 is a sequence diagram showing the flow of processing in the data processing system S. As shown in FIG. The sequence diagram in FIG. 8 starts when the user operates the business operator terminal 3 and performs an operation to transmit bill data. The business operator terminal 3 transmits business authentication information to the accounting processing device 1 (S101). The authentication unit 131 compares the received operator authentication information with the operator authentication information to authenticate the operator terminal 3 . The authentication unit 131 transmits the authentication result to the operator terminal 3 (S102). When the authentication result indicates successful authentication, the business operator terminal 3 transmits bill data to the accounting processing device 1 (S103).

The data transmission unit 134 transmits the device authentication information to the data processing device 2 (S104). The authentication unit 231 verifies the received device authentication information and authenticates the transaction processing device 1 . The authentication unit 231 transmits the authentication result to the accounting processing device 1 (S105). If the authentication result is authentication success, the invoice data creating unit 133 creates invoice data. The data transmission unit 134 transmits the created invoice data to the data processing device 2 (S106).

The authentication unit 231 determines whether the accounting processing device 1 has been authenticated within a predetermined period of time prior to the receipt of the bill data (S107). If the transaction processing device 1 has not been authenticated within the predetermined time (NO in S107), the data receiving unit 232 outputs error information to the transaction processing device 1 (S108). The accounting processing device 1 that has received the error information outputs the error information to the business operator terminal 3 (S109).

If the accounting processing device 1 has been authenticated within the predetermined time (YES in S107), the data receiving unit 232 determines whether the invoice data belongs to a valid business operator (S110). That is, the data processing device 2 determines whether or not the business identification information included in the invoice data matches the business information stored in the storage unit 22 for data processing. If the business identification information included in the bill data does not match the business information stored in the data processing storage unit 22 and the bill data does not belong to a valid business (NO in S110), the data The receiving unit 232 outputs error information to the accounting processing device 1 (S111). The accounting processing device 1 that has received the error information outputs the error information to the business operator terminal 3 (S112).

If the bill data belongs to a valid business operator (YES in S110), the data receiving unit 232 determines whether the received bill data satisfies predetermined requirements (S113). Predetermined requirements include whether or not essential items are entered. If the received bill data does not meet the predetermined requirements (NO in S113), the data receiving unit 232 outputs error information to the accounting processing device 1 (S114). The accounting processing device 1 that has received the error information outputs the error information to the business operator terminal 3 (S115).

If the received invoice data satisfies the predetermined requirements (YES in S113), the invoice creation unit 233 acquires user identification information corresponding to the business operator identification information (S116). The invoice creation unit 233 creates an electronic invoice from the invoice data (S117). The invoice creation unit 233 transmits the created electronic invoice to the relay device 4 (S118). When the transmission of the electronic invoice is completed, the invoice creation unit 233 transmits completion information indicating that the transmission of the electronic invoice is completed to the accounting processing device 1 (S119). Upon receiving the completion information, the accounting processing device 1 transmits the completion information to the business operator terminal 3 (S120).

<Modification>
In the above description, the data processing device 2 stores the user identification information of each business as an example, but the data processing device 2 acquires the user identification information from the accounting processing device 1. may

In this case, the data receiving unit 232 acquires the user identification information corresponding to the business operator that issued the bill corresponding to the bill data from the accounting processing device 1 in association with the bill data. As an example, the data receiving unit 232 acquires the user identification information transmitted by the accounting processing device 1 together with the invoice data. Then, the invoice creating section 233 may create an electronic invoice including the user identification information acquired by the data receiving section 232 .

Note that the accounting processing device 1 may add user identification information to bill data and transmit it to the data processing device 2 . In this case, the accounting processing device 1 reads the user identification information stored in the accounting processing storage unit 12 in association with the business to which the invoice data is addressed, and adds the read user identification information to the invoice data. do.

[Effects of modified example]
By configuring the data processing system S in this way, the transaction processing apparatus 1 can centrally manage information about users. As a result, it is possible to realize a system that imposes less burden on the operation of the data processing device 2 .

[Effect of data processing system S]
As described above, in the data processing system S, the accounting processing device 1 in which the business entity issuing the invoice is registered, and the invoice data received from the accounting processing device 1 are converted into an electronic invoice in a predetermined format. and a data processing device 2 for processing. The accounting processing device 1 has an accounting processing storage unit 12 that stores business operator authentication information for authenticating the business operator, and a transaction created by the business operator on the condition that the business operator has been authenticated using the business operator authentication information. and a data transmission unit 134 that transmits bill data corresponding to the received bill to the data processing device 2 . The data processing device 2 includes a data processing storage unit 22 for storing device authentication information for authenticating the accounting processing device 1, a data receiving unit 232 for receiving invoice data from the accounting processing device 1, and device authentication information. Invoice creation for transmitting an electronic invoice created by converting the invoice data received by the data receiving unit 232 into a predetermined format to the electronic invoice network on condition that the accounting processing apparatus 1 has been authenticated using and a portion 233 .

With the data processing system S having such a configuration, the electronic invoice can be issued even if the device that creates the electronic invoice does not have information on the business operator that issued the invoice. can do. In particular, it is possible to allow a business operator to participate in the invoice network without the business operator providing the data processing device 2 performing user registration of the participants participating in the invoice network. Further, it is possible to reduce the burden on both the business operator who provides the data processing device 2 and the users of the invoice network.

Although the present invention has been described above using the embodiments, the technical scope of the present invention is not limited to the scope described in the above embodiments, and various modifications and changes are possible within the scope of the gist thereof. be. For example, all or part of the device can be functionally or physically distributed and integrated in arbitrary units. In addition, new embodiments resulting from arbitrary combinations of multiple embodiments are also included in the embodiments of the present invention. The effect of the new embodiment caused by the combination has the effect of the original embodiment.

1 Accounting device 2 Data processing device 3 Business operator terminal 4 Relay device 5 SMP
6 SML
11 communication unit 12 accounting processing storage unit 13 control unit 21 communication unit 22 data processing storage unit 23 control unit 131 authentication unit 132 data reception unit 133 invoice data creation unit 134 data transmission unit 135 display processing unit 231 authentication unit 232 data Receiving unit 233 Invoice creating unit

Claims

An accounting processing device in which a business that issues an invoice is registered, and a data processing device that converts invoice data received from the accounting processing device into an electronic invoice in a predetermined format,
The accounting processing device
an accounting processing storage unit that stores business operator authentication information for authenticating the business operator;
a data transmission unit configured to transmit the invoice data corresponding to the invoice created by the business operator to the data processing device on condition that the business operator has been successfully authenticated using the business operator authentication information;
has
The data processing device is
a data processing storage unit for storing device authentication information for authenticating the accounting processing device;
a data receiving unit that receives the invoice data from the accounting processing device;
An electronic invoice created by converting the bill data received by the data receiving unit into the predetermined format on condition that the accounting processing device is authenticated using the device authentication information. an invoice generator for transmission to a network;
A data processing system having
The data processing storage unit stores an IP address of the accounting processing device as the device authentication information,
The invoice creating unit generates the invoice data on condition that the source IP address sent by the data receiving unit together with the invoice data matches the IP address stored in the data processing storage unit. send electronic invoices based on
The data processing system of claim 1.
The invoice creation unit updates the device authentication information stored in the data processing storage unit within a predetermined period of time starting from the point in time when the data receiving unit receives the invoice data and before that point in time. Sending an electronic invoice based on the invoice data on the condition that it was received from the accounting device;
3. A data processing system according to claim 1 or 2.
The data receiving unit includes a user identification, which is information for identifying a user of an electronic invoice network to and from which an electronic invoice is sent and received, corresponding to the business operator who issued the invoice corresponding to the invoice data. obtaining information from the accounting processor in association with the invoice data;
The invoice creation unit creates an electronic invoice including the user identification information acquired by the data reception unit.
4. A data processing system according to any one of claims 1-3.
The data processing storage unit contains business identification information that is information for identifying the business, and user identification that is information for identifying users of an electronic invoice network to which electronic invoices are sent and received. store information in association with
The data receiving unit acquires from the accounting processing device the business identification information of a business that issued an invoice corresponding to the invoice data in association with the invoice data,
The invoice creation unit creates an electronic invoice including the user identification information stored in the data processing storage unit in association with the business identification information acquired by the data reception unit.
4. A data processing system according to any one of claims 1-3.
The data processing storage unit contains business identification information that is information for identifying the business, and user identification that is information for identifying users of an electronic invoice network to which electronic invoices are sent and received. store information in association with
The data receiving unit acquires the business identification information included in the invoice data,
The invoice creation unit creates an electronic invoice including the user identification information stored in the data processing storage unit in association with the business identification information acquired by the data reception unit.
4. A data processing system according to any one of claims 1-3.
If the acquired business identification information is not stored in the data processing storage unit, the data reception unit notifies the accounting processing device that the business is an unregistered business.
7. A data processing system according to claim 5 or 6.
When the data included in the invoice data does not meet the requirements necessary for creating an electronic invoice, the invoice creation unit notifies the accounting processing device that the invoice data does not meet the requirements. Notice,
A data processing system according to any one of claims 1-7.
The accounting processing device sends the invoice data by e-mail to the business terminal that transmits the invoice created by the business, or converts the invoice data into an electronic invoice and then sends the electronic invoice. further comprising a display processing unit for displaying a screen for selecting whether to transmit via a network;
The data transmission unit transmits the invoice data to the data processing device on condition that an instruction to convert the invoice data into an electronic invoice is received from the business operator terminal.
9. A data processing system according to any one of claims 1-8.
Data processing executed by a computer by an accounting processing device in which a business entity issuing an invoice is registered, and a data processing device that converts invoice data received from the accounting processing device into an electronic invoice in a predetermined format. A method, wherein the data processing method comprises:
a step in which the accounting processing device authenticates the business operator using the business operator authentication information stored in an accounting processing storage unit that stores business operator authentication information for authenticating the business operator;
a step of transmitting the invoice data corresponding to the invoice created by the business operator to the data processing device on condition that the accounting processing device has successfully authenticated the business operator;
the data processing device receiving the invoice data from the accounting device;
a step of authenticating the accounting processing device using the device authentication information stored in a data processing storage unit that stores device authentication information for authenticating the accounting processing device;
transmitting an electronic invoice created by converting the received invoice data into the predetermined format to an electronic invoice network on the condition that the accounting processing device has been successfully authenticated;
data processing methods that perform
a data processing storage unit for storing device authentication information for authenticating an accounting processing device registered with a business entity issuing an invoice;
a data receiving unit that receives invoice data corresponding to the invoice from the accounting processing device;
An electronic invoice created by converting the bill data received by the data receiving unit into a predetermined format on the condition that the accounting processing device is authenticated using the device authentication information is sent to an electronic invoice network. an invoice generator for sending to
A data processing device having