Certificate issuing device, certificate issuing method, and certificate issuing program

Abstract

To provide a certificate issuing device, a certificate issuing method, and a certificate issuing program that can prevent certificate issuance errors while reducing the workload on personnel responsible for issuing certificates. [Solution] A certificate issuing device equipped with a control unit, which has access to certificate source data that holds information for issuing certificates for each trading partner, and a trading partner master that associates the last issuance date and time of the certificate and the certificate issuance interval for each trading partner, and the control unit is equipped with identification means that, at predetermined certificate issuance timings, identifies target data for which certificates will be issued for each trading partner from the certificate source data based on the last issuance date and time of the certificate and the certificate issuance interval, issuing means that issues certificates for each trading partner using the target data, and updating means that updates the last issuance date and time included in the trading partner master for trading partners for which certificates have been issued.

Description

Technical Field

[0001] The present invention relates to a ticket issuing device, a ticket issuing method, and a ticket issuing program.

Background Art

[0002] Patent Document 1 discloses a technique for automatically performing form issuance in requests for form issuance repeatedly performed for a plurality of product names. In this technique, when repeatedly issuing forms for a plurality of product names, a dynamic code for automatic issuance or semi-automatic issuance is assigned to a request for form issuance of the same product name next time. When the dynamic code is for automatic issuance, a form with the same content as the previous time is automatically issued, and when the dynamic code is for semi-automatic issuance, a form with specific items blanked out is issued.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] By the way, in recent years, due to price fluctuations caused by soaring costs and competition with other companies, in order to conduct continuous transactions, it has become necessary to meet customer demands. Among such customer demands, there may be a demand for adjusting the frequency of receiving tickets. For example, when conducting ticket transactions each time a transaction is made, the receiving / confirmation load of the trading partner increases depending on the transaction volume, so it is often required to issue tickets in a certain aggregation. Also, on the company's side, from the perspective of cost reduction such as paper and ink costs and communication line contract fees, the number of companies considering issuing tickets in aggregation is increasing. However, when setting a period for aggregating tickets for each trading partner, in order to prevent omission of ticket issuance, the load on the person in charge of ticket issuance (for example, a salesperson, etc.) may increase.

[0005] The present invention has been made in view of the above, and aims to provide a certificate issuing device, a certificate issuing method, and a certificate issuing program that can reduce the workload of personnel in charge of issuing certificates while preventing the omission of certificate issuance. [Means for solving the problem]

[0006] To solve the above-mentioned problems and achieve the objective, the present invention provides a certificate issuing device that includes a control unit, which has access to certificate source data that holds information for issuing certificates for each trading partner, and a trading partner master that associates the previous issuance date and time of the certificate with the certificate issuance interval for each trading partner, and the control unit is characterized by including identification means for identifying target data for which certificates are to be issued from the certificate source data for each trading partner based on the previous issuance date and time of the certificate and the certificate issuance interval at predetermined certificate issuance timings, issuing means for issuing certificates for each trading partner using the target data, and updating means for updating the previous issuance date and time included in the trading partner master for trading partners to which certificates have been issued.

[0007] Furthermore, the certificate issuing device according to the present invention has a certificate source data in which the transaction details and processing date are associated for each transaction with the trading partner, and the identification means is characterized in that, when the next issuance date and time after the interval between issuances of the certificate from the previous issuance date and time of the certificate reaches the predetermined issuance timing of the certificate, the record in the certificate source data in which the processing date included in the record falls between the previous issuance date and time and the next issuance date and time, and the certificate has not yet been issued, is identified as the target data.

[0008] Furthermore, the certificate issuing device according to the present invention is characterized in that, when the next issuance date and time after the issuance interval from the previous issuance date and time of the certificate reaches the predetermined issuance timing of the certificate, the identification means extends the issuance interval for business partners whose target data is not included in the certificate source data.

[0009] Furthermore, the certificate issuing device according to the present invention is characterized in that the customer master further associates the date and time of the next issuance of the certificate after the interval between issuances with the date and time of the previous issuance of the certificate, and the update means further updates the date and time of the next issuance included in the customer master for the customer that issued the certificate.

[0010] Furthermore, the certificate issuing device according to the present invention is characterized in that the certificate issuance interval is at least one of the following: the number of days and the number of days of the week.

[0011] Furthermore, the certificate issuance method according to the present invention is a certificate issuance method performed in a certificate issuance device equipped with a control unit, wherein the control unit has access to certificate source data that holds information for issuing certificates for each trading partner, and a trading partner master that associates the previous issuance date and time of the certificate with the certificate issuance interval for each trading partner, and is characterized in that, at each predetermined certificate issuance timing, the control unit performs a selection step of identifying target data for which the certificate is to be issued from the certificate source data for each trading partner based on the previous issuance date and time of the certificate and the certificate issuance interval, an issuance step of issuing the certificate for each trading partner using the target data, and an update step of updating the previous issuance date and time included in the trading partner master for trading partners to which the certificate has been issued.

[0012] Furthermore, the certificate issuance program according to the present invention is a certificate issuance program to be executed by a certificate issuance device equipped with a control unit, wherein the control unit has access to certificate source data that holds information for issuing certificates for each trading partner, and a trading partner master that associates the previous issuance date and time of the certificate with the certificate issuance interval for each trading partner, and is a product management program to be executed by the control unit at predetermined certificate issuance timings, which includes: an identification step that identifies target data for which certificates are to be issued for each trading partner from the certificate source data based on the previous issuance date and time of the certificate and the certificate issuance interval; an issuance step that issues the certificate for each trading partner using the target data; and an update step that updates the previous issuance date and time included in the trading partner master for trading partners to which certificates have been issued. [Effects of the Invention]

[0013] According to the present invention, it is possible to prevent the omission of issuing certificates while reducing the workload on the person in charge of issuing certificates. [Brief explanation of the drawing]

[0014] [Figure 1] Figure 1 is a block diagram showing an example of the configuration of a certificate issuing device according to an embodiment. [Figure 2] Figure 2 is a flowchart showing an example of processing by the certificate issuing device according to this embodiment. [Figure 3] Figure 3 shows an example of sales data according to this embodiment. [Figure 4] Figure 4 shows an example of a customer master according to the embodiment. [Figure 5] Figure 5 is a diagram illustrating an example of a specific process according to the embodiment. [Figure 6] Figure 6 shows an example of a temporary work table according to the embodiment. [Figure 7] Figure 7 shows an example of the update process according to the embodiment. [Figure 8]FIG. 8 is a diagram showing an example of sales data according to an embodiment. [Figure 9] FIG. 9 is a diagram showing an example of a customer master according to an embodiment. [Figure 10] FIG. 10 is a diagram for explaining an example of a specific process according to an embodiment. [Figure 11] FIG. 11 is a diagram showing an example of a temporary work table according to an embodiment. [Figure 12] FIG. 12 is a diagram showing an example of an update process according to an embodiment. Embodiments for Carrying Out the Invention

[0015] Hereinafter, embodiments of a ticket issuing apparatus, a ticket issuing method, and a ticket issuing program according to the present invention will be described in detail based on the drawings. Note that the present invention is not limited by this embodiment.

[0016] [1. Overview] In recent years, due to requests from customers and cost reduction within the company, etc., the case of issuing tickets in batches at regular intervals has been increasing. In such cases, instead of issuing tickets for each transaction, tickets for a certain amount of transactions are issued in batches. However, the periods for issuing tickets in batches vary depending on the customer. For example, various periods such as the number of days (every two days, every ten days, etc.) or for each day of the week (every Tuesday, etc.) are set. Therefore, the person in charge of issuing tickets has an increasing burden related to ticket issuance in order to issue tickets without omission within the period set for each customer in charge. Also, if tickets could not be issued within the set period, it might lead to claims.

[0017] Therefore, the certificate issuing device, certificate issuing method, and certificate issuing program according to this embodiment store the date and time of the previous certificate issuance and the aggregation period (certificate issuance interval) in the customer master that manages customer partners. At a predetermined certificate issuance timing, it is checked whether each customer is eligible for issuance, and if they are eligible, the certificate is automatically issued. This prevents certificate issuance omissions while reducing the workload on the person in charge of certificate issuance. Furthermore, by preventing certificate issuance omissions and reducing the workload on the person in charge, the certificate issuing device, certificate issuing method, and certificate issuing program according to this embodiment can maintain the trust of customer partners and lead to securing resources for new proposals and transactions.

[0018] [2. Structure] An example of the configuration of the certificate issuing device according to this embodiment will be described with reference to Figure 1. Figure 1 is a block diagram showing an example of the configuration of the certificate issuing device 100 according to this embodiment.

[0019] As shown in Figure 1, the certificate issuing device 100 comprises a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108, and is connected to a server 200 (e.g., a web server) that stores various data (for example, the data stored in the storage unit 106, which will be described later) via a network 300 (e.g., the Internet, an intranet, a LAN (Local Area Network)).

[0020] Each component of the certificate issuing device 100 is connected to communicate via any communication channel.

[0021] The certificate issuing device 100 may be a stationary device such as a desktop personal computer, or it may be a portable device such as a notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

[0022] The control unit 102 is a CPU or similar component that comprehensively controls the certificate issuing device 100. The control unit 102 has internal memory for storing control programs such as the OS, programs that define various processing procedures, and required data, and executes various information processing based on these stored programs.

[0023] Functionally, the control unit 102 includes an acquisition unit 102a, a specification unit 102b, an issuance unit 102c, an update unit 102d, and the like.

[0024] The acquisition unit 102a acquires certificate source data for each certificate issuance timing. The certificate issuance timing is the date and time of certificate issuance set by the company, and a regular date and time is set. The certificate source data is data that holds information for issuing certificates, and has records that associate transaction details and processing date for each transaction with a business partner. Each record included in the certificate source data is associated with, for example, the business partner, the quantity of goods traded, the unit price, the amount, the processing date processed by the company, and a classification indicating whether the certificate has been issued or not. The amount is obtained by multiplying the quantity by the unit price.

[0025] The identification unit 102b refers to the customer master and identifies the target data for which certificates will be issued from the certificate source data. The customer master associates the previous certificate issuance date and time and the certificate issuance interval for each customer. At each predetermined certificate issuance timing, the identification unit 102b identifies the target data for which certificates will be issued from the certificate source data for each customer, based on the previous certificate issuance date and time and the certificate issuance interval. Specifically, when the certificate issuance timing reaches the next issuance date and time after the certificate issuance interval from the previous certificate issuance date and time, the identification unit 102b identifies records in the certificate source data whose processing date falls between the previous issuance date and time and the next issuance date and time, and for which certificates have not yet been issued, as target data. Here, when the certificate issuance timing reaches the next issuance date and time after the certificate issuance interval from the previous certificate issuance date and time, the identification unit 102b extends the issuance interval for customers for whom the certificate source data does not contain target data. The issuance interval for the certificate is at least one of the following: days or days of the week.

[0026] The issuing unit 102c issues certificates for each trading partner using the target data. Specifically, the issuing unit 102c issues certificates that summarize the target data identified by the identification unit 102b for each trading partner. The certificates may include the quantity, unit price, and amount of the goods traded.

[0027] The update unit 102d updates the previous issuance date and time included in the customer master for the customer to whom the certificate was issued. The customer master may include the next issuance date and time after the interval between the previous issuance date and time of the certificate. The update unit 102d further updates the next issuance date and time included in the customer master for the customer to whom the certificate was issued.

[0028] The communication interface unit 104 connects the certificate issuing device 100 to the network 300 in a communicative manner via communication devices such as routers and wired or wireless communication lines such as dedicated lines. The communication interface unit 104 also has the function of communicating data with other devices via communication lines.

[0029] The memory unit 106 stores various databases, tables, and files. The memory unit 106 also stores computer programs that work in cooperation with the OS (Operating System) to give instructions to the CPU (Central Processing Unit) to perform various processes. As the memory unit 106, for example, memory devices such as RAM (Random Access Memory) and ROM (Read Only Memory), fixed disk devices such as hard disks, flexible disks, and optical disks can be used.

[0030] The storage unit 106 stores the customer master 106a, the source data 106b, and the temporary work table 106c.

[0031] The customer master 106a contains records that associate customers with the date and time of the previous issuance of the certificate, the issuance interval set for each customer, and the next issuance date and time calculated from the previous issuance date and time and the issuance interval. It is referenced by the identification unit 102b and updated by the update unit 102d. The customer master 106a can be modified as needed to add customers and change the issuance interval.

[0032] The source data 106b is acquired and stored by the acquisition unit 102a each time a transaction with a business partner is processed by the company. The source data 106b includes, for example, sales data, payment request data, purchase data, etc.

[0033] The temporary worktable 106c is a worktable in which the target data identified by the identification unit 102b is registered, and is referenced by the issuing unit 102c.

[0034] The input / output interface unit 108 is connected to an input device 400 and an output device 500. The output device 500 includes display devices such as displays and projectors, sound devices such as speakers, printing devices such as printers, and devices that allow data to be downloaded in data file format. The data file format can be any file format known in this field, such as PDF, CSV, document files, spreadsheet software files, or text files. The input device 400 can include a keyboard, mouse, and microphone, as well as a monitor that works in conjunction with the mouse to provide pointing device functionality.

[0035] [3. Specific Examples] The information processing by the certificate issuing device 100 according to this embodiment will be explained below using a specific example. Figure 2 is a flowchart showing an example of processing by the certificate issuing device 100 according to this embodiment.

[0036] In the certificate issuing device 100, the acquisition unit 102a determines whether or not the timing for issuing the certificate has been reached (S101).

[0037] If the timing for issuing the certificate has been reached (S101, Yes), the acquisition unit 102a acquires a record from the certificate source data 106b (S102). Note that the acquisition unit 102a remains in a standby state until the timing for issuing the certificate is reached (S101, No).

[0038] The identification unit 102b refers to the customer master and determines whether the customer included in the record acquired by the acquisition unit 102a is a customer whose next issuance date and time has arrived (S103).

[0039] If the customer included in the record is a customer whose next issuance date and time has been reached (S103, Yes), the identification unit 102b further determines whether or not a certificate has been issued for that record (S104). If the customer included in the record is not a customer whose next issuance date and time has been reached (S103, No), the certificate issuing device 100 proceeds to the process in S106.

[0040] If the certificate has not yet been issued (S104, No), the identification unit 102b registers the record as data to be issued for the certificate in the temporary work table 106c (S105). If the certificate has already been issued (S104, Yes), the certificate issuing device 100 proceeds to the process in S106.

[0041] After the processing by the identification unit 102b is performed, the acquisition unit 102a determines whether all records have been processed (S106). If all records have not been processed (S106, No), the acquisition unit 102a returns to S102 and retrieves the unprocessed records from the source data.

[0042] On the other hand, if all records have been processed (S106, Yes), the issuing unit 102c issues a certificate using the records (target data) registered in the temporary work table (S107).

[0043] The update unit 102d updates the customer master for customers for whom certificates have been issued by the issuing unit 102c (S108).

[0044] As described above, the certificate issuing device 100 identifies the target data from the source data of a trading partner that has reached the next issuance date and time, at the periodic certificate issuance timing set by the company, and issues a certificate using the identified target data. Here, since the certificate issuance interval (batch period) differs for each trading partner, the next issuance date and time will also differ for each trading partner. Furthermore, the certificate issuance interval can be set by various conditions, such as by the number of days or by the day of the week. In the following, we will explain the processing of the certificate issuing device 100 for trading partners whose certificate issuance interval is set by the number of days, and then the processing of the certificate issuing device 100 for trading partners whose certificate issuance interval is set by the day of the week, in order. However, in reality, the certificate issuing device 100 processes these trading partners together. In the following example, we will explain the case where the certificate to be issued is a delivery slip and the source data is sales data.

[0045] (Handling when the summarization period is in days) Figure 3 shows an example of sales data according to the embodiment. For example, when a sale is recorded by the company, the acquisition unit 102a acquires the record shown in Figure 3 and stores it in the storage unit 106. The sales data stored by the acquisition unit 102a includes records consisting of a combination of "customer code," "customer name," "sales number," "sales date," "quantity," "unit price," "amount," and "issued," as shown in Figure 3.

[0046] For example, the record shown in the first row of Figure 3 indicates that in a transaction with "Tanaka Shoten" with customer code "TO001", one item with a unit price of "100 yen" for a total amount of "100 yen" was sold on "2024 / 8 / 3" with sales number "UA000001", and that the delivery note for that transaction has been "issued". Similarly, the sales data stores various records for each transaction with a customer, including transaction details, sales date (processing date), and the status of delivery note issuance.

[0047] The acquisition unit 102a acquires each record of sales data at the timing of issuing the receipt (delivery note) set by the company. The following explanation will use the example where the delivery note issuance timing is set to 7 PM every day, and the acquisition unit 102a acquires sales data at 7 PM on August 5th.

[0048] The identification unit 102b refers to the customer master and determines whether each record acquired by the acquisition unit 102a is data subject to delivery note issuance.

[0049] Figure 4 shows an example of a customer master according to the embodiment. The customer master stored in the certificate issuing device 100 registers records consisting of combinations of "customer ID", "customer name", "previous transmission date and time (previous issuance date and time)", "summary period (issuance interval)", and "next transmission date and time scheduled (next issuance date and time)", as shown in Figure 4.

[0050] For example, in the customer master data as of 7 PM on August 5th, for "Tanaka Shoten" with "Customer CD: TO001", the previous delivery note was sent on "2024 / 8 / 2 19:00", the consolidation period is "3 days", and the next scheduled delivery date and time, after a 3-day consolidation period has elapsed since the previous delivery, is registered as "2024 / 8 / 5 19:00". Similarly, for "Nakajima Shoten" with "Customer CD: TO002", "Kato Shoten" with "Customer CD: TO003", and "Noumi Shoten" with "Customer CD: TO004", the previous delivery note was sent on "2024 / 8 / 5 19:00", respectively.

[0051] The identification unit 102b refers to the customer master shown in Figure 4 and identifies the records (slips) for which delivery notes will be issued for each customer from the sales data shown in Figure 3. Specifically, for customers whose next scheduled transmission date and time is reached at 7 PM on August 5th, the identification unit 102b identifies the records for which sales have been recorded since the previous transmission date and time as target data.

[0052] Figure 5 is a diagram illustrating an example of the identification process according to the embodiment. Here, Figure 5 shows the status regarding the issuance of delivery slips for each customer shown in Figure 4 in chronological order. For example, for "TO001: Tanaka Shoten," as shown in Figure 5, "August 5, 19:00" is the "scheduled next transmission date and time," which is three days after the "previous transmission date and time: August 2, 19:00." Therefore, the identification unit 102b determines that "TO001: Tanaka Shoten" is a customer subject to delivery slip issuance at the present time (August 5, 19:00) and identifies records for which sales were recorded and delivery slips were not issued between "previous transmission date and time: August 2, 19:00" and "scheduled next transmission date and time: August 5, 19:00" (within the summary period in the diagram) as target data.

[0053] For example, the identification unit 102b identifies the record "Sales Number: UA000001" shown in Figure 3 as not being target data because, although the customer name is "Tanaka Shoten" and the sales date is "2024 / 8 / 3", the category "Issued" indicating whether or not a delivery slip has been issued is "Issued". Here, such records correspond to data such as when a delivery slip was manually issued by a person in charge.

[0054] On the other hand, for the records with sales numbers UA000002 to US000004 shown in Figure 3, the identification unit 102b identifies each record as target data because the customer name is Tanaka Shoten, the sales date falls within the period 8 / 2 to 8 / 5, and the category "Issued" is "Not Issued".

[0055] For example, as shown in Figure 5, for "TO002: Nakajima Shoten," the "next scheduled transmission date and time" is "7 / 29 19:00," which is three days after the "previous transmission date and time: 7 / 26 19:00." However, since no sales records were recorded for "TO002: Nakajima Shoten" during that time, the special unit 102b extended the consolidation period to the present time, and the special unit 102b still determines that "TO002: Nakajima Shoten" is a customer for which a delivery slip should be issued at the present time (19:00 on 8 / 5). Note that the extension of the consolidation period is performed each time a delivery slip is issued (19:00 every day), and this continues up to the present time.

[0056] The identification unit 102b identifies records for "TO002: Nakajima Shoten" that were recorded as sales between "Previous transmission date and time: 7 / 26 19:00" and the present (the original summary period + extended summary period in the diagram) and for which delivery slips have not yet been issued, as target data. For example, the identification unit 102b identifies the record "Sales number: UA000005" shown in Figure 3 as target data because the customer name is "Nakajima Shoten", the sales date is "8 / 5", and the category "Issued" is "Not issued". On the other hand, the identification unit 102b identifies the record "Sales number: UA000006" shown in Figure 3 as not being target data because, although the customer name is "Nakajima Shoten" and the category "Issued" is "Not issued", the sales date is "8 / 6" and it is not within the summary period.

[0057] For example, as shown in Figure 5, "TO003: Kato Shoten" has a "scheduled next transmission date and time" of "8 / 5 19:00," which is 10 days after the "previous transmission date and time: 7 / 26 19:00." Therefore, the identification unit 102b determines that "TO003: Kato Shoten" is a customer for which a delivery slip should be issued at the present time (8 / 5 19:00), and identifies records for which sales were recorded between "previous transmission date and time: 7 / 26 19:00" and "scheduled next transmission date and time: 8 / 5 19:00" (within the summary period shown in the figure) and for which a delivery slip has not yet been issued as target data.

[0058] For example, the identification unit 102b identifies each record in the "Sales Number: UA000007~UA000008" shown in Figure 3 as target data because the customer name is "Kato Shoten", the sales date falls within the period "7 / 26~8 / 5", and the category "Issued" is "Not Issued". On the other hand, for the record "Sales Number: UA000009" shown in Figure 3, the identification unit 102b identifies this record as not target data because, although the customer name is "Kato Shoten" and the category "Issued" is "Not Issued", the sales date is "8 / 6" and does not fall within the summary period.

[0059] Furthermore, for example, as shown in Figure 5, "TO004: Noumi Shoten" has a "scheduled next transmission date and time" of "8 / 6 19:00", which is four days after the "previous transmission date and time: 8 / 2 19:00". Therefore, the identification unit 102b determines that "TO004: Noumi Shoten" is not a customer for which a delivery slip should be issued at this time (19:00 on 8 / 5), and does not identify the target data.

[0060] As described above, the records identified by the identification unit 102b are registered in the temporary work table by the identification unit 102b. Figure 6 shows an example of a temporary work table according to the embodiment. Here, for the sake of explanation, Figure 6 also shows records that are not target data, but in reality, data that is not target data is not registered in the temporary work table.

[0061] As shown in Figure 6, the temporary work table after the identification process by the identification unit 102b contains the records for which delivery slips were issued this time, namely "Sales Numbers: UA000002~UA000005, UA000007~UA000008".

[0062] The issuing unit 102c issues delivery slips using the temporary work table shown in Figure 6. Here, the delivery slips issued by the issuing unit 102c include the transaction details for each record (slip). For example, the issuing unit 102c issues a delivery slip to "TO001: Tanaka Shoten" showing the transaction details (sales date, quantity, unit price, amount, etc.) included in each record from "Sales Number: UA000002 to UA000004". The issuing unit 102c also issues a delivery slip to "TO002: Nakajima Shoten" showing the transaction details (sales date, quantity, unit price, amount, etc.) included in the record from "Sales Number: UA000005". Furthermore, the issuing unit 102c issues a delivery slip to "TO003: Kato Shoten" showing the transaction details (sales date, quantity, unit price, amount, etc.) included in each record from "Sales Number: UA000007 to UA000008".

[0063] The update unit 102d updates the customer master information for customers for whom a delivery note has been issued by the issuing unit 102c. Specifically, the update unit 102d updates the previous transmission date and time and the next scheduled transmission date and time included in the customer master for customers for whom a delivery note has been issued. Figure 7 is a diagram showing an example of the update process according to the embodiment. In Figure 7, the customer master before the update is shown in the upper section, and the customer master after the update is shown in the lower section.

[0064] For example, as shown in Figure 7, the update unit 102d updates the "Previous Transmission Date and Time" for "TO001: Tanaka Shoten," which issued the delivery slip, from "2024 / 8 / 2 (Fri) 19:00" to "2024 / 8 / 5 (Mon) 19:00." Furthermore, based on the updated "Previous Transmission Date and Time: 2024 / 8 / 5 (Mon) 19:00" and "Summary Period: 3 days," the update unit 102d updates the "Next Transmission Date and Time Scheduled" for "TO001: Tanaka Shoten" from "2024 / 8 / 5 (Mon) 19:00" to "2024 / 8 / 8 (Thu) 19:00."

[0065] Similarly, as shown in Figure 7, the update unit 102d updates the "Previous transmission date and time" and "Next transmission date and time scheduled" for "TO002: Nakajima Shoten" and "TO003: Kato Shoten," which issued the delivery slips.

[0066] (Handling when the summarization period is based on the day of the week) Figure 8 shows an example of sales data according to the embodiment. For example, when a sale is recorded by the company, the acquisition unit 102a acquires the record shown in Figure 8 and stores it in the storage unit 106. The sales data stored by the acquisition unit 102a is similar to the sales data shown in Figure 3, and stores records consisting of combinations of "customer code," "customer name," "sales number," "sales date," "quantity," "unit price," "amount," and "issued."

[0067] For example, the record shown in the first row of Figure 8 indicates a transaction with "Sakaguchi Shoten" with customer code "NO001," where "2" units of an item priced at "150 yen" for a total amount of "300 yen" were sold on "2024 / 8 / 3" with sales number "RG000001," and a delivery note for that transaction has been "issued." Similarly, the sales data stores various records for each transaction with a customer, including transaction details, sales date (processing date), and the status of the delivery note issuance.

[0068] The acquisition unit 102a acquires each record of sales data at the timing of issuing the receipt (delivery note) set by the company. The following explanation will use the example where the delivery note issuance timing is set to 7 PM every day, and the acquisition unit 102a acquires sales data at 7 PM on August 8th.

[0069] The identification unit 102b refers to the customer master and determines whether each record acquired by the acquisition unit 102a is data subject to delivery note issuance.

[0070] Figure 9 shows an example of a customer master according to the embodiment. The customer master referenced by the specific unit 102b, for example, is similar to the customer master shown in Figure 4, and registers records consisting of combinations of "customer ID," "customer name," "previous transmission date and time (previous issuance date and time)," "summary period (issuance interval)," and "next transmission date and time (next issuance date and time)." Here, in the customer master for customers whose summary period is by day of the week, "day of the week" is registered in "summary period."

[0071] For example, in the customer master data as of 7 PM on August 8th, for "Sakaguchi Shoten" with "Customer CD: NO001", the previous delivery note transmission date and time is registered as "2024 / 8 / 1 (Thu) 19:00", the consolidation period is "Thu (Thursday)", and the next scheduled transmission date and time after the consolidation period has elapsed since the previous transmission date and time is registered as "2024 / 8 / 8 (Thu) 19:00". Similarly, for "Kakuda Shoten" with "Customer CD: NO002" and "Terao Shoten" with "Customer CD: NO003", the previous delivery note transmission date and time, consolidation period, and next scheduled transmission date and time are registered, respectively.

[0072] The identification unit 102b refers to the customer master shown in Figure 9 and identifies the records (slips) for which delivery notes will be issued for each customer from the sales data shown in Figure 8. Specifically, for customers whose next scheduled transmission date and time is reached at 7 PM on August 8, the identification unit 102b identifies the records for which sales have been recorded since the previous transmission date and time as the target data.

[0073] Figure 10 is a diagram illustrating an example of the identification process according to the embodiment. Here, Figure 10 is a diagram showing the status regarding the issuance of delivery slips in chronological order for each customer shown in Figure 9. For example, for "NO001: Sakaguchi Shoten," as shown in Figure 10, the "next scheduled transmission date and time" is "August 8 (Thu) 19:00," which is after the "summary period: every Thursday (number of days: 7 days)" has elapsed from "previous transmission date and time: August 1 (Thu) 19:00." Therefore, the identification unit 102b determines that "NO001: Sakaguchi Shoten" is a customer subject to delivery slip issuance at the present time (August 8, 19:00) and identifies records for which sales were recorded and delivery slips have not been issued between "previous transmission date and time: August 1 (Thu) 19:00" and "next scheduled transmission date and time: August 8 (Thu) 19:00" (within the summary period in the diagram) as target data.

[0074] For example, the identification unit 102b identifies the record with "Sales Number: RG000001" shown in Figure 8 as not being target data because the customer name is "Sakaguchi Shoten" and the sales date is "2024 / 8 / 3", but the category "Issued" is "Completed". On the other hand, the identification unit 102b identifies the record with "Sales Number: RG000002" shown in Figure 8 as target data because the customer name is "Sakaguchi Shoten", the sales date is "8 / 3", and the category "Issued" is "Not Issued".

[0075] For example, as shown in Figure 10, "NO002: Kakuda Shoten" has a "scheduled next transmission date and time" of "August 8th (Thu) 19:00," which is the period of "compilation period: every Thursday (number of days: 7 days)" from "previous transmission date and time: August 1st (Thu) 19:00." Therefore, the identification unit 102b determines that "NO002: Kakuda Shoten" is a customer for which a delivery slip should be issued at the present time (August 8th, 19:00), and identifies records for which sales were recorded between "previous transmission date and time: August 1st (Thu) 19:00" and "scheduled next transmission date and time: August 8th (Thu) 19:00" (within the compilation period shown in the figure) and for which a delivery slip has not yet been issued as target data.

[0076] For example, the identification unit 102b identifies the record with "Sales Number: RG000003" shown in Figure 8 as not being target data because the customer name is "Kakuda Shoten", the category "Issued" is "Not Issued", and the sales date is "2024 / 8 / 9", which is outside the aggregation period. On the other hand, the identification unit 102b identifies the record with "Sales Number: RG000004" shown in Figure 8 as target data because the customer name is "Kakuda Shoten", the sales date is "8 / 5", and the category "Issued" is "Not Issued".

[0077] Furthermore, for example, as shown in Figure 10, "NO003: Terao Shoten" has a "next scheduled transmission date and time" of "19:00 on 8 / 9 (Fri)", which is the period of "compilation period: every Friday (number of days: 7 days)" since the "last transmission date and time: 19:00 on 8 / 2 (Fri)". Therefore, the identification unit 102b determines that "NO003: Terao Shoten" is not a customer subject to delivery slip issuance at this time (19:00 on 8 / 8) and does not identify the target data.

[0078] As described above, the records identified by the identification unit 102b are registered in the temporary work table by the identification unit 102b. Figure 11 shows an example of the temporary work table according to the embodiment. Here, for the sake of explanation, records that are not target data are also shown in Figure 11, but in reality, data that is not target data is not registered in the temporary work table.

[0079] As shown in Figure 11, the temporary work table after the identification process by the identification unit 102b contains the records for which delivery slips were issued this time, namely "Sales Number: RG000002" and "RG000004".

[0080] The issuing unit 102c issues delivery slips using the temporary work table shown in Figure 11. For example, the issuing unit 102c issues a delivery slip for "NO001: Sakaguchi Shoten" showing the transaction details (sales date, quantity, unit price, amount, etc.) included in the record with "Sales Number: RG000002". The issuing unit 102c also issues a delivery slip for "NO002: Kakuta Shoten" showing the transaction details (sales date, quantity, unit price, amount, etc.) included in the record with "Sales Number: RG000004".

[0081] The update unit 102d updates the customer master information for customers for whom delivery slips have been issued by the issuing unit 102c. Figure 12 is a diagram showing an example of the update process according to the embodiment. In Figure 12, the customer master before the update is shown in the upper section, and the customer master after the update is shown in the lower section.

[0082] For example, as shown in Figure 12, the update unit 102d updates the "Previous Transmission Date and Time" for "NO001: Sakaguchi Shoten," which issued the delivery slip, from "2024 / 8 / 1 (Thu) 19:00" to "2024 / 8 / 8 (Thu) 19:00." Furthermore, based on the updated "Previous Transmission Date and Time: 2024 / 8 / 8 (Mon) 19:00" and "Summary Period: Thu (Thursday)," the update unit 102d updates the "Next Transmission Date and Time Scheduled" for "NO001: Sakaguchi Shoten" from "2024 / 8 / 8 (Thu) 19:00" to "2024 / 8 / 15 (Thu) 19:00."

[0083] Similarly, as shown in Figure 12, the update unit 102d updates the "Previous transmission date and time" and "Next transmission date and time scheduled" for "NO002: Kakuda Shoten," which issued the delivery slip.

[0084] In the embodiment described above, an example was explained in which sales data is used as the source data for the document and a delivery note is issued as the document. However, the embodiment is not limited to this, and the document may also be a payment request form or a purchase statement, which serve as a return form for the customer. For example, when issuing a payment request form, the document issuing device 100 stores payment request data as the source data 106b, which includes records associated with the customer code, customer name, payment request number, payment request date (processing date), transaction details, and classification "issued," and issues a payment request form for each customer using the payment request data and the customer master. Alternatively, for example, when issuing a purchase statement, the document issuing device 100 stores purchase data as the source data 106b, which includes records associated with the customer code, customer name, purchase number, purchase date (processing date), transaction details, and classification "issued," and issues a purchase statement for each customer using the purchase data and the customer master.

[0085] According to the embodiment described above, even if a batch period for issuing certificates is set for each business partner, certificates can be automatically issued for each business partner within the set period, preventing certificates from being missed and reducing the workload on the person in charge of issuing certificates.

[0086] [4. Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This embodiment can contribute to improving operational efficiency and promoting appropriate management decisions within companies, thereby enabling contributions to SDGs Goals 8 and 9.

[0087] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and digital processes, thereby contributing to SDGs Goals 12, 13, and 15.

[0088] Furthermore, this embodiment can contribute to strengthening control and governance, thereby enabling contributions to SDG Goal 16.

[0089] [5. Other Embodiments] Although embodiments of the present invention have been described above, the present invention may be implemented in various different embodiments within the scope of the technical idea described in the claims, in addition to the embodiments described above.

[0090] For example, among the processes described in the embodiments described above, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically by known methods.

[0091] In addition, the processing procedures, control procedures, specific names, information including parameters such as registration data and search conditions for each process, screen examples, and database configuration shown in the above-mentioned documents and drawings may be changed at will unless otherwise specified.

[0092] Furthermore, with respect to the certificate issuing device 100, each component shown in the illustration is a functional concept and does not necessarily have to be physically configured as shown.

[0093] For example, the processing functions of each device constituting the certificate issuing device 100, particularly those performed in the control unit, may be implemented in whole or in part by a CPU and a program interpreted and executed by the CPU, or they may be implemented as wired logic hardware. The program is recorded on a non-temporary computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processing described in this embodiment, and is mechanically read by each device as needed. That is, a storage unit such as ROM or HDD (Hard Disk Drive) records a computer program that works in cooperation with the OS to give instructions to the CPU and perform various processing. This computer program is executed by being loaded into RAM and works in cooperation with the CPU to constitute the control unit.

[0094] Furthermore, this computer program may be stored on an application program server connected to the certificate issuing device 100 via any network, and it is possible to download all or part of it as needed.

[0095] Furthermore, the program for executing the processing described in this embodiment may be stored on a non-temporary computer-readable recording medium, or it may be configured as a program-first product. Here, "recording medium" includes any "portable physical medium" such as memory cards, USB (Universal Serial Bus) memory, SD (Secure Digital) cards, flexible disks, magneto-optical disks, ROMs, EPROMs (Erasable Programmable Read Only Memory), EEPROMs (Registered Trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROMs (Compact Disk Read Only Memory), MOs (Magneto-Optical disks), DVDs (Digital Versatile Disks), and Blu-ray (Registered Trademark) Discs.

[0096] Furthermore, "program" refers to a data processing method described in any language or writing method, regardless of its format, such as source code or binary code. Note that "program" is not necessarily limited to a single, monolithic structure; it also includes distributed structures consisting of multiple modules or libraries, and those that work in cooperation with other programs, such as an operating system, to achieve their functions. Regarding the specific configuration and reading procedures for reading the recording medium in each device shown in the embodiments, as well as the installation procedures after reading, well-known configurations and procedures can be used.

[0097] The various databases stored in the memory unit are storage means such as RAM, ROM, other memory devices, hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and website provision.

[0098] Furthermore, the certificate issuing device 100 may be configured as an information processing device such as a known personal computer or workstation, or as an information processing device to which any peripheral devices are connected. Alternatively, the certificate issuing device 100 may be implemented by installing software (including programs or data, etc.) that enables the processing described in this embodiment onto the certificate issuing device 100.

[0099] Furthermore, the specific forms of distribution and integration of the devices are not limited to those shown in the figures, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit according to various additions or functional loads. In other words, the embodiments described above may be implemented in any combination, or the embodiments may be implemented selectively. [Industrial applicability]

[0100] This invention is useful for accounting procedures in manufacturing industries such as agricultural machinery manufacturing, heavy machinery manufacturing, and the semiconductor industry. [Explanation of symbols]

[0101] 100 Certificate Issuing Device 102 Control Unit 102a Acquisition Department 102b Specific part 102c Publishing Department 102d Update Department 104 Communication Interface Section 106 Storage section 106a Customer Master 106b Source data of the certificate 106c Temporary work table 108 Input / Output Interface Section 200 servers 300 Networks 400 Input Devices 500 Output Device

Claims

1. A certificate issuing device equipped with a control unit, It is possible to access the certificate source data, which holds information for issuing certificates for each business partner, and the business partner master, which associates the last issuance date and time of the certificate with the issuance interval of the certificate for each business partner. The control unit, A means for identifying target data for which the certificate is to be issued, for each trading partner, from the certificate source data, based on the date and time of the previous issuance of the certificate and the issuance interval of the certificate, at each predetermined issuance timing of the certificate; An issuing means for issuing the certificate for each business partner using the aforementioned target data, An update means for updating the previous issuance date and time included in the customer master for the customer that issued the aforementioned certificate, Equipped with, A certificate issuing device characterized by the following features.

2. The aforementioned certificate source data has records that associate transaction details and processing dates for each transaction with the aforementioned trading partner. The identification means identifies, when the timing of issuing the certificate reaches the next issuance date and time after the interval between the previous issuance date and time of the certificate, as the target data, in the certificate source data, records in which the processing date included in the record falls between the previous issuance date and time and the next issuance date and time, and for which the certificate has not yet been issued. The certificate issuing device according to feature 1.

3. The aforementioned identification means extends the issuance interval for business partners whose source data does not contain the target data when the timing of issuing the certificate reaches the next issuance date and time after the interval between the previous issuance date and time of the certificate. The certificate issuing device according to feature 2.

4. The aforementioned customer master further associates the date and time of the next issuance of the certificate after the interval between issuances, with the date and time of the previous issuance of the certificate. The update means further updates the next issuance date and time included in the customer master for the customer that issued the certificate. The certificate issuing device according to feature 1.

5. The issuance interval for the aforementioned certificate is at least one of the following: days and days of the week. A certificate issuing device according to any one of claims 1 to 4.

6. A certificate issuance method performed in a certificate issuance device equipped with a control unit, The control unit, It is possible to access the certificate source data, which holds information for issuing certificates for each business partner, and the business partner master, which associates the last issuance date and time of the certificate with the issuance interval of the certificate for each business partner. The control unit executes the following: At each predetermined issuance timing of the certificate, a selection step is performed to identify the target data for which the certificate is to be issued for each trading partner from the certificate source data, based on the date and time of the previous issuance of the certificate and the issuance interval of the certificate. An issuance step of issuing the certificate for each business partner using the aforementioned target data, The update step includes updating the previous issuance date and time included in the customer master for the customer that issued the aforementioned certificate. A method for issuing certificates characterized by the following features.

7. A certificate issuance program to be executed by a certificate issuance device equipped with a control unit, The control unit, It is possible to access the certificate source data, which holds information for issuing certificates for each business partner, and the business partner master, which associates the last issuance date and time of the certificate with the issuance interval of the certificate for each business partner. The control unit executes the following: At each predetermined issuance timing of the certificate, a selection step is performed to identify the target data for which the certificate is to be issued for each trading partner from the certificate source data, based on the date and time of the previous issuance of the certificate and the issuance interval of the certificate. An issuance step of issuing the certificate for each business partner using the aforementioned target data, For the trading partner that issued the aforementioned certificate, an update step is performed to update the previous issuance date and time included in the trading partner master, A certificate issuance program to execute the program.

Images