JP7129734B1 - DATA PROCESSING DEVICE, DATA PROCESSING METHOD AND PROGRAM - Google Patents

Abstract

Acquiring a storage unit 12 for storing in association with a second business operator who is a destination business operator of the issued invoice already issued by the first business operator and the billing amount, and data of the receipt of the invoice issued by the second business operator. A data acquisition unit 131, a calculation unit 132 for calculating the difference obtained by subtracting the invoice amount of the issued invoice that has not been paid from the invoice amount indicated by the received invoice data, and creating settlement data for settlement of the difference. The data processing device 1 has a data generation unit 133 that

Description

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

Bill management systems for sending and receiving bills online are known. Patent Literature 1 describes an invoice management system that electronically manages invoices.

WO2017/73102

In accounting work, it is necessary to accurately process payments based on a large number of invoices in a short period of time and to perform accurate payment confirmation based on issued invoices. There is

Accordingly, the present invention has been made in view of these points, and an object of the present invention is to reduce the burden on business operators who have issued invoices.

In the data processing device according to the first aspect of the present invention, a storage unit that stores a billing amount in association with a second business operator, which is a destination business operator of a bill issued by a first business operator; 2 a data acquisition unit that acquires data of an invoice issued by a business operator; a calculation unit that calculates the difference obtained by subtracting the invoice amount of the issued invoice that has not yet been paid from the invoice amount indicated by the invoice receipt data; and a data creating unit that creates settlement data for settlement of the difference.

The data creation unit creates the settlement data when the billed amount indicated by the received bill data is larger than the billed amount of the unpaid invoice issued, and if the billed amount of the unpaid bill issued is less than or equal to In some cases, request data may be generated for requesting the second operator to pay the absolute amount of the difference.

The data creation unit may create payment detail data indicating the difference after transmitting the payment data to a payment server that performs payment processing.

The data creation unit creates payment statement data indicating the difference before transmitting the payment data to a payment server that performs payment processing, and after obtaining approval for the payment statement data from the destination business operator, The payment data may be transmitted to a payment server.

The storage unit further associates and stores a first payment deadline, which is the payment deadline for the issued invoice, and the data creation unit stores the payment data in the payment server when the first payment deadline has not arrived. may be created before transmitting the payment details data, and after obtaining the approval for the payment details data from the destination business operator, the payment data may be sent to the settlement server.

The method may further include a data transmission unit that transmits issued invoice data corresponding to the issued invoice to the second business operator, and the data transmission unit may transmit the payment details data to the second business operator. .

The data creation unit may create journal data corresponding to the invoice data to be issued and the invoice data to be received after creating the payment data.

further comprising an amount determination unit that determines a first amount to be borne by the first business operator and a second amount to be borne by the second business operator, out of fees for performing payment processing based on the payment data. The calculation unit may calculate the difference by further subtracting the second amount from the billing amount indicated by the received bill data.

further comprising a reception unit that receives a setting of a ratio between the first amount and the second amount, wherein the amount determination unit determines the first amount and the commission based on the ratio and the commission set by the reception unit; The second amount may be determined.

In the data processing method according to the second aspect of the present invention, the computer executes the method in which the second business operator, who is the destination business operator of the issued invoice issued by the first business operator, and the billing amount are associated with each other and stored in the storage unit. a step of storing; a step of acquiring data of the bill received issued by the second business operator; and calculating a difference obtained by subtracting the bill amount of the bill issued that has not yet been paid from the bill amount indicated by the data of the bill received. and creating settlement data for settlement of the difference.

In the program according to the third aspect of the present invention, the step of causing the computer to associate the second business operator, which is the destination business operator of the issued invoice issued by the first business operator, with the billing amount, and store the amount in the storage unit; , the step of obtaining data of the invoice received issued by the second business operator, and the step of calculating the difference obtained by subtracting the invoice amount of the issued invoice that has not yet been paid from the invoice amount indicated by the invoice receipt data; and a step of creating settlement data for settlement of the difference.

According to the present invention, it is possible to reduce the burden on the business operator who issued the invoice.

It is a figure explaining the outline|summary of the data processing system S concerning embodiment. 2 is a block diagram showing the configuration of the data processing device 1; FIG. 4 is a diagram showing an example of the data structure of invoice data stored in a storage unit 12; FIG. It is a figure explaining an example of a process of data processing system S concerning an embodiment. It is a figure explaining an example of a process of data processing system S concerning an embodiment. 4 is a flow chart showing the flow of processing in the data processing device 1;

[Overview of data processing system S]
FIG. 1 is a diagram illustrating an overview of a data processing system S according to an embodiment. The data processing system S is a system for exchanging electronic invoice data and making payments based on the exchanged invoice data. The data processing system S has a data processing device 1 , an accounting processing device 2 and a settlement server 3 .

The data processing device 1 is a device that generates invoice data and transmits the generated invoice data. The data processing device 1 is, for example, a server. The data processing device 1, for example, transmits the bill data to the accounting processing device 2 used by the company to which the bill is addressed, via a network.

The accounting processing device 2 is a device having functions similar to those of the data processing device 1 . In this specification, it is assumed that the accounting processing device 2 is used by a business operator different from the business operator using the data processing device 1 . The settlement server 3 is a server for performing payment processing. The settlement server 3 is, for example, a server provided by a financial institution or the like.

Next, the flow of payment processing in the data processing system S will be described. The data processing device 1 transmits the issued bill data to the accounting processing device 2 ((1) in FIG. 1). Issued invoice data is electronic data of issued invoices. The business operator that issued the issued bill data may be referred to as the first business operator, and the destination business operator of the issued bill data may be referred to as the second business operator. The data processing device 1 acquires the bill receipt data ((2) in FIG. 1). The bill receipt data is electronic data of a bill issued by the second business operator with the first business operator as the destination business operator.

The data processing device 1 calculates the difference by subtracting the billed amount of the unpaid bill issued data from the billed amount indicated by the received bill data ((3) in FIG. 1). The data processing device 1 creates settlement data for settlement of the calculated difference ((4) in FIG. 1). The settlement data is data that instructs the settlement server 3 about the amount to be settled and the payee.

The data processing device 1 transmits the created payment data to the payment server 3 ((5) in FIG. 1). The data processing device 1 creates payment details data ((6) in FIG. 1). The payment detail data is data including the difference to be paid in the settlement data. The payment details data may include data indicating the issued bill data and the received bill data used to calculate the difference. The data processing device 1 transmits the payment details data to the accounting processing device 2 ((7) in FIG. 1). As a result of the above processing, when payment has not been received from the destination business operator of the issued bill data, the person in charge of the business operator using the data processing device 1 has entered the bill without demanding the destination business operator. Since the cost can be recovered and the amount of work for deposit processing can be reduced, the burden on the person in charge can be reduced.

[Configuration of data processor 1]
FIG. 2 is a block diagram showing the configuration of the data processing device 1. As shown in FIG. The data processing device 1 has a communication section 11 , a storage section 12 and a control section 13 . The control unit 13 has a data acquisition unit 131 , a calculation unit 132 , a data generation unit 133 , a data transmission unit 134 , an amount determination unit 135 and a reception unit 136 .

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

The storage unit 12 stores the second business operator, which is the destination business operator of the bill issued by the first business operator, and the billing amount in association with each other. The storage unit 12 may further associate and store the first payment deadline, which is the payment deadline of the bill to be issued. FIG. 3 is a diagram showing an example of the data structure of invoice data stored in the storage unit 12. As shown in FIG. FIG. 3A is a diagram showing an example of the data structure of issued bill data stored in the storage unit 12. As shown in FIG.

The issued invoice data includes the issued invoice number, the invoice issue date, the invoice payment deadline (also referred to as the first payment deadline), the invoice destination business operator, the invoice amount, and the payment completion flag. The issued invoice number is a number that uniquely identifies the issued invoice. The destination business includes, for example, a business number and business name. A business number is, for example, a corporate number or an ID (Identification) assigned to a network user who exchanges bills. The business number may be a PEPPOL (Pan-European Public Procurement Online) ID. The payment completion flag is a flag indicating whether or not the payment for the issued bill has been completed.

FIG. 3B is a diagram showing an example of the data structure of invoice data stored in the storage unit 12. As shown in FIG. The received bill data includes the issuing business operator, the date of receipt of the bill, the payment deadline (also referred to as the second payment deadline), the received bill number, the billed amount, and the payment completion flag.

The control unit 13 is, for example, a CPU (Central Processing Unit). The control unit 13 functions as a data acquisition unit 131, a calculation unit 132, a data creation unit 133, a data transmission unit 134, an amount determination unit 135, and a reception unit 136 by executing the control programs stored in the storage unit 12. do.

The data acquisition unit 131 acquires bill receipt data issued by the second business operator. The data acquisition unit 131 acquires bill receipt data from the accounting processing device 2 used by the second business operator. The data acquisition unit 131 causes the storage unit 12 to store the acquired invoice receipt data.

The calculation unit 132 calculates the difference by subtracting the billed amount of the unpaid bill issued from the billed amount indicated by the received bill data. The calculation unit 132 searches the issued bill data stored in the storage unit 12 using the issuing business operator included in the received bill data as a search key, and retrieves the unpaid bill issued data corresponding to the received bill data. to get The calculation unit 132 calculates the difference by subtracting the billed amount of the obtained issued bill data from the billed amount included in the received bill data.

When there are a plurality of unpaid invoice data to be issued that the calculation unit 132 has acquired, the calculation unit 132 calculates, for example, the invoice amount and the invoice amount included in the issued invoice data or received invoice data with the oldest issue date. The difference may be calculated using the closest issued bill data. Further, when there are a plurality of acquired unpaid invoice data to be issued, the calculation unit 132 may calculate the difference by subtracting the sum of the invoiced amounts from the invoiced amount indicated by the received invoice data. If there are a plurality of receipt data issued by the same business operator, the difference between the billed amount of the issued bill and the sum of billed amounts in the plurality of receipt bill data may be calculated.

In the example shown in FIG. 3, the invoice data enclosed by the thick line in the invoice data shown in FIG. 3(a), the addressee company is "B Trading", the payment completion flag is "not completed", and the billed amount is "150,000 yen", which is surrounded by a thick line in the issued invoice data shown in FIG. 3(a). Get invoice data for The calculation unit 132 calculates the difference between the billed amount of the received bill data and the bill issued. The calculation unit 132 calculates the difference as "100,000 yen".

The data creating unit 133 creates settlement data for settlement of the difference. The data creation unit 133 may display a screen for approving the payment on a user terminal (not shown) used by the user of the first business operator, and create payment data when an operation to approve is performed. . The data creation unit 133 then transmits the created payment data to the payment server 3 .

When settling the difference between the received invoice and the issued invoice in this way, it may be difficult for the other party to link the billing data and the payment data because the billed amount charged by the other party and the actual transferred amount differ. Therefore, the data processing device 1 may create payment detail data indicating the basis of the payment amount.

The data creation unit 133 may create payment detail data indicating the difference after transmitting the payment data to the payment server 3 that performs payment processing. The payment details data includes, for example, the payment amount, the issued invoice number included in the issued invoice data used to calculate the payment amount, and the received invoice number of the received invoice used to calculate the payment amount. including.

By the way, depending on the destination business operator, there may be a case where the other party's approval is required to pay the difference. In this case, the data processing device 1 may be configured to transmit the payment detail data before transmitting the payment data and obtain approval from the destination business operator.

Processing in this case will be described with reference to FIG. FIG. 4 is a diagram explaining an example of processing of the data processing system S according to the embodiment. Since the processes (1) to (3) in FIG. 4 are common to the processes (1) to (3) in FIG. 1, the description thereof is omitted.

When the calculation unit 132 calculates the difference, the data creation unit 133 creates payment detail data ((4) in FIG. 4). The payment details data in this case may include information indicating that the issued invoice and the acquired invoice, which are the basis of the payment details data, have not yet been settled. The data transmission unit 134 transmits the created payment statement data to the accounting processing device 2 ((5) in FIG. 4). When the user of the second business operator confirms the payment details data and performs an operation to approve the payment based on the difference, the accounting processing device 2 transmits an approval notice ((6) in FIG. 4). The approval notice is a notice indicating approval of payment based on the received payment detail data.

Upon receiving the approval notification, the data creating unit 133 creates settlement data for settlement of the calculated difference ((7) in FIG. 4). The data transmission unit 134 transmits the created payment data to the payment server 3 ((8) in FIG. 4).

Returning to FIG. 2, the data creation unit 133 creates payment detail data indicating the difference before transmitting payment data to the payment server 3 that performs payment processing, and obtains approval for the payment detail data from the destination business operator. The payment data may be transmitted to the payment server 3 later. As an example, the data creation unit 133 may refer to the offset enable/disable flag set for each business operator to determine whether to create payment data after receiving approval from the destination business operator. The offset propriety flag is, for example, information indicating that “offset is possible without prior approval”, “needs approval for offset”, or “cannot be offset” for each business operator. For example, when the offset enable/disable flag corresponding to the destination business operator is "requires approval for offset", the data creation unit 133 sends a request for approval of the payment details data to the accounting processing device 2 of the destination business operator. Settlement data is sent to the settlement server 3 on the condition that the transmitted request is approved.

Set-off without notifying the other party when the payment deadline for the issued invoice has not yet arrived may cause trouble. Therefore, when the payment deadline has not yet arrived, the data processing device 1 transmits the payment details data before transmitting the payment data, obtains the approval of the destination business operator, and then transmits the payment data. If it is after arrival, it may be configured to send the payment data without obtaining the approval of the destination operator.

Specifically, first, the data creation unit 133 refers to the payment deadline included in the acquired issued bill data, and determines whether or not the payment deadline has arrived. Subsequently, if the payment deadline has not yet arrived, the data creation unit 133 creates payment detail data before sending the payment data to the payment server 3, and after obtaining approval for the payment detail data from the destination business operator, , the payment data is sent to the payment server 3 .

The data processing device 1 may determine whether or not approval of the other party is required based on the payment deadline of the received bill data in addition to the payment deadline of the issued bill data. That is, if either the first payment deadline or the second payment deadline has not arrived, payment detail data is created before the payment data is transmitted to the payment server 3, and the destination business operator requests approval for the payment detail data. The payment data may be transmitted to the payment server 3 after being acquired from the payment server 3 . In this case, when both the first payment deadline and the second payment deadline have passed, the data processing device 1 transmits the payment data without obtaining the approval of the destination business operator.

It is very convenient for the user if the journal data can be created after the settlement amount is determined. Therefore, the data creation unit 133 may create journal data corresponding to the issued invoice data and the received invoice data after creating the settlement data. As an example, the data creation unit 133 creates journal data indicating that the accounts receivable corresponding to the issued bill data and the accounts payable corresponding to the received bill data are set off.

The data transmission unit 134 transmits the issued invoice data corresponding to the issued invoice to the second business operator. Also, the data transmission unit 134 may transmit the payment statement data to the second business operator. The data transmission unit 134 transmits the issued bill data or the payment details data to the accounting processing device 2 used by the second business operator via the communication unit 11 .

By the way, if the billing amount included in the issued bill data is larger than the billed amount included in the received bill data, it will be necessary to receive payment of the difference from the other party. Therefore, the data processing device 1 may be configured to create data requesting payment of the difference in such a case. That is, the data creation unit 133 creates settlement data when the billed amount indicated by the receipt data is larger than the billed amount of the unpaid invoice issued, and when it is less than or equal to the billed amount of the unpaid issued invoice. Alternatively, request data may be created for requesting the second business operator to pay the absolute value of the difference.

Processing in this case will be described with reference to FIG. FIG. 5 is a diagram explaining an example of processing of the data processing system S according to the embodiment. Since the processes (1) to (3) in FIG. 5 are common to the processes (1) to (3) in FIG. 1, the description thereof is omitted.

As a result of calculating the difference, if the billed amount indicated by the received bill data is equal to or less than the billed amount of the unpaid issued bill, the data creation unit 133 creates request data ((4) in FIG. 5). Request data is data requesting payment of the difference. The requested data includes the calculated absolute value of the difference as the requested amount to be paid from the second business operator. The requested data may further include the issued bill number included in the issued bill data used to calculate the requested amount and the received bill number of the received bill used to calculate the requested amount. Then, the data creation unit 133 transmits the request data to the accounting processing device 2 ((5) in FIG. 5).

By the way, there are cases where the proportion of the settlement fee that occurs at the time of settlement is determined in advance. In this case, it is very convenient for the user if the data processing device 1 calculates the payment amount by subtracting the amount according to the ratio of the burden of the other party.

Therefore, the amount determination unit 135 determines the first amount to be borne by the first business operator and the second amount to be borne by the second business operator, among the fees for performing payment processing based on the payment data. good. The amount determination unit 135 acquires the fee necessary for settlement of the difference acquired from the calculation unit 132 . As an example, the amount determination unit 135 acquires information indicating the fee from the settlement server 3 . Then, the amount determination unit 135 refers to the storage unit 12 and acquires the fee burden ratio corresponding to the second business operator. In this case, the information for identifying the second business operator and the fee sharing ratio are stored in the business information stored in the storage unit 12 in association with each other.

The amount determination unit 135 multiplies the acquired fee by the burden ratio to determine the first amount to be borne by the first business operator and the second amount to be borne by the second business operator. In addition, when the burden ratio is not set, as an example, the amount determining unit 135 may determine that the fee is shared equally. Then, the calculation unit 132 calculates the difference by further subtracting the second amount from the billing amount indicated by the received bill data. That is, the calculation unit 132 calculates an amount obtained by further subtracting the second amount from the calculated difference between the billed amount of the received bill data and the issued bill data as the difference to be paid.

In the above example, an example in which the fee burden ratio is predetermined for each business operator has been described, but the information for the storage unit 12 to identify the second business operator, the content of the transaction, and the fee burden ratio are stored in association with each other, and the calculation unit 132 stores the burden ratio stored in the storage unit 12 in association with the name of the business operator described in the invoice to be settled and the content of the transaction. Fees may be determined.

Further, the storage unit 12 stores the billed amount and the fee burden ratio in association with each other. The fee may be determined based on the burden percentage stored in the . As an example, the calculation unit 132 increases the burden ratio of the issuing company when the billing amount described in the issued bill is large, compared to when the billing amount is small. By configuring the data processing device 1 in this way, it becomes possible to bear appropriate fees according to the contents of various transactions.

Furthermore, the data processing device 1 may be configured such that the user of the first business operator sets the fee burden ratio. In this case, the reception unit 136 receives the setting of the ratio between the first amount of money and the second amount of money (that is, the burden ratio). As an example, the receiving unit 136 causes the user terminal to display a screen for receiving an input of the share of the commission between the first business operator and the second business operator. Then, accepting unit 136 outputs the burden ratio input by the user to amount determining unit 135 . Then, the amount determination unit 135 determines the first amount and the second amount based on the ratio and the commission set in the reception unit 136 .

[Flow of processing in data processor 1]
FIG. 6 is a flow chart showing the flow of processing in the data processing device 1. As shown in FIG. The flowchart in FIG. 6 starts when the data acquisition unit 131 is ready to acquire the invoice. The data acquisition unit 131 acquires receipt data (S01). The data acquisition unit 131 determines whether or not there is issued invoice data corresponding to the issuer of the invoice (S02).

If there is corresponding invoice data (YES in S02), the calculation unit 132 refers to the storage unit 12, acquires the invoice corresponding to the invoice receipt data, and obtains the invoice receipt data included in the acquired invoice receipt data. The difference between the billed amount and the issued bill data is calculated (S03).

The data creation unit 133 determines whether the amount billed in the bill received is greater than the amount billed in the bill issued (S04). If the invoice amount included in the received invoice is larger than the invoice amount included in the issued invoice (YES in S04), the data creation unit 133 determines whether the payment deadline included in the issued invoice data has arrived. (S05).

If the payment deadline included in the issued bill data has passed (YES in S05), the data creation unit 133 creates settlement data for settlement of the difference calculated by the calculation unit 132 (S06). Then, the data creation unit 133 transmits the payment data to the payment server 3 (S07). The data creation unit 133 creates payment detail data indicating the grounds for the settled balance (S08). Then, the data transmission unit 134 transmits the payment statement data created by the data creation unit 133 to the accounting processing device 2 (S09), and ends the process.

If the payment deadline included in the issued bill data has not arrived (NO in S05), the data creation unit 133 creates payment detail data (S10). Then, the data transmission unit 134 transmits the payment statement data created by the data creation unit 133 to the accounting processing device 2 (S11). When an approval operation is performed in the accounting processing device 2, the data acquisition unit 131 acquires an approval notice (S12). When the data acquisition unit 131 acquires the approval notification, the data creation unit 133 creates payment data (S13). The data creation unit 133 transmits the payment data to the payment server 3 (S14). Then, the data processing device 1 terminates the processing.

If the billed amount included in the received bill is not greater than the billed amount included in the issued bill (NO in S04), the data creation unit 133 creates payment request data (S15). Then, the data transmission unit 134 transmits the payment request data to the accounting processing device 2 (S16). Then, the data processing device 1 terminates the processing.

If there is no corresponding issued bill data (NO in S02), the data creation unit 133 creates payment data indicating that the billed amount included in the received bill is to be settled (S17). Then, the data creation unit 133 transmits the payment data to the payment server 3 (S18). Then, the data processing device 1 terminates the processing.

[Effects of data processor 1]
As described above, the data processing device 1 includes the storage unit 12 that stores the billing amount in association with the second business operator, which is the destination business operator of the issued invoice issued by the first business operator, and the second business operator. A data acquisition unit 131 that acquires data of an invoice issued by a business operator, and a calculation unit 132 that calculates the difference obtained by subtracting the invoice amount of the issued invoice that has not been paid from the invoice amount indicated by the invoice receipt data. , and a data creating unit 133 for creating settlement data for settlement of the difference. By configuring the data processing device 1 in this way, it is possible to set off the amounts billed by the parties who have issued the bills and settle the accounts. It is possible to reduce the burden on the person in charge.

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 Data processing device 2 Accounting processing device 3 Settlement server 11 Communication unit 12 Storage unit 13 Control unit 131 Data acquisition unit 132 Calculation unit 133 Data creation unit 134 Data transmission unit 135 Amount determination unit 136 Acceptance unit

Claims (11)

a storage unit that associates and stores a second business operator that is a destination business operator of an issued invoice that has already been issued by the first business operator, an invoice amount, and a first payment deadline that is a payment deadline of the issued invoice ;
a data acquisition unit that acquires invoice data issued by the second business operator;
a calculation unit for calculating a difference obtained by subtracting the billed amount of the issued bill that has not yet been paid from the billed amount indicated by the received bill data;
a data creation unit that creates settlement data for settlement of the difference;
has
If the first payment deadline has not arrived, the data creation unit acquires data indicating approval from the destination business operator before transmitting the payment data to a payment server that performs payment processing, and then performs the payment. sending the payment data to a server, and sending the payment data to the payment server when the first payment deadline has arrived;
Data processing equipment. The data creation unit creates the settlement data when the billed amount indicated by the received bill data is larger than the billed amount of the unpaid invoice issued, and if the billed amount of the unpaid bill issued is less than or equal to In some cases, creating request data for requesting the second business operator to pay the amount of the absolute value of the difference;
2. A data processing apparatus according to claim 1. The data creation unit creates payment detail data indicating the difference after transmitting the payment data to the payment server.
3. A data processing apparatus according to claim 1 or 2. The data creation unit creates payment detail data indicating the difference before transmitting the payment data to the payment server, and after obtaining approval for the payment detail data from the destination business operator, transmits the payment data to the payment server. transmitting said payment data;
3. A data processing apparatus according to claim 1 or 2. Previous If the first payment deadline has not arrived, the data creation unit creates the payment detail data before transmitting the payment data to the payment server, and sends the approval for the payment detail data to the destination business operator. transmitting the payment data to the payment server after obtaining from
5. A data processing apparatus according to claim 4. further comprising a data transmission unit that transmits issued bill data corresponding to the issued bill to the second business operator;
The data transmission unit transmits the payment details data to the second business operator.
6. A data processing apparatus according to any one of claims 3 to 5. After creating the payment data, the data creation unit creates journal data corresponding to the invoice data to be issued and the invoice data to be received.
A data processing apparatus according to any one of claims 1 to 6. further comprising an amount determination unit that determines a first amount to be borne by the first business operator and a second amount to be borne by the second business operator, out of fees for performing payment processing based on the payment data. ,
wherein the calculation unit calculates the difference by further subtracting the second amount from the billing amount indicated by the received bill data;
A data processing apparatus according to any one of claims 1 to 7. further comprising a reception unit that receives setting of a ratio between the first amount and the second amount;
The amount determination unit determines the first amount and the second amount based on the ratio and the fee set in the reception unit,
9. A data processing apparatus according to claim 8. the computer runs,
a step of obtaining bill receipt data issued by the second business operator;,
The first business operator refers to a storage unit that associates and stores the second business operator that is the destination business operator of the issued invoice that has already been issued, the amount of the invoice, and the first payment deadline that is the payment deadline of the issued invoice. , a step of calculating the difference obtained by subtracting the billed amount of the issued bill that has not been paid from the billed amount indicated by the received bill data;
creating settlement data for settlement of the difference;
In the creating step,referring to the storage unit,If the first payment deadline has not arrived,After acquiring data indicating approval from the destination business operator before transmitting the payment data to a settlement server that performs settlement processing, the settlement data is transmitted to the settlement server, and the first payment deadline is reached. if so, sending the payment data to the payment server;
A data processing method comprising: to the computer,
a step of obtaining bill receipt data issued by the second business operator;,
The first business operator refers to a storage unit that associates and stores the second business operator that is the destination business operator of the issued invoice that has already been issued, the amount of the invoice, and the first payment deadline that is the payment deadline of the issued invoice. , a step of calculating the difference obtained by subtracting the billed amount of the issued bill that has not been paid from the billed amount indicated by the received bill data;
creating settlement data for settlement of the difference;
In the creating step,referring to the storage unit,If the first payment deadline has not arrived,After acquiring data indicating approval from the destination business operator before transmitting the payment data to a settlement server that performs settlement processing, the settlement data is transmitted to the settlement server, and the first payment deadline is reached. if so, sending the payment data to the payment server;
program to run the

Images