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

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

Info

Publication number
WO2023119580A1
WO2023119580A1 PCT/JP2021/047975 JP2021047975W WO2023119580A1 WO 2023119580 A1 WO2023119580 A1 WO 2023119580A1 JP 2021047975 W JP2021047975 W JP 2021047975W WO 2023119580 A1 WO2023119580 A1 WO 2023119580A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
billing
billing data
periodic
issued
Prior art date
Application number
PCT/JP2021/047975
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 JP2021576751A priority Critical patent/JP7215779B1/en
Priority to PCT/JP2021/047975 priority patent/WO2023119580A1/en
Priority to JP2023002753A priority patent/JP2023094617A/en
Publication of WO2023119580A1 publication Critical patent/WO2023119580A1/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
    • G06Q30/00—Commerce
    • G06Q30/04—Billing or invoicing

Definitions

  • 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 Document 1 requires processing by the person in charge in order to issue the invoice.
  • it is necessary to process a large amount of billing data, and it is necessary to prevent omission of billing due to human error.
  • the present invention has been made in view of these points, and aims to provide information for preventing billing omissions for continuous transactions.
  • a specifying unit for specifying periodic billing data indicating the billing content of a bill issued periodically; After the first timing of creating or issuing the invoice and before the second timing of creating or issuing the invoice after the first timing, it is determined whether or not the invoice has been issued. and an output unit that outputs warning information when the determination unit determines that the invoice based on the regular billing data has not been issued.
  • a periodic data storage unit that associates and stores the destination business operator of the periodic billing data and the one or more items to be billed in the periodic billing data, wherein the specifying unit stores the items stored in the periodic data storage unit; Billing data including the destination business operator and the one or more items may be identified as the periodic billing data.
  • the periodic data storage unit further stores the timing of issuing the bill in association with the destination business operator and the one or more items, and the determination unit stores the timing of issuing the invoice from the first timing determined based on the timing of issuing the bill. It may be determined whether or not the invoice has been issued later than the second timing and before the second timing.
  • an acquisition unit that acquires purchase order data or contract data that includes a destination business operator, one or more items to be billed, and a periodic delivery date or a periodic billing date; may specify, as the periodic billing data, billing data including the destination business operator and the one or more items described in the purchase order data or the contract data.
  • a destination business operator for each of a plurality of billing data indicating billing content in the issued bill, one or more items to be billed in each of the plurality of billing data, and an issue date of each of the plurality of billing data.
  • the determination unit searches the billing history information using the destination business operator and the one or more items included in the periodic data as keys, and searches for the billing history information.
  • the periodical billing data has been issued based on whether the billing data having the latest issue date among the one or more billing data extracted from the billing history information is within a predetermined range from the time of retrieval. It may be determined whether
  • a destination business operator for each of a plurality of billing data indicating billing content in the issued bill, one or more items to be billed in each of the plurality of billing data, and an issue date of each of the plurality of billing data.
  • a billing data storage unit for storing associated billing history information, wherein the specifying unit performs mutual identification of three or more of the billing data in which the destination business operator and the item to be billed match in the billing history information;
  • the periodical billing data may be specified based on a plurality of the intervals between the billing data having the closest issuing dates among the intervals of the issuing dates.
  • the identifying unit may identify the three or more pieces of billing data as the regular billing data when the variations in the plurality of intervals are within a predetermined range.
  • a storage unit that stores a learned model that outputs information indicating whether or not it is the regular billing data when a business operator and an item are entered, wherein the specifying unit stores the billing content of the bill that has been issued. and one or more items to be billed in each of the plurality of billing data are input into the learned model, and the information output from the trained model is used for the periodic billing data, the billing data corresponding to the destination business operator and the one or more items input to the trained model may be identified as the periodic billing data.
  • a computer-executed step of identifying periodic billing data indicating billing content in a periodically issued bill After the first timing of creating or issuing an invoice based on periodic billing data and before the second timing of creating or issuing the invoice after the first timing, the invoice has been issued. and outputting warning information when it is determined in the determining step that the bill based on the periodic billing data has not been issued.
  • a computer executes a step of identifying periodic billing data indicating the billing content of a bill issued periodically;
  • the invoice has been issued after a first timing of creating or issuing an invoice based on data and before a second timing of creating or issuing the invoice after the first timing. and outputting warning information when it is determined in the determining step that the bill based on the periodic billing data has not been issued.
  • FIG. 2 is a block diagram showing the configuration of the data processing device 1;
  • FIG. 4 is a diagram showing an example of a data structure of regular data stored in a regular data storage unit 121;
  • FIG. 4 is a diagram showing an example data structure of billing history information stored in a billing data storage unit 122.
  • FIG. 6 is a diagram showing an example of order form data acquired by an acquisition unit 134;
  • FIG. 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 that generates invoice data and exchanges invoice data.
  • the invoice data is electronic invoice data.
  • a data processing system S has a data processing device 1 and an information terminal 2 .
  • the data processing device 1 is a device that generates bill data and transmits the generated bill data to an accounting processing device (not shown) used by the business operator to whom the bill is addressed.
  • the data processing device 1 automatically issues a bill issued periodically.
  • the data processing device 1 is, for example, a server.
  • the information terminal 2 is a device for displaying information output by the data processing device 1 and for operating the data processing device 1 .
  • the information terminal 2 is a tablet, a smart phone, a personal computer, or the like.
  • the data processing device 1 identifies periodic billing data ((1) in FIG. 1). As an example, the data processing device 1 identifies periodic billing data based on pre-registered periodic data. Periodical data is data that associates a business to which a bill issued periodically is addressed and an item to be billed on the bill.
  • the data processing device 1 determines whether or not a bill based on the identified periodic billing data has been issued ((2) in FIG. 1).
  • the data processing device 1 outputs warning information to the information terminal 2 when a bill based on the specified periodic billing data has not been issued ((3) in FIG. 1).
  • 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 storage unit 12 has a regular data storage unit 121 , a billing data storage unit 122 and a model storage unit 123 .
  • the control unit 13 has an identification unit 131 , a determination unit 132 , an output unit 133 and an acquisition unit 134 .
  • the communication unit 11 is a communication interface for communicating with the information terminal 2 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 regular data storage unit 121 associates and stores the destination business operator of the regular billing data with one or more items to be billed in the regular billing data.
  • FIG. 3 is a diagram showing an example of the data structure of regular data stored in the regular data storage unit 121.
  • the regular data ID (Identification)
  • the regular data ID is an identifier for identifying registered regular billing data.
  • the destination of periodic billing data is, for example, at least one of the business number or business name of the destination business.
  • the item of periodic billing data is, for example, the name of one or more goods or services to be billed in the periodic billing data. Items of recurring billing data may include quantities of each product or service. Items of periodic billing data may be further associated with item types, prices, account titles, and the like.
  • the periodic data storage unit 121 may further store the timing of issuing the invoice in association with the destination business operator and one or more items.
  • billing times for periodic billing are stored in association with periodical billing data.
  • the billing period includes, for example, the billing date and cycle.
  • the billing date is the date on which the invoice is issued when the time for issuing the invoice has arrived.
  • a cycle is a cycle of issuing a bill. For example, if the billing period indicated by the periodical data indicates that the billing date is every 30th and the cycle is every month, the periodical data indicates that a bill based on the periodical billing data will be issued on the 30th of every month.
  • the billing data storage unit 122 stores the addressee business operator of each of the plurality of billing data indicating the billing content of the issued bill, one or more items to be billed in each of the plurality of billing data, and the issuance of each of the plurality of billing data.
  • FIG. 4 is a diagram showing an example of the data structure of billing history information stored in the billing data storage unit 122. As shown in FIG. The billing history information stores the bill number, the billing date, the billing address, and the item billed on the bill in association with each other.
  • the invoice number is information that identifies the invoice.
  • the destination includes, for example, the business number and business name of the destination business.
  • Items include, for example, a plurality of items to be billed on the invoice and the quantity of each item. Items in the billing history information may be further associated with item types, prices, account titles, and the like.
  • the model storage unit 123 stores a learned model that outputs information indicating whether or not it is periodic billing data when a business operator and an item are input.
  • the model storage unit 123 stores a trained model that has learned teacher data that associates information indicating the business operator and item included in the invoice data with a flag indicating whether the invoice data is regular billing data. do.
  • the business is the destination business name or the destination business number of the invoice.
  • the items are, for example, item names and item codes included in the billing data.
  • the model storage unit 123 may store a learned model that has learned teacher data further associated with the quantity of items included in the invoice data. Furthermore, the model storage unit 123 may store a learned model that has learned teacher data further associated with the date of issue of billing data.
  • the control unit 13 is, for example, a CPU (Central Processing Unit).
  • the control unit 13 functions as an identification unit 131 , a determination unit 132 , an output unit 133 and an acquisition unit 134 by executing control programs stored in the storage unit 12 .
  • the identifying unit 131 identifies periodic billing data that indicates billing details in bills issued periodically.
  • the identification unit 131 can identify periodic billing data by various methods. As an example, the identification unit 131 identifies billing data including the destination business operator and one or more items stored in the periodic data storage unit 121 as periodic billing data.
  • the specifying unit 131 determines a plurality of intervals between billing data with close issuing dates among three or more mutual billing data intervals in which the destination business operator and the item to be billed match. Identify recurring billing data based on relationships.
  • the identification unit 131 acquires billing data included in the billing history information, and obtains billing data billing the same destination business operator for the same item. Then, when there are three or more invoice data items acquired, the identification unit 131 sorts the invoice data in order of issue date. Then, the specifying unit 131 calculates the difference in the issue date between each invoice data and the invoice data issued immediately before or after the invoice data.
  • the identifying unit 131 identifies billing data acquired when the calculated difference between the respective issuing dates has a predetermined relationship as periodic billing data.
  • the predetermined relationship is, for example, a case where the interval between issue dates is the same period (7 days, 1 month, etc.).
  • the identifying unit 131 may identify three or more pieces of billing data as periodic billing data when the variations in the intervals are within a predetermined range. That is, the predetermined relationship is, for example, the case where the intervals between the publication dates are within one month, every other month, or within a quarter. Since the interval between issue dates may increase or decrease due to the influence of holidays, etc., even if the interval between issue dates is within 40 days, 70 days, or 100 days, which is obtained by adding 10 days to the predetermined number of days, the predetermined relationship may be set. good.
  • a lower limit may be set for the interval between issue dates.
  • the lower limit is, for example, 20 days, 50 days, 80 days, or the like. That is, when the interval between issue dates ranges from 20 days to 40 days, for example, the identifying unit 131 identifies the acquired billing data as periodic billing data.
  • the identification unit 131 inputs the destination business operator of each of the plurality of billing data indicating the billing content of the issued bill and the one or more items to be billed in each of the plurality of billing data into the learned model. If the information output from the model indicates periodic billing data, billing data corresponding to the destination business operator and one or more items input to the learned model may be identified as periodic billing data.
  • the identifying unit 131 acquires a trained model from the model storage unit 123.
  • the specifying unit 131 inputs the destination business operator in the billing data and the items to be billed in the billing data into the learned model.
  • the identification unit 131 may further input the quantity of items in the billing data and the date of issue of the bill to the trained model.
  • the output from the learned model indicates that the input billing data is periodical billing data
  • the input billing data is identified as periodical billing data.
  • the identification unit 131 identifies the periodic billing data using the trained model of the periodic billing data, thereby making it possible to identify the periodic billing data even when the determination rule cannot be specified in advance.
  • the identifying unit 131 may identify, as periodic billing data, billing data that includes the destination business operator and one or more items described in the order form data or contract data regarding goods or services that are regularly delivered.
  • the specifying unit 131 refers to order form data stored in the storage unit 12, and specifies periodic billing data based on information included in the order form data.
  • the identification unit 131 may identify periodic billing data based on information included in the order form data when the order content in the order form data indicates that the product or service is to be delivered periodically. good.
  • the determination unit 132 determines whether or not the invoices to be issued periodically have been issued. As an example, the determination unit 132 determines the second timing for creating or issuing the invoice after the first timing for creating or issuing the invoice based on the periodic billing data specified by the specifying unit 131 and after the first timing. It is determined whether or not the invoice has been issued before the 2nd timing.
  • the first timing is, for example, the timing predetermined as the timing at which the invoice should be created or issued, or the timing indicated by the issuance timing stored in association with the periodical data.
  • the second timing is determined, for example, by adding the issue cycle associated with the periodic data to the determined first timing or issue date associated with the periodic data.
  • the determining unit 132 determines that, when there is a bill issued to the destination business operator corresponding to the periodic billing data within a predetermined period of time with respect to the first timing, the bill based on the periodic billing data is issued. Identify as issued. This predetermined range is determined based on the periodic billing cycle, and is, for example, one month.
  • the determining unit 132 searches the billing history information by using the destination business operator and one or more items included in the periodic data as keys, and searches the billing history information one month before the first timing. If there is a bill issued later, it is determined that the bill to be issued periodically has been issued.
  • the determining unit 132 searches the billing history information using the destination business operator and the one or more items included in the periodic data as keys, and finds the bill with the latest issue date among the one or more billing data extracted from the billing history information. It may be determined whether or not the periodical billing data has been issued based on whether the date of issue of the data is within a predetermined range from the time of retrieval. This predetermined range is, for example, a period that is longer than the issue cycle of regular billing data and shorter than twice the issue cycle. If the issue date of the latest billing data is within a predetermined range from the time of retrieval, the determination unit 132 determines that the periodical billing data to be issued has already been issued, and issues the latest billing data. If the date is earlier than the predetermined range with respect to the retrieved time, it is determined that the periodic billing data to be issued has not been issued.
  • the predetermined range is, for example, 35 days.
  • the determination unit 132 determines that a regular bill that should be issued within 35 days from the time of issuance of the previous bill has already been issued, and a period longer than 35 days from the time of issuance of the previous bill. has passed, it is determined that the periodic invoice has not been issued. In this case, the determining unit 132 can identify that the periodic invoice has not been issued without identifying the first timing.
  • the output unit 133 outputs warning information when the determination unit 132 determines that the invoice based on the periodic billing data has not been issued. As an example, the output unit 133 displays on the information terminal 2 a warning screen indicating that the bill based on the periodic billing data has not been issued. The output unit 133 may transmit a message including warning information to the user of the data processing device 1 .
  • the data processing device 1 may specify periodic billing data based on, for example, order data or contract data. By configuring the data processing device 1 in this way, the business operator who issues the invoice does not need to register the periodic billing data, which enhances the convenience.
  • the acquisition unit 134 acquires various data. For example, the acquisition unit 134 acquires, from the external device or the storage unit 12, purchase order data or a contract in which a destination business operator, one or more items to be billed, and a periodical delivery date or periodical billing date are described. Get document data.
  • FIG. 5 is a diagram showing an example of order form data acquired by the acquiring unit 134. As shown in FIG.
  • the order form data includes the destination business name, destination business number, order date, business name, business number, address or telephone number of the ordering business, product name of the product or service to be ordered, Includes quantity and delivery date.
  • the data acquired by the acquisition unit 134 is contract data or written agreement data, it may include information indicating payment methods such as payment dates, payment cycles, account numbers, etc., in addition to these pieces of information.
  • Acquisition unit 134 stores the acquired data in storage unit 12 .
  • 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 timing for performing the preset determination process arrives.
  • the identification unit 131 acquires billing history information (S01).
  • the identification unit 131 acquires the regular data stored in the regular data storage unit 121 (S02).
  • the identifying unit 131 identifies periodic billing data from the billing history information (S03).
  • the identification unit 131 identifies periodic billing data from the periodic data (S04).
  • the determination unit 132 determines whether or not a bill based on the specified periodic billing data has been issued (S05).
  • the output unit 133 determines whether or not there is an unissued bill among the bills based on the identified periodic billing data (S06). If there is no unissued bill (NO in S06), data processor 1 terminates the process. If there is an unissued bill (YES in S06), output unit 133 outputs warning information (S07), and data processor 1 terminates the process.
  • the identification unit 131 for identifying periodic billing data indicating the billing content of a bill issued periodically, and the bill based on the periodic billing data identified by the identification unit 131. After the first timing of creating or issuing the invoice and before the second timing of creating or issuing the invoice after the first timing, it is determined whether or not the invoice has been issued. It has a determination unit 132 and an output unit 133 that outputs warning information when the determination unit 132 determines that the invoice based on the periodic billing data has not been issued. With such a configuration, the data processing device 1 can provide information for preventing billing omissions for continuous transactions.

Landscapes

  • Business, Economics & Management (AREA)
  • Development Economics (AREA)
  • Accounting & Taxation (AREA)
  • Economics (AREA)
  • Finance (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (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 determines whether bills, which are to regularly issued, have been issued. This data processing device comprises: an identification unit 131 that identifies regular billing data indicative of billing details in bills which are to be issued regularly; a determination unit 132 that determines, after a first timing to create or issue a bill based on the regular billing data identified by the identification unit 131 and before a second timing to create or issue the bill after the first timing, whether the bill has already been issued; and an output unit 133 that outputs warning information upon determination by the determination unit 132 that the bill based on the regular billing data has not yet been issued.

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.
国際公開第２０１７／７３１０２号WO2017/73102
　特許文献１に記載の請求書管理システムにおいては、請求書を発行するために担当者による処理を必要としている。請求書の発行業務においては大量の請求データを処理する必要があり、人為的なミスによる請求書の発行漏れを防止する必要がある。 The invoice management system described in Patent Document 1 requires processing by the person in charge in order to issue the invoice. In the billing business, it is necessary to process a large amount of billing data, and it is necessary to prevent omission of billing due to human error.
　そこで、本発明はこれらの点に鑑みてなされたものであり、継続的にされる取引の請求漏れを防止するための情報を提供することを目的とする。 Therefore, the present invention has been made in view of these points, and aims to provide information for preventing billing omissions for continuous transactions.
　本発明の第１の態様のデータ処理装置においては、定期的に発行される請求書における請求内容を示す定期請求データを特定する特定部と、前記特定部が特定した前記定期請求データに基づく請求書を作成又は発行する第１タイミングよりも後であり、かつ前記第１タイミングの後に該請求書を作成又は発行する第２タイミングよりも前に、該請求書が発行済であるか否かを判定する判定部と、前記定期請求データに基づく請求書が発行済でないと前記判定部が判定した場合に警告情報を出力する出力部と、を有する。 In the data processing apparatus according to the first aspect of the present invention, there are provided: a specifying unit for specifying periodic billing data indicating the billing content of a bill issued periodically; After the first timing of creating or issuing the invoice and before the second timing of creating or issuing the invoice after the first timing, it is determined whether or not the invoice has been issued. and an output unit that outputs warning information when the determination unit determines that the invoice based on the regular billing data has not been issued.
　前記定期請求データの宛先事業者と前記定期請求データにおける請求対象の１以上の品目とを関連付けて記憶する定期データ記憶部をさらに有し、前記特定部は、前記定期データ記憶部に記憶された前記宛先事業者と前記１以上の品目とを含む請求データを前記定期請求データとして特定してもよい。 a periodic data storage unit that associates and stores the destination business operator of the periodic billing data and the one or more items to be billed in the periodic billing data, wherein the specifying unit stores the items stored in the periodic data storage unit; Billing data including the destination business operator and the one or more items may be identified as the periodic billing data.
　前記定期データ記憶部は、前記宛先事業者及び前記１以上の品目に関連付けて、前記請求書の発行時期をさらに記憶し、前記判定部は、前記発行時期に基づいて決定した前記第１タイミングよりも後であり、かつ前記第２タイミングよりも前に、該請求書が発行済であるか否かを判定してもよい。 The periodic data storage unit further stores the timing of issuing the bill in association with the destination business operator and the one or more items, and the determination unit stores the timing of issuing the invoice from the first timing determined based on the timing of issuing the bill. It may be determined whether or not the invoice has been issued later than the second timing and before the second timing.
　宛先事業者と、請求対象の１以上の品目と、定期的な納品日又は定期的な請求日とが記載された注文書データ又は契約書データを取得する取得部をさらに有し、前記特定部は、前記注文書データ又は前記契約書データに記載された前記宛先事業者と前記１以上の品目とを含む請求データを前記定期請求データとして特定してもよい。 an acquisition unit that acquires purchase order data or contract data that includes a destination business operator, one or more items to be billed, and a periodic delivery date or a periodic billing date; may specify, as the periodic billing data, billing data including the destination business operator and the one or more items described in the purchase order data or the contract data.
　発行済みの前記請求書における請求内容を示す複数の請求データそれぞれの宛先事業者と、前記複数の請求データそれぞれにおける請求対象の１以上の品目と、前記複数の請求データそれぞれの発行日と、を関連付けた請求履歴情報を記憶する請求データ記憶部をさらに有し、前記判定部は、定期データに含まれる前記宛先事業者と前記１以上の品目とをキーとして前記請求履歴情報を検索し、前記請求履歴情報から抽出された１以上の前記請求データのうち発行日が最新である前記請求データの発行日が検索時から所定の範囲以内であるかに基づいて前記定期請求データが発行済みであるか否かを判定してもよい。 A destination business operator for each of a plurality of billing data indicating billing content in the issued bill, one or more items to be billed in each of the plurality of billing data, and an issue date of each of the plurality of billing data. Further comprising a billing data storage unit for storing associated billing history information, the determination unit searches the billing history information using the destination business operator and the one or more items included in the periodic data as keys, and searches for the billing history information. The periodical billing data has been issued based on whether the billing data having the latest issue date among the one or more billing data extracted from the billing history information is within a predetermined range from the time of retrieval. It may be determined whether
　発行済みの前記請求書における請求内容を示す複数の請求データそれぞれの宛先事業者と、前記複数の請求データそれぞれにおける請求対象の１以上の品目と、前記複数の請求データそれぞれの発行日と、を関連付けた請求履歴情報を記憶する請求データ記憶部をさらに有し、前記特定部は、前記請求履歴情報において、前記宛先事業者と前記請求対象の品目とが一致する３以上の前記請求データ相互の発行日の間隔のうち、発行日が近い前記請求データ同士の複数の前記間隔の関係に基づいて前記定期請求データを特定してもよい。 A destination business operator for each of a plurality of billing data indicating billing content in the issued bill, one or more items to be billed in each of the plurality of billing data, and an issue date of each of the plurality of billing data. further comprising a billing data storage unit for storing associated billing history information, wherein the specifying unit performs mutual identification of three or more of the billing data in which the destination business operator and the item to be billed match in the billing history information; The periodical billing data may be specified based on a plurality of the intervals between the billing data having the closest issuing dates among the intervals of the issuing dates.
　前記特定部は、前記複数の間隔のばらつきが所定の範囲以内である場合に、前記３以上の請求データを前記定期請求データとして特定してもよい。 The identifying unit may identify the three or more pieces of billing data as the regular billing data when the variations in the plurality of intervals are within a predetermined range.
　事業者と品目とを入力すると前記定期請求データであるか否かを示す情報を出力する学習済みモデルを記憶する記憶部をさらに有し、前記特定部は、発行済みの前記請求書における請求内容を示す複数の請求データそれぞれの宛先事業者と、前記複数の請求データそれぞれにおける請求対象の１以上の品目とを前記学習済みモデルに入力し、前記学習済みモデルから出力された情報が前記定期請求データであることを示している場合に、前記学習済みモデルに入力した前記宛先事業者及び前記１以上の品目に対応する請求データを前記定期請求データとして特定してもよい。 Further comprising a storage unit that stores a learned model that outputs information indicating whether or not it is the regular billing data when a business operator and an item are entered, wherein the specifying unit stores the billing content of the bill that has been issued. and one or more items to be billed in each of the plurality of billing data are input into the learned model, and the information output from the trained model is used for the periodic billing data, the billing data corresponding to the destination business operator and the one or more items input to the trained model may be identified as the periodic billing data.
　本発明の第２の態様のデータ処理方法においては、コンピュータが実行する、定期的に発行される請求書における請求内容を示す定期請求データを特定するステップと、前記特定するステップにおいて特定された前記定期請求データに基づく請求書を作成又は発行する第１タイミングよりも後であり、かつ前記第１タイミングの後に該請求書を作成又は発行する第２タイミングよりも前に、該請求書が発行済であるか否かを判定するステップと、前記定期請求データに基づく請求書が発行済でないと前記判定するステップにおいて判定された場合に警告情報を出力する出力するステップと、を有する。 In the data processing method according to the second aspect of the present invention, there are provided a computer-executed step of identifying periodic billing data indicating billing content in a periodically issued bill; After the first timing of creating or issuing an invoice based on periodic billing data and before the second timing of creating or issuing the invoice after the first timing, the invoice has been issued. and outputting warning information when it is determined in the determining step that the bill based on the periodic billing data has not been issued.
　本発明の第３の態様のプログラムにおいては、コンピュータに実行させる、定期的に発行される請求書における請求内容を示す定期請求データを特定するステップと、前記特定するステップにおいて特定された前記定期請求データに基づく請求書を作成又は発行する第１タイミングよりも後であり、かつ前記第１タイミングの後に該請求書を作成又は発行する第２タイミングよりも前に、該請求書が発行済であるか否かを判定するステップと、前記定期請求データに基づく請求書が発行済でないと前記判定するステップにおいて判定された場合に警告情報を出力する出力するステップと、を有する。 In the program according to the third aspect of the present invention, a computer executes a step of identifying periodic billing data indicating the billing content of a bill issued periodically; The invoice has been issued after a first timing of creating or issuing an invoice based on data and before a second timing of creating or issuing the invoice after the first timing. and outputting warning information when it is determined in the determining step that the bill based on the periodic billing data has not been issued.
　本発明によれば、継続的にされる取引の請求漏れを防止するための情報を提供することができるという効果を奏する。 According to the present invention, it is possible to provide information for preventing billing omissions for continuous transactions.
実施の形態に係るデータ処理システムＳの概要を説明する図である。It is a figure explaining the outline|summary of the data processing system S which concerns on embodiment. データ処理装置１の構成を示すブロック図である。2 is a block diagram showing the configuration of the data processing device 1; FIG. 定期データ記憶部１２１が記憶する定期データのデータ構造の一例を示す図である。4 is a diagram showing an example of a data structure of regular data stored in a regular data storage unit 121; FIG. 請求データ記憶部１２２が記憶する請求履歴情報のデータ構造の一例を示す図である。4 is a diagram showing an example data structure of billing history information stored in a billing data storage unit 122. FIG. 取得部１３４が取得する注文書データの一例を示す図である。6 is a diagram showing an example of order form data acquired by an acquisition unit 134; FIG. データ処理装置１における処理の流れを示すフローチャートである。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 that generates invoice data and exchanges invoice data. The invoice data is electronic invoice data. A data processing system S has a data processing device 1 and an information terminal 2 .
　データ処理装置１は、請求書データを生成し、生成した請求書データを請求書の宛先の事業者が使用する会計処理装置（不図示）に送信する装置である。データ処理装置１は、定期的に発行される請求書を自動的に発行する。データ処理装置１は、例えばサーバである。 The data processing device 1 is a device that generates bill data and transmits the generated bill data to an accounting processing device (not shown) used by the business operator to whom the bill is addressed. The data processing device 1 automatically issues a bill issued periodically. The data processing device 1 is, for example, a server.
　情報端末２は、データ処理装置１が出力する情報を表示し、データ処理装置１を操作するための装置である。情報端末２は、タブレット、スマートフォン、パーソナルコンピュータ等である。 The information terminal 2 is a device for displaying information output by the data processing device 1 and for operating the data processing device 1 . The information terminal 2 is a tablet, a smart phone, a personal computer, or the like.
　データ処理システムＳが警告情報を出力する流れについて説明する。データ処理装置１は、定期請求データを特定する（図１における（１））。一例として、データ処理装置１は、予め登録された定期データに基づいて定期請求データを特定する。定期データは定期的に発行される請求書の宛先事業者と請求書における請求対象の品目とを関連付けたデータである。 The flow of the data processing system S outputting warning information will be explained. The data processing device 1 identifies periodic billing data ((1) in FIG. 1). As an example, the data processing device 1 identifies periodic billing data based on pre-registered periodic data. Periodical data is data that associates a business to which a bill issued periodically is addressed and an item to be billed on the bill.
　データ処理装置１は、特定した定期請求データに基づく請求書が発行済みか否かを判定する（図１における（２））。データ処理装置１は、特定した定期請求データに基づく請求書が発行済みでない場合、警告情報を情報端末２に出力する（図１における（３））。 The data processing device 1 determines whether or not a bill based on the identified periodic billing data has been issued ((2) in FIG. 1). The data processing device 1 outputs warning information to the information terminal 2 when a bill based on the specified periodic billing data has not been issued ((3) in FIG. 1).
＜データ処理装置１の構成＞
　図２は、データ処理装置１の構成を示すブロック図である。データ処理装置１は、通信部１１、記憶部１２及び制御部１３を有する。記憶部１２は、定期データ記憶部１２１、請求データ記憶部１２２及びモデル記憶部１２３を有する。制御部１３は、特定部１３１、判定部１３２、出力部１３３及び取得部１３４を有する。 <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 storage unit 12 has a regular data storage unit 121 , a billing data storage unit 122 and a model storage unit 123 . The control unit 13 has an identification unit 131 , a determination unit 132 , an output unit 133 and an acquisition unit 134 .
　通信部１１は、ネットワークを介して情報端末２と通信するための通信インターフェースである。記憶部１２は、例えば、ＲＯＭ（Read Only Memory）、ＲＡＭ（Random Access Memory）、ＳＳＤ（Solid State Drive）、ハードディスク等の記憶媒体である。記憶部１２は、制御部１３を機能させるための各種のプログラムを記憶する。 The communication unit 11 is a communication interface for communicating with the information terminal 2 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.
　定期データ記憶部１２１は、定期請求データの宛先事業者と定期請求データにおける請求対象の１以上の品目とを関連付けて記憶する。図３は、定期データ記憶部１２１が記憶する定期データのデータ構造の一例を示す図である。図３に示す定期データにおいては、定期データＩＤ（Identification）、定期請求データの宛先及び定期請求データの品目を関連付けて記憶している。定期データＩＤは登録された定期請求データを識別する識別子である。定期請求データの宛先は、例えば宛先事業者の事業者番号又は事業者名の少なくともいずれかである。定期請求データの品目は、例えば、定期請求データにおいて請求対象となる１以上の商品又は役務の名称である。定期請求データの品目には、商品又は役務それぞれの数量が含まれていてもよい。定期請求データの品目においては、品目の種類、価格や勘定科目などがさらに関連付けられていてもよい。 The regular data storage unit 121 associates and stores the destination business operator of the regular billing data with one or more items to be billed in the regular billing data. FIG. 3 is a diagram showing an example of the data structure of regular data stored in the regular data storage unit 121. As shown in FIG. In the regular data shown in FIG. 3, the regular data ID (Identification), the destination of the regular billing data, and the item of the regular billing data are stored in association with each other. The regular data ID is an identifier for identifying registered regular billing data. The destination of periodic billing data is, for example, at least one of the business number or business name of the destination business. The item of periodic billing data is, for example, the name of one or more goods or services to be billed in the periodic billing data. Items of recurring billing data may include quantities of each product or service. Items of periodic billing data may be further associated with item types, prices, account titles, and the like.
　定期データ記憶部１２１は、宛先事業者及び１以上の品目に関連付けて、請求書の発行時期をさらに記憶してもよい。図３に示す定期データにおいては、定期請求データに関連付けて定期的に請求を行う請求時期が記憶されている。請求時期は一例として、請求日と周期を含む。請求日は請求書の発行時期が到来した請求書を発行する日である。周期は、請求書を発行する周期である。例えば、定期データが示す請求時期が、請求日が３０日で周期が毎月であることを示している場合、定期データは、毎月３０日に定期請求データに基づく請求書を発行することを示す。 The periodic data storage unit 121 may further store the timing of issuing the invoice in association with the destination business operator and one or more items. In the periodical data shown in FIG. 3, billing times for periodic billing are stored in association with periodical billing data. The billing period includes, for example, the billing date and cycle. The billing date is the date on which the invoice is issued when the time for issuing the invoice has arrived. A cycle is a cycle of issuing a bill. For example, if the billing period indicated by the periodical data indicates that the billing date is every 30th and the cycle is every month, the periodical data indicates that a bill based on the periodical billing data will be issued on the 30th of every month.
　請求データ記憶部１２２は、発行済みの請求書における請求内容を示す複数の請求データそれぞれの宛先事業者と、複数の請求データそれぞれにおける請求対象の１以上の品目と、複数の請求データそれぞれの発行日と、を関連付けた請求履歴情報を記憶する。図４は、請求データ記憶部１２２が記憶する請求履歴情報のデータ構造の一例を示す図である。請求履歴情報には請求書番号、請求書の発行日、請求書の宛先及び請求書において請求される品目が関連付けて記憶されている。 The billing data storage unit 122 stores the addressee business operator of each of the plurality of billing data indicating the billing content of the issued bill, one or more items to be billed in each of the plurality of billing data, and the issuance of each of the plurality of billing data. Store billing history information associated with date. FIG. 4 is a diagram showing an example of the data structure of billing history information stored in the billing data storage unit 122. As shown in FIG. The billing history information stores the bill number, the billing date, the billing address, and the item billed on the bill in association with each other.
　請求書番号は請求書を識別する情報である。宛先は一例として宛先事業者の事業者番号と事業者名を含む。品目は、一例として、請求書において請求対象となる複数の品目と、それぞれの品目の数量を含む。請求履歴情報の品目においては、品目の種類、価格や勘定科目などがさらに関連付けられていてもよい。 The invoice number is information that identifies the invoice. The destination includes, for example, the business number and business name of the destination business. Items include, for example, a plurality of items to be billed on the invoice and the quantity of each item. Items in the billing history information may be further associated with item types, prices, account titles, and the like.
　モデル記憶部１２３は、事業者と品目とが入力されると定期請求データであるか否かを示す情報を出力する学習済みモデルを記憶する。モデル記憶部１２３は、請求書データに含まれる事業者及び品目を示す情報と、請求書データが定期請求データであるか否かを示すフラグとを関連付けた教師データを学習した学習済みモデルを記憶する。事業者は、請求書の宛先事業者名又は宛先事業者番号である。品目は例えば、請求データに含まれる品目名や品目コードである。 The model storage unit 123 stores a learned model that outputs information indicating whether or not it is periodic billing data when a business operator and an item are input. The model storage unit 123 stores a trained model that has learned teacher data that associates information indicating the business operator and item included in the invoice data with a flag indicating whether the invoice data is regular billing data. do. The business is the destination business name or the destination business number of the invoice. The items are, for example, item names and item codes included in the billing data.
　モデル記憶部１２３は、請求書データに含まれる品目の数量をさらに関連付けた教師データを学習した学習済みモデルを記憶してもよい。さらに、モデル記憶部１２３は、請求データの発行日をさらに関連付けた教師データを学習した学習済みモデルを記憶してもよい。 The model storage unit 123 may store a learned model that has learned teacher data further associated with the quantity of items included in the invoice data. Furthermore, the model storage unit 123 may store a learned model that has learned teacher data further associated with the date of issue of billing data.
　制御部１３は、例えばＣＰＵ（Central Processing Unit）である。制御部１３は、記憶部１２に記憶されている制御プログラムを実行することにより、特定部１３１、判定部１３２、出力部１３３及び取得部１３４として機能する。 The control unit 13 is, for example, a CPU (Central Processing Unit). The control unit 13 functions as an identification unit 131 , a determination unit 132 , an output unit 133 and an acquisition unit 134 by executing control programs stored in the storage unit 12 .
　特定部１３１は、定期的に発行される請求書における請求内容を示す定期請求データを特定する。特定部１３１は、定期請求データを様々な方法により特定することができる。一例として、特定部１３１は、定期データ記憶部１２１に記憶された宛先事業者と１以上の品目とを含む請求データを定期請求データとして特定する。 The identifying unit 131 identifies periodic billing data that indicates billing details in bills issued periodically. The identification unit 131 can identify periodic billing data by various methods. As an example, the identification unit 131 identifies billing data including the destination business operator and one or more items stored in the periodic data storage unit 121 as periodic billing data.
　特定部１３１は、例えば、請求履歴情報において、宛先事業者と請求対象の品目とが一致する３以上の請求データ相互の発行日の間隔のうち、発行日が近い請求データ同士の複数の間隔の関係に基づいて定期請求データを特定する。一例として、特定部１３１は、請求履歴情報に含まれる請求データを取得し、同一の宛先事業者に対して同一の品目について請求している請求書データを取得する。そして、特定部１３１は、取得した請求書データが３以上ある場合、請求書データを発行日の順にソートする。そして、特定部１３１は、それぞれの請求書データと、その請求書データの直前又は直後に発行された請求書データと、の発行日の差分を算出する。特定部１３１は、算出したそれぞれの発行日の差分が所定の関係にある場合に取得した請求データを定期請求データとして特定する。所定の関係は、一例として、発行日の間隔が同じ期間（７日、１か月等）となる場合である。 For example, in the billing history information, the specifying unit 131 determines a plurality of intervals between billing data with close issuing dates among three or more mutual billing data intervals in which the destination business operator and the item to be billed match. Identify recurring billing data based on relationships. As an example, the identification unit 131 acquires billing data included in the billing history information, and obtains billing data billing the same destination business operator for the same item. Then, when there are three or more invoice data items acquired, the identification unit 131 sorts the invoice data in order of issue date. Then, the specifying unit 131 calculates the difference in the issue date between each invoice data and the invoice data issued immediately before or after the invoice data. The identifying unit 131 identifies billing data acquired when the calculated difference between the respective issuing dates has a predetermined relationship as periodic billing data. The predetermined relationship is, for example, a case where the interval between issue dates is the same period (7 days, 1 month, etc.).
　特定部１３１は、複数の間隔のばらつきが所定の範囲以内である場合に、３以上の請求データを定期請求データとして特定してもよい。すなわち、所定の関係は、例えば、発行日の間隔が１か月、隔月、四半期以内となる場合である。休日等の影響で発行日の間隔が増減する場合があるため、所定の日数として例えば１０日を加算した４０日、７０日、１００日以内に発行日の間隔がなる場合を所定の関係としてもよい。 The identifying unit 131 may identify three or more pieces of billing data as periodic billing data when the variations in the intervals are within a predetermined range. That is, the predetermined relationship is, for example, the case where the intervals between the publication dates are within one month, every other month, or within a quarter. Since the interval between issue dates may increase or decrease due to the influence of holidays, etc., even if the interval between issue dates is within 40 days, 70 days, or 100 days, which is obtained by adding 10 days to the predetermined number of days, the predetermined relationship may be set. good.
　発行日の間隔は下限値が設定されてもよい。下限値は例えば２０日、５０日、８０日等である。すなわち、発行日の間隔が一例として、２０日から４０日の範囲となる場合に、特定部１３１は、取得した請求データを定期請求データとして特定する。 A lower limit may be set for the interval between issue dates. The lower limit is, for example, 20 days, 50 days, 80 days, or the like. That is, when the interval between issue dates ranges from 20 days to 40 days, for example, the identifying unit 131 identifies the acquired billing data as periodic billing data.
　特定部１３１は、発行済みの請求書における請求内容を示す複数の請求データそれぞれの宛先事業者と、複数の請求データそれぞれにおける請求対象の１以上の品目とを学習済みモデルに入力し、学習済みモデルから出力された情報が定期請求データであることを示している場合に、学習済みモデルに入力した宛先事業者及び１以上の品目に対応する請求データを定期請求データとして特定してもよい。 The identification unit 131 inputs the destination business operator of each of the plurality of billing data indicating the billing content of the issued bill and the one or more items to be billed in each of the plurality of billing data into the learned model. If the information output from the model indicates periodic billing data, billing data corresponding to the destination business operator and one or more items input to the learned model may be identified as periodic billing data.
　特定部１３１は、モデル記憶部１２３から学習済みモデルを取得する。特定部１３１は、請求データにおける宛先事業者と請求データにおける請求対象の品目とを学習済みモデルに入力する。特定部１３１は、請求データにおける品目の数量や請求書の発行日をさらに学習済みモデルに入力してもよい。そして、学習済みモデルからの出力が入力した請求データが定期請求データであることを示す場合に入力した請求データを定期請求データとして特定する。特定部１３１が、定期請求データ学習済みモデルを使用して定期請求データを特定することで、予め判定ルールを指定できない場合においても定期請求データを特定することが可能となる。 The identifying unit 131 acquires a trained model from the model storage unit 123. The specifying unit 131 inputs the destination business operator in the billing data and the items to be billed in the billing data into the learned model. The identification unit 131 may further input the quantity of items in the billing data and the date of issue of the bill to the trained model. Then, when the output from the learned model indicates that the input billing data is periodical billing data, the input billing data is identified as periodical billing data. The identification unit 131 identifies the periodic billing data using the trained model of the periodic billing data, thereby making it possible to identify the periodic billing data even when the determination rule cannot be specified in advance.
　特定部１３１は、定期的に納品される商品又はサービスに関する注文書データ又は契約書データに記載された宛先事業者と１以上の品目とを含む請求データを定期請求データとして特定してもよい。特定部１３１は、例えば、記憶部１２に記憶された注文書データを参照し、注文書データに含まれる情報に基づいて定期請求データを特定する。特定部１３１は、注文書データにおける注文内容が、定期的に納品される商品又はサービスであることを示している場合に、注文書データに含まれる情報に基づいて定期請求データを特定してもよい。 The identifying unit 131 may identify, as periodic billing data, billing data that includes the destination business operator and one or more items described in the order form data or contract data regarding goods or services that are regularly delivered. The specifying unit 131, for example, refers to order form data stored in the storage unit 12, and specifies periodic billing data based on information included in the order form data. The identification unit 131 may identify periodic billing data based on information included in the order form data when the order content in the order form data indicates that the product or service is to be delivered periodically. good.
　判定部１３２は、定期的に発行するべき請求書が発行済であるか否かを判定する。一例として、判定部１３２は、特定部１３１が特定した定期請求データに基づく請求書を作成又は発行する第１タイミングよりも後であり、かつ第１タイミングの後に該請求書を作成又は発行する第２タイミングよりも前に、該請求書が発行済であるか否かを判定する。第１タイミングは、例えば請求書を作成若しくは発行するべきタイミングとして予め定められたタイミング、又は定期データに関連付けて記憶された発行時期が示すタイミング等である。第２タイミングは、例えば、決定された第１タイミング又は定期データに関連付けられた発行日に定期データに関連付けられた発行周期を加算して決定される。 The determination unit 132 determines whether or not the invoices to be issued periodically have been issued. As an example, the determination unit 132 determines the second timing for creating or issuing the invoice after the first timing for creating or issuing the invoice based on the periodic billing data specified by the specifying unit 131 and after the first timing. It is determined whether or not the invoice has been issued before the 2nd timing. The first timing is, for example, the timing predetermined as the timing at which the invoice should be created or issued, or the timing indicated by the issuance timing stored in association with the periodical data. The second timing is determined, for example, by adding the issue cycle associated with the periodic data to the determined first timing or issue date associated with the periodic data.
　一例として、判定部１３２は、第１タイミングに対して所定の範囲の期間内に、定期請求データに対応する宛先事業者に発行された請求書がある場合に、定期請求データに基づく請求書が発行済であると特定する。この所定の範囲は、定期請求書の発行周期に基づいて定められており、例えば１ヵ月である。 As an example, the determining unit 132 determines that, when there is a bill issued to the destination business operator corresponding to the periodic billing data within a predetermined period of time with respect to the first timing, the bill based on the periodic billing data is issued. Identify as issued. This predetermined range is determined based on the periodic billing cycle, and is, for example, one month.
　判定部１３２は、例えば請求書の発行周期が１ヵ月である場合、定期データに含まれる宛先事業者と１以上の品目とをキーとして請求履歴情報を検索し、第１タイミングの１ヵ月前よりも後に発行された請求書があった場合に、定期的に発行するべき請求書が発行済であると判定する。 For example, if the invoice issuance cycle is one month, the determining unit 132 searches the billing history information by using the destination business operator and one or more items included in the periodic data as keys, and searches the billing history information one month before the first timing. If there is a bill issued later, it is determined that the bill to be issued periodically has been issued.
　判定部１３２は、定期データに含まれる宛先事業者と１以上の品目とをキーとして請求履歴情報を検索し、請求履歴情報から抽出された１以上の請求データのうち発行日が最新である請求データの発行日が検索時から所定の範囲以内であるかに基づいて定期請求データが発行済みであるか否かを判定してもよい。この所定の範囲は、例えば、定期請求データの発行周期よりも長く、発行周期の２倍よりも短い期間である。判定部１３２は、最新の請求データの発行日が、検索した時点に対して所定の範囲以内である場合、発行されるべき定期請求データが発行済みであると判定し、最新の請求データの発行日が、検索した時点に対して所定の範囲よりも前である場合、発行されるべき定期請求データが発行済でないと判定する。 The determining unit 132 searches the billing history information using the destination business operator and the one or more items included in the periodic data as keys, and finds the bill with the latest issue date among the one or more billing data extracted from the billing history information. It may be determined whether or not the periodical billing data has been issued based on whether the date of issue of the data is within a predetermined range from the time of retrieval. This predetermined range is, for example, a period that is longer than the issue cycle of regular billing data and shorter than twice the issue cycle. If the issue date of the latest billing data is within a predetermined range from the time of retrieval, the determination unit 132 determines that the periodical billing data to be issued has already been issued, and issues the latest billing data. If the date is earlier than the predetermined range with respect to the retrieved time, it is determined that the periodic billing data to be issued has not been issued.
　発行周期が１ヵ月である場合、所定の範囲は、例えば３５日である。この場合、判定部１３２は、前回の請求書の発行時点より３５日以内であれば発行されるべき定期請求書は発行済みと判定し、前回の請求書の発行時点より３５日よりも長い期間が経過していれば定期請求書が未発行であると判定する。この場合、判定部１３２は、第１タイミングを特定することなく定期請求書が未発行であることを特定することができる。 If the issue cycle is one month, the predetermined range is, for example, 35 days. In this case, the determination unit 132 determines that a regular bill that should be issued within 35 days from the time of issuance of the previous bill has already been issued, and a period longer than 35 days from the time of issuance of the previous bill. has passed, it is determined that the periodic invoice has not been issued. In this case, the determining unit 132 can identify that the periodic invoice has not been issued without identifying the first timing.
　出力部１３３は、定期請求データに基づく請求書が発行済でないと判定部１３２が判定した場合に警告情報を出力する。一例として、出力部１３３は、定期請求データに基づく請求書が発行済でないことを示す警告画面を情報端末２に表示する。出力部１３３は、警告情報を含むメッセージをデータ処理装置１のユーザに送信してもよい。 The output unit 133 outputs warning information when the determination unit 132 determines that the invoice based on the periodic billing data has not been issued. As an example, the output unit 133 displays on the information terminal 2 a warning screen indicating that the bill based on the periodic billing data has not been issued. The output unit 133 may transmit a message including warning information to the user of the data processing device 1 .
　データ処理装置１は、例えば注文データや契約データに基づいて定期請求データを特定してもよい。データ処理装置１がこのように構成されることで、請求書を発行する事業者においては定期的な請求データを登録する必要がなくなり、利便性が高くなる。 The data processing device 1 may specify periodic billing data based on, for example, order data or contract data. By configuring the data processing device 1 in this way, the business operator who issues the invoice does not need to register the periodic billing data, which enhances the convenience.
　取得部１３４は、各種のデータを取得する。取得部１３４は、例えば、外部装置又は記憶部１２から、宛先事業者と、請求対象の１以上の品目と、定期的な納品日又は定期的な請求日とが記載された注文書データ又は契約書データを取得する。図５は、取得部１３４が取得する注文書データの一例を示す図である。一例として、注文書データには、宛先事業者名、宛先事業者番号、注文日、発注する事業者の事業者名、事業者番号、住所又は電話番号、注文する商品又は役務の品名、注文する数量並びに納品日が含まれる。 The acquisition unit 134 acquires various data. For example, the acquisition unit 134 acquires, from the external device or the storage unit 12, purchase order data or a contract in which a destination business operator, one or more items to be billed, and a periodical delivery date or periodical billing date are described. Get document data. FIG. 5 is a diagram showing an example of order form data acquired by the acquiring unit 134. As shown in FIG. For example, the order form data includes the destination business name, destination business number, order date, business name, business number, address or telephone number of the ordering business, product name of the product or service to be ordered, Includes quantity and delivery date.
　なお、取得部１３４が取得するデータが契約書データ又は請書データである場合、これらの情報に加えて、支払い期日や支払い周期、口座番号等の支払い方法を示す情報が含まれていてもよい。取得部１３４は、取得したデータを記憶部１２に記憶する。 If the data acquired by the acquisition unit 134 is contract data or written agreement data, it may include information indicating payment methods such as payment dates, payment cycles, account numbers, etc., in addition to these pieces of information. Acquisition unit 134 stores the acquired data in storage unit 12 .
＜データ処理装置１における処理の流れ＞
　図６は、データ処理装置１における処理の流れを示すフローチャートである。図６におけるフローチャートは、予め設定された判定処理を行うタイミングが到来した時点から開始している。 <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 timing for performing the preset determination process arrives.
　特定部１３１は、請求履歴情報を取得する（Ｓ０１）。特定部１３１は、定期データ記憶部１２１に記憶された定期データを取得する（Ｓ０２）。 The identification unit 131 acquires billing history information (S01). The identification unit 131 acquires the regular data stored in the regular data storage unit 121 (S02).
　特定部１３１は、請求履歴情報から定期請求データを特定する（Ｓ０３）。特定部１３１は、定期データから定期請求データを特定する（Ｓ０４）。判定部１３２は、特定した定期請求データに基づく請求書が発行済みかを判定する（Ｓ０５）。 The identifying unit 131 identifies periodic billing data from the billing history information (S03). The identification unit 131 identifies periodic billing data from the periodic data (S04). The determination unit 132 determines whether or not a bill based on the specified periodic billing data has been issued (S05).
　出力部１３３は、特定した定期請求データに基づく請求書の中に未発行の請求書が存在するか否かを判定する（Ｓ０６）。未発行の請求書が存在しない場合（Ｓ０６におけるＮＯ）、データ処理装置１は処理を終了する。未発行の請求書が存在する場合（Ｓ０６におけるＹＥＳ）、出力部１３３は警告情報を出力し（Ｓ０７）、データ処理装置１は、処理を終了する。 The output unit 133 determines whether or not there is an unissued bill among the bills based on the identified periodic billing data (S06). If there is no unissued bill (NO in S06), data processor 1 terminates the process. If there is an unissued bill (YES in S06), output unit 133 outputs warning information (S07), and data processor 1 terminates the process.
［データ処理装置１の効果］
　以上説明したように、データ処理装置１においては、定期的に発行される請求書における請求内容を示す定期請求データを特定する特定部１３１と、特定部１３１が特定した定期請求データに基づく請求書を作成又は発行する第１タイミングよりも後であり、かつ第１タイミングの後に該請求書を作成又は発行する第２タイミングよりも前に、該請求書が発行済であるか否かを判定する判定部１３２と、定期請求データに基づく請求書が発行済でないと判定部１３２が判定した場合に警告情報を出力する出力部１３３と、を有する。データ処理装置１がこのような構成を有することで、継続的にされる取引の請求漏れを防止するための情報を提供することができる。 [Effects of data processor 1]
As described above, in the data processing device 1, the identification unit 131 for identifying periodic billing data indicating the billing content of a bill issued periodically, and the bill based on the periodic billing data identified by the identification unit 131. after the first timing of creating or issuing the invoice and before the second timing of creating or issuing the invoice after the first timing, it is determined whether or not the invoice has been issued. It has a determination unit 132 and an output unit 133 that outputs warning information when the determination unit 132 determines that the invoice based on the periodic billing data has not been issued. With such a configuration, the data processing device 1 can provide information for preventing billing omissions for continuous transactions.
　以上、本発明を実施の形態を用いて説明したが、本発明の技術的範囲は上記実施の形態に記載の範囲には限定されず、その要旨の範囲内で種々の変形及び変更が可能である。例えば、装置の全部又は一部は、任意の単位で機能的又は物理的に分散・統合して構成することができる。また、複数の実施の形態の任意の組み合わせによって生じる新たな実施の形態も、本発明の実施の形態に含まれる。組み合わせによって生じる新たな実施の形態の効果は、もとの実施の形態の効果を併せ持つ。 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 information terminal 11 communication unit 12 storage unit 13 control unit 121 regular data storage unit 122 billing data storage unit 123 model storage unit 131 identification unit 132 determination unit 133 output unit 134 acquisition unit

Claims (10)

  1. 　定期的に発行される請求書における請求内容を示す定期請求データを特定する特定部と、
    　前記特定部が特定した前記定期請求データに基づく請求書を作成又は発行する第１タイミングよりも後であり、かつ前記第１タイミングの後に該請求書を作成又は発行する第２タイミングよりも前に、該請求書が発行済であるか否かを判定する判定部と、
    　前記定期請求データに基づく請求書が発行済でないと前記判定部が判定した場合に警告情報を出力する出力部と、
    　を有するデータ処理装置。     an identification unit for identifying periodic billing data indicating billing content in a bill issued periodically;
    After a first timing for creating or issuing a bill based on the periodic billing data specified by the specifying unit, and before a second timing for creating or issuing the invoice after the first timing , a determination unit that determines whether the invoice has been issued;
    an output unit that outputs warning information when the determination unit determines that the invoice based on the periodic billing data has not been issued;
    A data processing device having
  2. 　前記定期請求データの宛先事業者と前記定期請求データにおける請求対象の１以上の品目とを関連付けて記憶する定期データ記憶部をさらに有し、
    　前記特定部は、前記定期データ記憶部に記憶された前記宛先事業者と前記１以上の品目とを含む請求データを前記定期請求データとして特定する、
    　請求項１に記載のデータ処理装置。     a periodical data storage unit that associates and stores a destination business operator of the periodical billing data and one or more items to be billed in the periodical billing data;
    The identifying unit identifies, as the periodic billing data, billing data including the destination business operator and the one or more items stored in the periodic data storage unit.
    2. A data processing apparatus according to claim 1.
  3. 　前記定期データ記憶部は、前記宛先事業者及び前記１以上の品目に関連付けて、前記請求書の発行時期をさらに記憶し、
    　前記判定部は、前記発行時期に基づいて決定した前記第１タイミングよりも後であり、かつ前記第２タイミングよりも前に、該請求書が発行済であるか否かを判定する、
    　請求項２に記載のデータ処理装置。     The periodic data storage unit further stores the timing of issuing the bill in association with the destination business operator and the one or more items,
    The determining unit determines whether the invoice has been issued after the first timing determined based on the issuing time and before the second timing.
    3. A data processing apparatus according to claim 2.
  4. 　宛先事業者と、請求対象の１以上の品目と、定期的な納品日又は定期的な請求日とが記載された注文書データ又は契約書データを取得する取得部をさらに有し、
    　前記特定部は、前記注文書データ又は前記契約書データに記載された前記宛先事業者と前記１以上の品目とを含む請求データを前記定期請求データとして特定する、
    　請求項１から３のいずれか一項に記載のデータ処理装置。     further comprising an acquisition unit that acquires purchase order data or contract data that includes a destination business operator, one or more items to be invoiced, and a periodic delivery date or periodic billing date;
    The identifying unit identifies, as the regular billing data, billing data including the destination business operator and the one or more items described in the order form data or the contract data.
    4. A data processing apparatus according to any one of claims 1 to 3.
  5. 　発行済みの前記請求書における請求内容を示す複数の請求データそれぞれの宛先事業者と、前記複数の請求データそれぞれにおける請求対象の１以上の品目と、前記複数の請求データそれぞれの発行日と、を関連付けた請求履歴情報を記憶する請求データ記憶部をさらに有し、
    　前記判定部は、定期データに含まれる前記宛先事業者と前記１以上の品目とをキーとして前記請求履歴情報を検索し、前記請求履歴情報から抽出された１以上の前記請求データのうち発行日が最新である前記請求データの発行日が検索時から所定の範囲以内であるかに基づいて前記定期請求データが発行済みであるか否かを判定する、
    　請求項２から４のいずれか１項に記載するデータ処理装置。     A destination business operator for each of a plurality of billing data indicating billing content in the issued bill, one or more items to be billed in each of the plurality of billing data, and an issue date of each of the plurality of billing data. further comprising a billing data storage unit that stores associated billing history information;
    The determining unit searches the billing history information using the destination business operator and the one or more items included in the periodic data as keys, and extracts the one or more billing data extracted from the billing history information. determining whether the regular billing data has been issued based on whether the date of issue of the latest billing data is within a predetermined range from the time of retrieval;
    A data processing apparatus according to any one of claims 2 to 4.
  6. 　発行済みの前記請求書における請求内容を示す複数の請求データそれぞれの宛先事業者と、前記複数の請求データそれぞれにおける請求対象の１以上の品目と、前記複数の請求データそれぞれの発行日と、を関連付けた請求履歴情報を記憶する請求データ記憶部をさらに有し、
    　前記特定部は、前記請求履歴情報において、前記宛先事業者と前記請求対象の品目とが一致する３以上の前記請求データ相互の発行日の間隔のうち、発行日が近い前記請求データ同士の複数の前記間隔の関係に基づいて前記定期請求データを特定する、
    　請求項１に記載するデータ処理装置。     A destination business operator for each of a plurality of billing data indicating billing content in the issued bill, one or more items to be billed in each of the plurality of billing data, and an issue date of each of the plurality of billing data. further comprising a billing data storage unit that stores associated billing history information;
    The specifying unit selects, in the billing history information, a plurality of pieces of the billing data whose issuing dates are close among three or more pieces of billing data that match the item to be billed. identifying the recurring billing data based on the interval relationship of
    A data processing apparatus according to claim 1.
  7. 　前記特定部は、前記複数の間隔のばらつきが所定の範囲以内である場合に、前記３以上の請求データを前記定期請求データとして特定する、
    　請求項６に記載するデータ処理装置。     The identifying unit identifies the three or more pieces of billing data as the periodic billing data when the variations in the plurality of intervals are within a predetermined range.
    7. A data processing apparatus according to claim 6.
  8. 　事業者と品目とを入力すると前記定期請求データであるか否かを示す情報を出力する学習済みモデルを記憶する記憶部をさらに有し、
    　前記特定部は、発行済みの前記請求書における請求内容を示す複数の請求データそれぞれの宛先事業者と、前記複数の請求データそれぞれにおける請求対象の１以上の品目とを前記学習済みモデルに入力し、前記学習済みモデルから出力された情報が前記定期請求データであることを示している場合に、前記学習済みモデルに入力した前記宛先事業者及び前記１以上の品目に対応する請求データを前記定期請求データとして特定する、
    　請求項１に記載するデータ処理装置。     further comprising a storage unit that stores a learned model that outputs information indicating whether or not it is the regular billing data when a business operator and an item are entered;
    The specifying unit inputs, into the learned model, a destination business operator of each of a plurality of billing data indicating billing content in the issued bill and one or more items to be billed in each of the plurality of billing data. , when the information output from the learned model indicates that it is the periodic billing data, the billing data corresponding to the destination business operator and the one or more items input to the learned model is sent to the periodic billing data; identify as Billing Data;
    A data processing apparatus according to claim 1.
  9. 　コンピュータが実行する、
    　定期的に発行される請求書における請求内容を示す定期請求データを特定するステップと、
    　前記特定するステップにおいて特定された前記定期請求データに基づく請求書を作成又は発行する第１タイミングよりも後であり、かつ前記第１タイミングの後に該請求書を作成又は発行する第２タイミングよりも前に、該請求書が発行済であるか否かを判定するステップと、
    　前記定期請求データに基づく請求書が発行済でないと前記判定するステップにおいて判定された場合に警告情報を出力する出力するステップと、
    　を有するデータ処理方法。     the computer runs
    identifying recurring billing data indicative of billing content in recurring bills;
    later than a first timing for creating or issuing an invoice based on the regular billing data identified in the identifying step, and after the first timing and before a second timing for creating or issuing the invoice; A step of determining whether the invoice has been issued before;
    an outputting step of outputting warning information when it is determined in the determining step that the invoice based on the periodic billing data has not been issued;
    A data processing method comprising:
  10. 　コンピュータに実行させる、
    　定期的に発行される請求書における請求内容を示す定期請求データを特定するステップと、
    　前記特定するステップにおいて特定された前記定期請求データに基づく請求書を作成又は発行する第１タイミングよりも後であり、かつ前記第１タイミングの後に該請求書を作成又は発行する第２タイミングよりも前に、該請求書が発行済であるか否かを判定するステップと、
    　前記定期請求データに基づく請求書が発行済でないと前記判定するステップにおいて判定された場合に警告情報を出力する出力するステップと、
    　を有するプログラム。     make the computer run
    identifying recurring billing data indicative of billing content in recurring bills;
    later than a first timing for creating or issuing an invoice based on the regular billing data identified in the identifying step, and after the first timing and before a second timing for creating or issuing the invoice; A step of determining whether the invoice has been issued before;
    an outputting step of outputting warning information when it is determined in the determining step that the invoice based on the periodic billing data has not been issued;
    A program with
PCT/JP2021/047975 2021-12-23 2021-12-23 Data processing device, data processing method, and program WO2023119580A1 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
JP2021576751A JP7215779B1 (en) 2021-12-23 2021-12-23 Data processing device, data processing method and program
PCT/JP2021/047975 WO2023119580A1 (en) 2021-12-23 2021-12-23 Data processing device, data processing method, and program
JP2023002753A JP2023094617A (en) 2021-12-23 2023-01-12 Data processing device, data processing method, and program

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2021/047975 WO2023119580A1 (en) 2021-12-23 2021-12-23 Data processing device, data processing method, and program

Publications (1)

Publication Number Publication Date
WO2023119580A1 true WO2023119580A1 (en) 2023-06-29

Family

ID=85111695

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2021/047975 WO2023119580A1 (en) 2021-12-23 2021-12-23 Data processing device, data processing method, and program

Country Status (2)

Country Link
JP (2) JP7215779B1 (en)
WO (1) WO2023119580A1 (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2013186558A (en) * 2012-03-06 2013-09-19 Miroku Jyoho Service Co Ltd Regular sales management program, regular sales management device and regular sales appropriating processing method
JP2016126599A (en) * 2015-01-06 2016-07-11 株式会社Ｃｌｏｕｄ Ｐａｙｍｅｎｔ Periodic billing system, periodic billing method and periodic billing program
JP6759489B1 (en) * 2020-06-01 2020-09-23 ファーストアカウンティング株式会社 Invoice management device, invoice management method and program

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2013186558A (en) * 2012-03-06 2013-09-19 Miroku Jyoho Service Co Ltd Regular sales management program, regular sales management device and regular sales appropriating processing method
JP2016126599A (en) * 2015-01-06 2016-07-11 株式会社Ｃｌｏｕｄ Ｐａｙｍｅｎｔ Periodic billing system, periodic billing method and periodic billing program
JP6759489B1 (en) * 2020-06-01 2020-09-23 ファーストアカウンティング株式会社 Invoice management device, invoice management method and program

Also Published As

Publication number Publication date
JPWO2023119580A1 (en) 2023-06-29
JP7215779B1 (en) 2023-01-31
JP2023094617A (en) 2023-07-05

Similar Documents

Publication Publication Date Title
KR20040107715A (en) System and method for providing personally accounting management service using short message service
JP5391352B1 (en) System and customer management server
CN104221040A (en) Mobile terminal management server, and mobile terminal management program
JP2014216004A (en) Customer management server and customer management system
JPH11143952A (en) Transaction information center device, customer device and store device
JP2019121352A (en) Name-based product aggregation system
CN112541803A (en) Resource state display method and device, computer equipment and readable storage medium
WO2023119580A1 (en) Data processing device, data processing method, and program
JP6805394B1 (en) Data processing equipment, data processing methods and programs
JP6313499B1 (en) System, method and program for managing messages
JP6335866B2 (en) Display control apparatus, display control method, and display control program
JP7001733B2 (en) Information processing method
JP2016012235A (en) Sales promotion information provision server and sales promotion information provision system
JP6186460B2 (en) Information management system, method and program
JP7149676B1 (en) Information processing device, information processing method and program
JPH06325059A (en) Order managing system and customer managing system
CN110807678A (en) Method and system for generating value-added tax red invoice invoicing data
JP5187542B1 (en) Franchise-type organization-specific mediation device, franchise-type organization-specific mediation program, storage medium, and franchise-type organization-specific mediation method
JP7352997B1 (en) Information processing system, information processing method and program
JP7233794B1 (en) Information processing device, information processing method and program
JP2019121035A (en) Name-based product aggregation system
JP7193190B1 (en) Manufacturing consignment support system, manufacturing consignment support program, manufacturing consignment support method
JP7241362B2 (en) Accounting processing system, accounting processing method and accounting processing program
GB2352848A (en) Computer system for goods procurement including consolidating orders
JP2017146864A (en) Order placement data conversion system

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2021576751

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: 21969015

Country of ref document: EP

Kind code of ref document: A1