WO2023127116A1 - Data processing device, data processing method, and program - Google Patents

Data processing device, data processing method, and program Download PDF

Info

Publication number
WO2023127116A1
WO2023127116A1 PCT/JP2021/048847 JP2021048847W WO2023127116A1 WO 2023127116 A1 WO2023127116 A1 WO 2023127116A1 JP 2021048847 W JP2021048847 W JP 2021048847W WO 2023127116 A1 WO2023127116 A1 WO 2023127116A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
payment
issued
invoice
amount
Prior art date
Application number
PCT/JP2021/048847
Other languages
French (fr)
Japanese (ja)
Inventor
鴻鵬 葛
顕 松田
智 小俣
啓太郎 森
貴亮 佐藤
将和 早川
Original Assignee
ファーストアカウンティング株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ファーストアカウンティング株式会社 filed Critical ファーストアカウンティング株式会社
Priority to PCT/JP2021/048847 priority Critical patent/WO2023127116A1/en
Priority to JP2021578094A priority patent/JP7129734B1/en
Priority to JP2022129452A priority patent/JP2023098573A/en
Publication of WO2023127116A1 publication Critical patent/WO2023127116A1/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/22—Payment schemes or models
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes

Definitions

  • the present invention relates to a data processing device, a data processing method, and a program.
  • Patent Literature 1 describes an invoice management system that electronically manages invoices.
  • the present invention has been made in view of these points, and aims to reduce the burden on businesses that issue invoices.
  • 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.
  • the calculation unit may calculate the difference by further subtracting the second amount from the billing amount indicated by the received bill data.
  • 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.
  • 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.
  • FIG. 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.
  • 4 is a flow chart showing the flow of processing in the data processing device 1;
  • 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 accounting processing device 2 is a device that has the same functions as 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.
  • 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 issued bill 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 payment 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).
  • the person in charge of the business operator using the data processing device 1 writes it in the invoice 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.
  • FIG. 2 is a block diagram showing the configuration of the data processing device 1.
  • 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 payment server 3 via the network.
  • the storage unit 12 is, for example, a storage medium such as ROM (Read Only Memory), RAM (Random Access Memory), SSD (Solid State Drive), and hard disk.
  • the storage unit 12 stores various programs for causing the control unit 13 to function.
  • the storage unit 12 associates and stores the second business operator, which is the destination business operator of the bill issued by the first business operator, and the billing amount.
  • 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. 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.
  • Issued invoice data includes issued invoice number, invoice issue date, invoice payment deadline (also referred to as first payment deadline), invoice destination business operator, invoice amount, and 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 payment for the issued bill has been completed.
  • FIG. 3(b) is a diagram showing an example of the data structure of the invoice data stored in the storage unit 12.
  • 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 generation 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 the invoice 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 issued bill 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.
  • 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.
  • 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 creation 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 .
  • 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 sending 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.
  • 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.
  • 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.
  • the data creation unit 133 creates payment details 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).
  • 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.
  • the data creation unit 133 Upon receiving the approval notice, the data creation 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).
  • the data creation unit 133 creates payment detail data indicating the difference before sending 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.
  • 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.
  • 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.
  • 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.
  • the data creation unit 133 refers to the payment deadline included in the acquired invoice data to determine whether 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 the other party's approval 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.
  • journal data may create journal data corresponding to the issued invoice data and the received invoice data after creating the payment data.
  • 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 .
  • 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 billing amount indicated by the receipt data is larger than the billing amount of the unpaid bill issued. Alternatively, request data may be created for requesting the second business operator to pay the absolute value of the difference.
  • 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.
  • 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.
  • the data creation unit 133 transmits the request data to the accounting processing device 2 ((5) in FIG. 5).
  • the data processing device 1 calculates the payment amount by subtracting the amount according to the ratio of the burden of the other party.
  • 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 .
  • the amount determination unit 135 acquires information indicating the fee from the settlement server 3 .
  • 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 burden ratio are stored in association with each other in the business operator information stored in the storage unit 12 .
  • 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.
  • 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.
  • 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 .
  • 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.
  • the data processing device 1 may be configured so that the user of the first business operator sets the fee burden ratio.
  • 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).
  • the receiving unit 136 causes the user terminal to display a screen for receiving the input of the share of the commission between the first business operator and the second business operator.
  • accepting unit 136 outputs the burden ratio input by the user to amount determining unit 135 .
  • 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 .
  • 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).
  • 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 invoiced amount included in the received invoice is greater than the invoiced amount included in the issued invoice (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).
  • 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.
  • the data creation unit 133 creates payment details 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.
  • 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.
  • 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.
  • 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
  • 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.
  • a data creating unit 133 for creating settlement data for settlement of the difference.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Accounting & Taxation (AREA)
  • Theoretical Computer Science (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Finance (AREA)
  • Marketing (AREA)
  • Technology Law (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

A data processing device 1 comprising: a storage unit 12 that stores a second business operator, which is the destination business operator of an issued invoice issued by a first business operator, and the invoice amount in association with each other; a data acquisition unit 131 that acquires received invoice data issued by the second business operator; a calculation unit 132 that calculates a difference by subtracting, from the invoice amount indicated by the received invoice data, the invoice amount of the issued invoice that has not yet been paid; and a data creation unit 133 that creates settlement data for settling the difference.

Description

データ処理装置及びデータ処理方法及びプログラムDATA PROCESSING DEVICE, DATA PROCESSING METHOD AND PROGRAM
　本発明は、データ処理装置及びデータ処理方法及びプログラムに関する。 The present invention relates to a data processing device, a data processing method, and a program.
　請求書をオンラインで送受信する請求書管理システムが知られている。特許文献１には請求書を電子的に管理する請求書管理システムが記載されている。 An invoice management system that sends and receives invoices online is 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
　そこで、本発明はこれらの点に鑑みてなされたものであり、請求書を発行した事業者の負荷を軽減することを目的とする。 Therefore, the present invention has been made in view of these points, and aims to reduce the burden on businesses that issue 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. .
　前記データ作成部は、前記決済データを作成した後に、前記発行請求書及び前記受取請求書データに対応する仕訳データを作成してもよい。 After creating the payment data, the data creation unit may create journal data corresponding to the invoice data to be issued and the invoice data to be received.
　前記決済データに基づく決済処理を行うための手数料のうち、前記第１事業者が負担する第１金額と、前記第２事業者が負担する第２金額とを決定する金額決定部をさらに有し、前記算出部は、前記受取請求書データが示す請求額から前記第２金額をさらに減額した前記差額を算出してもよい。 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 that has the same functions as 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 explained. 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 issued bill 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 payment 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 writes it in the invoice 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 .
　通信部１１は、ネットワークを介して会計処理装置２及び決済サーバ３と通信するための通信インターフェースである。記憶部１２は、例えば、ＲＯＭ（Read Only Memory）、ＲＡＭ（Random Access Memory）、ＳＳＤ（Solid State Drive）、ハードディスク等の記憶媒体である。記憶部１２は、制御部１３を機能させるための各種のプログラムを記憶する。 The communication unit 11 is a communication interface for communicating with the accounting processing device 2 and the payment server 3 via the network. The storage unit 12 is, for example, a storage medium such as ROM (Read Only Memory), RAM (Random Access Memory), SSD (Solid State Drive), and hard disk. The storage unit 12 stores various programs for causing the control unit 13 to function.
　記憶部１２は、第１事業者が発行済の発行請求書の宛先事業者である第２事業者と請求額とを関連付けて記憶する。記憶部１２は、発行請求書の支払期限である第１支払期限をさらに関連付けて記憶してもよい。図３は、記憶部１２が記憶する請求書データのデータ構造の一例を示す図である。図３（ａ）は、記憶部１２が記憶する発行請求書データのデータ構造の一例を示す図である。 The storage unit 12 associates and stores the second business operator, which is the destination business operator of the bill issued by the first business operator, and the billing amount. 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.
　発行請求書データは、発行請求書番号、請求書の発行日、請求書の支払期限（第１支払い期限ともいう）、請求書の宛先事業者、請求額及び入金完了フラグを含む。発行請求書番号は発行した請求書を一意に識別する番号である。宛先事業者は一例として事業者番号と事業者名を含む。事業者番号は例えば、法人番号や請求書を授受するネットワークの利用者にわりあてられるＩＤ（Identification）である。事業者番号はＰＥＰＰＯＬ（Pan-European Public Procurement Online）　ＩＤであってもよい。入金完了フラグは、発行した請求書に対する入金が完了したか否かを示すフラグである。 Issued invoice data includes issued invoice number, invoice issue date, invoice payment deadline (also referred to as first payment deadline), invoice destination business operator, invoice amount, and 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 payment for the issued bill has been completed.
　図３（ｂ）は、記憶部１２が記憶する受取請求書データのデータ構造の一例を示す図である。受取請求書データは、発行元事業者、請求書の受領日、支払期限（第２支払期限ともいう）、受領請求書番号、請求額及び入金完了フラグを含む。 FIG. 3(b) is a diagram showing an example of the data structure of the 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.
　制御部１３は、例えばＣＰＵ（Central Processing Unit）である。制御部１３は、記憶部１２に記憶されている制御プログラムを実行することにより、データ取得部１３１、算出部１３２、データ作成部１３３、データ送信部１３４、金額決定部１３５及び受付部１３６として機能する。 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 generation 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 the invoice 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 issued bill 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 creation 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 invoice received and the invoice issued 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 transfer 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 sending 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, it is assumed that the other party's approval may be 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.
　図４を用いてこの場合の処理について説明する。図４は、実施の形態にかかるデータ処理システムＳの処理の一例を説明する図である。図４における（１）から（３）の処理は、図１における（１）から（３）の処理と共通であるため説明を省略する。 The processing in this case will be explained using 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 details 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 notice, the data creation 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 sending 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.
　発行請求書の支払期限が到来していない場合において相手方へ通知せずに相殺すると、トラブルとなる場合がある。そこで、データ処理装置１は、支払期限が到来していない場合においては、決済データの送信前に支払明細データを送信し、宛先事業者の承認を得てから決済データを送信し、支払期限が到来した後である場合には、宛先事業者の承認を得ることなく決済データを送信するように構成されてもよい。 If the payment deadline for the issued invoice has not yet arrived, set-off without notifying the other party 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 invoice data to determine whether 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 .
　なお、データ処理装置１は、発行請求書データの支払期限に加えて受取請求書データの支払期限に基づいて相手方の承認の要否を決定してもよい。すなわち、第１支払期限と第２支払期限とのいずれかが到来していない場合、決済サーバ３に決済データを送信する前に支払明細データを作成し、当該支払明細データに対する承認を宛先事業者から取得した後に、決済サーバ３に決済データを送信してもよい。この場合において、第１支払期限と第２支払期限との両方が到来している場合には、データ処理装置１は、宛先事業者の承認を得ることなく決済データを送信する。 It should be noted that the data processing device 1 may determine whether or not the other party's approval 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 would be very convenient for the user if journal data could be created after the settlement amount was 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 payment 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 invoice amount included in the issued invoice data is larger than the invoice amount included in the received invoice 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 billing amount indicated by the receipt data is larger than the billing amount of the unpaid bill issued. Alternatively, request data may be created for requesting the second business operator to pay the absolute value of the difference.
　図５を用いてこの場合の処理について説明する。図５は、実施の形態にかかるデータ処理システムＳの処理の一例を説明する図である。図５における（１）から（３）の処理は、図１における（１）から（３）の処理と共通であるため説明を省略する。 The processing in this case will be explained using 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 share of the settlement fee incurred at the time of settlement is predetermined. In this case, it is 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 burden ratio are stored in association with each other in the business operator information stored in the storage unit 12 .
　金額決定部１３５は、取得した手数料に負担割合を乗じて、第１事業者が負担する第１金額と、第２事業者が負担する第２金額とを決定する。なお、負担割合が定められていない場合、一例として、金額決定部１３５は、手数料を折半で負担するものと判定してもよい。そして、算出部１３２は、受取請求書データが示す請求額から第２金額をさらに減額した差額を算出する。すなわち、算出部１３２は、算出した受取請求書データの請求額と発行請求書－タとの差額から第２金額をさらに減算した金額を支払い対象の差額として算出する。 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 so 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 the 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 invoiced amount included in the received invoice is greater than the invoiced amount included in the issued invoice (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 arrived (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 details 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 invoice amount included in the received invoice is not greater than the invoice amount included in the issued invoice (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)

  1. 　第１事業者が発行済の発行請求書の宛先事業者である第２事業者と請求額とを関連付けて記憶する記憶部と、
    　前記第２事業者が発行した受取請求書データを取得するデータ取得部と、
    　前記受取請求書データが示す請求額から、未入金の前記発行請求書の請求額を減額した差額を算出する算出部と、
    　前記差額を決済するための決済データを作成するデータ作成部と、
    　を有するデータ処理装置。     a storage unit that associates and stores the second business operator, which is the destination business operator of the issued invoice issued by the first business operator, and the billing amount;
    a data acquisition unit that acquires the receipt 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;
    A data processing device having
  2. 　前記データ作成部は、前記受取請求書データが示す請求額が未入金の前記発行請求書の請求額よりも大きい場合に前記決済データを作成し、未入金の前記発行請求書の請求額以下である場合に、前記差額の絶対値の額を支払うことを前記第２事業者に要求するための要求データを作成する、
    　請求項１に記載のデータ処理装置。     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.
  3. 　前記データ作成部は、決済処理を行う決済サーバに前記決済データを送信した後に、前記差額を示す支払明細データを作成する、
    　請求項１又は２に記載のデータ処理装置。     The data creation unit creates payment detail data indicating the difference after transmitting the payment data to a payment server that performs payment processing.
    3. A data processing apparatus according to claim 1 or 2.
  4. 　前記データ作成部は、決済処理を行う決済サーバに前記決済データを送信する前に、前記差額を示す支払明細データを作成し、当該支払明細データに対する承認を前記宛先事業者から取得した後に、前記決済サーバに前記決済データを送信する、
    　請求項１又は２に記載のデータ処理装置。     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, transmitting the payment data to a payment server;
    3. A data processing apparatus according to claim 1 or 2.
  5. 　前記記憶部は、前記発行請求書の支払期限である第１支払期限をさらに関連付けて記憶し、
    　前記データ作成部は、前記第１支払期限が到来していない場合、前記決済サーバに前記決済データを送信する前に前記支払明細データを作成し、当該支払明細データに対する前記承認を前記宛先事業者から取得した後に、前記決済サーバに前記決済データを送信する、
    　請求項４に記載のデータ処理装置。     The storage unit further associates and stores a first payment deadline, which is the payment deadline for the issued invoice,
    If the first payment deadline has not yet arrived, the data creation unit creates the payment statement data before transmitting the payment data to the payment server, and requests the destination business operator to approve the payment statement data. transmitting the payment data to the payment server after obtaining from
    5. A data processing apparatus according to claim 4.
  6. 　前記発行請求書に対応する発行請求書データを前記第２事業者に送信するデータ送信部をさらに有し、
    　前記データ送信部は、前記支払明細データを前記第２事業者に送信する、
    　請求項３から５のいずれか１項に記載のデータ処理装置。     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.
  7. 　前記データ作成部は、前記決済データを作成した後に、前記発行請求書及び前記受取請求書データに対応する仕訳データを作成する、
    　請求項１から６のいずれか一項に記載のデータ処理装置。     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.
  8. 　前記決済データに基づく決済処理を行うための手数料のうち、前記第１事業者が負担する第１金額と、前記第２事業者が負担する第２金額とを決定する金額決定部をさらに有し、
    　前記算出部は、前記受取請求書データが示す請求額から前記第２金額をさらに減額した前記差額を算出する、
    　請求項１から７のいずれか一項に記載のデータ処理装置。     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.
  9. 　前記第１金額と前記第２金額との比率の設定を受け付ける受付部をさらに有し、
    　前記金額決定部は、前記受付部において設定された前記比率と前記手数料とに基づいて前記第１金額及び前記第２金額を決定する、
    　請求項８に記載のデータ処理装置。     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.
  10. 　コンピュータが実行する、
    　第１事業者が発行済の発行請求書の宛先事業者である第２事業者と請求額とを関連付けて記憶部に記憶させるステップと、
    　前記第２事業者が発行した受取請求書データを取得するステップと、
    　前記受取請求書データが示す請求額から、未入金の前記発行請求書の請求額を減額した差額を算出するステップと、
    　前記差額を決済するための決済データを作成するステップと、
    　を有するデータ処理方法。     the computer runs
    a step of associating the second business operator, who is the destination business operator of the issued invoice issued by the first business operator, with the billing amount and storing the same in a storage unit;
    obtaining bill receipt data issued by the second business operator;
    a 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 received invoice data;
    creating settlement data for settlement of the difference;
    A data processing method comprising:
  11. 　コンピュータに、
    　第１事業者が発行済の発行請求書の宛先事業者である第２事業者と請求額とを関連付けて記憶部に記憶させるステップと、
    　前記第２事業者が発行した受取請求書データを取得するステップと、
    　前記受取請求書データが示す請求額から、未入金の前記発行請求書の請求額を減額した差額を算出するステップと、
    　前記差額を決済するための決済データを作成するステップと、
    　を実行させるためのプログラム。     to the computer,
    a step of associating the second business operator, who is the destination business operator of the issued invoice issued by the first business operator, with the billing amount and storing the same in a storage unit;
    obtaining bill receipt data issued by the second business operator;
    a 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 received invoice data;
    creating settlement data for settlement of the difference;
    program to run the
PCT/JP2021/048847 2021-12-28 2021-12-28 Data processing device, data processing method, and program WO2023127116A1 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
PCT/JP2021/048847 WO2023127116A1 (en) 2021-12-28 2021-12-28 Data processing device, data processing method, and program
JP2021578094A JP7129734B1 (en) 2021-12-28 2021-12-28 DATA PROCESSING DEVICE, DATA PROCESSING METHOD AND PROGRAM
JP2022129452A JP2023098573A (en) 2021-12-28 2022-08-16 Data processing apparatus, data processing method, and program

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2021/048847 WO2023127116A1 (en) 2021-12-28 2021-12-28 Data processing device, data processing method, and program

Publications (1)

Publication Number Publication Date
WO2023127116A1 true WO2023127116A1 (en) 2023-07-06

Family

ID=83148933

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2021/048847 WO2023127116A1 (en) 2021-12-28 2021-12-28 Data processing device, data processing method, and program

Country Status (2)

Country Link
JP (2) JP7129734B1 (en)
WO (1) WO2023127116A1 (en)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH07129690A (en) * 1993-11-01 1995-05-19 Oki Software Kyushu:Kk Transaction processing system with commission processing
JP2003233765A (en) * 2002-02-07 2003-08-22 Financialeyes Co Ltd Transaction support server, transaction support system, transaction support method and program
JP2007109043A (en) * 2005-10-14 2007-04-26 Hitachi Ltd Netting processor, netting processing method and netting processing program
JP2015069493A (en) * 2013-09-30 2015-04-13 株式会社三井住友銀行 System and method for management of electronic recording credit
JP2019219933A (en) * 2018-06-20 2019-12-26 株式会社オービック Factoring device, factoring method, and factoring program
JP2020035370A (en) * 2018-08-31 2020-03-05 エヌ・ティ・ティ・コムウェア株式会社 Payment proxy device, settlement system, settlement method, and program

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH07129690A (en) * 1993-11-01 1995-05-19 Oki Software Kyushu:Kk Transaction processing system with commission processing
JP2003233765A (en) * 2002-02-07 2003-08-22 Financialeyes Co Ltd Transaction support server, transaction support system, transaction support method and program
JP2007109043A (en) * 2005-10-14 2007-04-26 Hitachi Ltd Netting processor, netting processing method and netting processing program
JP2015069493A (en) * 2013-09-30 2015-04-13 株式会社三井住友銀行 System and method for management of electronic recording credit
JP2019219933A (en) * 2018-06-20 2019-12-26 株式会社オービック Factoring device, factoring method, and factoring program
JP2020035370A (en) * 2018-08-31 2020-03-05 エヌ・ティ・ティ・コムウェア株式会社 Payment proxy device, settlement system, settlement method, and program

Also Published As

Publication number Publication date
JP7129734B1 (en) 2022-09-02
JPWO2023127116A1 (en) 2023-07-06
JP2023098573A (en) 2023-07-10

Similar Documents

Publication Publication Date Title
US7487127B2 (en) Merchant cash payment systems and methods
AU2002359630B2 (en) Electronic purchasing method and apparatus for performing the same
JP6431568B1 (en) Payroll management apparatus, method, and computer program
US20020120537A1 (en) Web based system and method for managing business to business online transactions
JP6942355B2 (en) Payroll equipment, methods, and computer programs
JP5858554B1 (en) Debtor debt reduction and financial content improvement method and system for lump sum factoring transactions with electronic record receivables
JP2009098986A (en) Electronic receivables mediating system
US7031940B2 (en) Charge collecting system and program for controlling the same
US20190272535A1 (en) System for providing overseas remittance service
JP2001243400A (en) Account managing system using related account
JP6816062B2 (en) Information processing equipment, information processing methods and programs
JP4461618B2 (en) Payment apparatus and method
AU2012369168B2 (en) Mobile money order
JP2001306962A (en) Commodity transaction system with funds raising function
US20030130938A1 (en) Coordination of independent billing and liquidity providers to facilitate electronic payments
WO2023127116A1 (en) Data processing device, data processing method, and program
US20120323774A1 (en) Point of sale (pos) systems and methods for making tax payments
JP2003242345A (en) Loan support system and computer program
KR20000036837A (en) Method of internet giro service
JP4838288B2 (en) Trust type electronic payment support system, method, and program
JP7280060B2 (en) Batch payment management server, payment information generation method and program
JP7162791B1 (en) Information processing device, information processing method, and program
KR102532996B1 (en) Method and device for supporting payment through mobile payment
JP7276951B1 (en) Information processing device, information processing method and program
US20240185195A1 (en) Method for real-time transfer of funds between customer and seller including generating accounting entries

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2021578094

Country of ref document: JP

Kind code of ref document: A

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21969997

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE