Qualified invoice issuing device, qualified invoice issuing method and qualified invoice issuing program

Abstract

To provide a qualified invoice issuing device capable of appropriately issuing a qualified invoice in accordance with an actual situation or the like of transactions in a physical distribution industry.SOLUTION: This embodiment includes a selection part for receiving from a user an input of selection as to whether materials to be issued when importing and exporting are a qualified invoice or a different qualified invoice is issued in addition to the materials, and an issuance part for issuing the qualified invoice on the basis of the input.SELECTED DRAWING: Figure 6

Description

[Technical Field]

[0001] The present invention relates to a qualified invoice issuing device, a qualified invoice issuing method, and a qualified invoice issuing program. [Background technology]

[0002] Patent document 1 discloses an invention in which receipt data received from a user terminal is associated with the business's qualified invoice issuing business registration number and stored, information that uniquely identifies the stored data is generated, and the generated information is sent to the user terminal. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2022-187822 Summary of the Invention [Problem to be solved by the invention]

[0004] In the logistics industry, there are many documents that are sent to the invoice recipient for each transaction, including freight memos and arrival notices issued when importing or exporting. Freight memos and arrival notices are sometimes sent as invoices, and sometimes they are merely billing details and a separate invoice is sent. Therefore, the documents that need to be kept vary depending on the transaction, making operations complicated.

[0005] The present invention has been made in consideration of the above problems, and aims to provide a qualified invoice issuing device, a qualified invoice issuing method, and a qualified invoice issuing program that can easily switch between treating the freight memo as a qualified invoice or issuing a separate qualified invoice for each transaction in the case of exports, and between treating the arrival notice as a qualified invoice or issuing a separate qualified invoice for each transaction in the case of imports, and that allows for the user to specify in advance, for example at the contract conclusion stage before an order is received, which will be the qualified invoice, and that can provide flexible output while solving the above problems. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the objectives, the qualified invoice issuing device of the present invention is characterized by having a selection unit that accepts input from the user as to whether the documents issued at the time of import / export should be qualified invoices or whether a separate qualified invoice should be issued in addition to the documents, and an issuing unit that issues the qualified invoice based on the input.

[0007] In the qualified invoice issuing device according to the present invention, the material may be a freight memo.

[0008] In addition, in the qualified invoice issuing device according to the present invention, the material may be an arrival notice.

[0009] In addition, the qualified invoice issuing device of the present invention may further include a registration unit that accepts input of transaction details at the conclusion of the transaction, and the registration unit may create a first table showing the conclusion detail data based on the input.

[0010] In addition, in the qualified invoice issuing device of the present invention, the registration unit may be characterized in that it creates a second table showing invoice information by inheriting information from the first table.

[0011] In addition, in the qualified invoice issuing device of the present invention, the registration unit may be characterized in that it creates the second table based on HBL (House Bill of Lading) input data or DO (Delivery Order) input data.

[0012] In addition, in the qualified invoice issuance device of the present invention, the issuance unit may be characterized in that if the document is to be the qualified invoice, it outputs the document as the qualified invoice, and if the qualified invoice is to be issued separately in addition to the document, it outputs the document as a breakdown document.

[0013] In addition, in the qualified invoice issuance device of the present invention, the issuance unit may be characterized in that if the document is to be the qualified invoice, it outputs the document as the qualified invoice, and if the qualified invoice is to be issued separately in addition to the document, it outputs the qualified invoice based on separately entered billing input data.

[0014] In addition, the method for issuing qualified invoices according to the present invention is characterized by including a selection step in which the selection unit receives input from the user as to whether the documents to be issued at the time of import / export should be qualified invoices or whether a separate qualified invoice should be issued in addition to the documents, and an issuance step in which the issuance unit issues the qualified invoice based on the input.

[0015] In addition, the qualified invoice issuance program of the present invention causes an information processing device to function as a selection means for accepting input from a user of whether to make the documents issued at the time of import / export a qualified invoice or to issue a separate qualified invoice in addition to the documents, and as an issuance means for issuing the qualified invoice based on the input. [Effects of the Invention]

[0016] The present invention has the effect of providing a qualified invoice issuing device, a qualified invoice issuing method, and a qualified invoice issuing program that can easily switch between treating the freight memo as a qualified invoice or issuing a separate qualified invoice for each transaction in the case of exports, and between treating the arrival notice as a qualified invoice or issuing a separate qualified invoice for each transaction in the case of imports, and that can specify in advance, for example, at the contract conclusion stage before an order is received, which will be the qualified invoice, and that can provide flexible output while solving the above problems. [Brief explanation of the drawings]

[0017] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of a qualified invoice issuing device according to this embodiment. [Figure 2] FIG. 2 is a diagram showing an example of a contract details data table. [Figure 3] FIG. 3 is a diagram showing an example of the billing information data table. [Figure 4] FIG. 4 is a diagram showing an overview of the processing performed by the qualified invoice issuing device according to the embodiment when documents relating to imports and exports are sent as qualified invoices. [Figure 5] FIG. 5 is a diagram showing an overview of the processing performed by a qualified invoice issuing device according to an embodiment when a qualified invoice is sent separately from documents relating to imports and exports. [Figure 6] FIG. 6 is a flowchart showing the flow of processing performed by the qualified invoice issuing device according to this embodiment. [Figure 7] FIG. 7 is a diagram showing an example of the user input screen in step S100. [Figure 8] FIG. 8 is a diagram showing an example of the user input screen in step S400. [Figure 9] FIG. 9 is a diagram showing an example of the user input screen in step S400. [Figure 10] FIG. 10 is a diagram illustrating the update process of the billing information data table that accompanies the process in step S500A. [Figure 11] FIG. 11 is a diagram showing an example of the user input screen in step S500B. [Figure 12] FIG. 12 is a diagram illustrating the update process of the billing information data table that accompanies the process in step S500B. [Figure 13] FIG. 13 is a diagram showing an example of a user input screen in steps S600A and S600B. [Figure 14] FIG. 14 is a diagram illustrating the materials printed as a result of the processing in step S600B. [Figure 15] FIG. 15 is a diagram showing an example of the user input screen in step S700B. [Figure 16] FIG. 16 is a diagram illustrating a qualified invoice printed as a result of the processing in step S700 in FIG. DETAILED DESCRIPTION OF THE INVENTION

[0018] The following describes in detail an embodiment of a qualified invoice issuing device, a qualified invoice issuing method, and a qualified invoice issuing program according to the present invention, with reference to the accompanying drawings. However, the present invention is not limited to the present embodiment.

[0019] [1. Configuration] An example of the configuration of a qualified invoice issuing device 100 according to this embodiment will be described with reference to Fig. 1 etc. Fig. 1 is a block diagram showing an example of the configuration of a qualified invoice issuing device 100.

[0020] The qualified invoice issuing device 100 is constructed, for example, based on a commercially available desktop personal computer. Note that the qualified invoice issuing device 100 is not limited to devices constructed based on stationary information processing devices such as desktop personal computers, but may also be devices constructed based on portable information processing devices such as commercially available notebook personal computers, PDAs (Personal Digital Assistants), smartphones, or tablet personal computers.

[0021] The qualified invoice issuing device 100 comprises a control unit 102, a communication interface unit 104, a memory unit 106, and an input / output interface unit 108. Each unit of the qualified invoice issuing device 100 is connected to each other so that they can communicate with each other via any communication path.

[0022] The communication interface unit 104 communicatively connects the qualified invoice issuing device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has the function of communicating data with other devices via a communication line. Here, the network 300 has the function of connecting the qualified invoice issuing device 100 and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network). Note that the data stored in the memory unit 106 may also be stored in the server 200, for example.

[0023] An input device 112 and an output device 114 are connected to the input / output interface unit 108. The output device 114 may be a monitor (including a home television), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that cooperates with a mouse to achieve a pointing device function.

[0024] Various databases, tables, files, etc. are stored in the storage unit 106. Computer programs that work in conjunction with the OS (Operating System) to issue commands to the CPU (Central Processing Unit) to perform various processes are recorded in the storage unit 106. The storage unit 106 can be, for example, a memory device such as RAM (Random Access Memory) or ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, etc.

[0025] The storage unit 106 stores data such as a contract details data table 106a and a billing information data table 106b.

[0026] FIG. 2 shows an example of information stored in the deal details data table 106a. The deal details table 106a is a table that holds information entered by the user at the conclusion of a transaction. The deal details data table 106a holds information such as a "deal no.", which is a number used to identify each deal; a "line no.", which is used to manage when each deal includes multiple items; a "billing date," which is the date and time of the invoice; a "billing recipient," which is the party to whom the invoice is to be made; "item," which is the invoice item; a "amount," which is the invoice amount; and a "invoice type," which indicates whether the document issued for import / export is a qualified invoice or whether a qualified invoice is to be issued separately in addition to the document. Based on the deal details data table 106a, the qualified invoice issuing device 100 outputs the deal details data 10 to the output device 114 at the user's request.

[0027] In this context, the documents related to exports and imports refer to freight memos for exports and arrival notices for imports. A freight memo is a detailed statement of ocean freight charges sent to the shipper (exporter, consignor) along with the HBL (House Bill of Lading, a bill of lading issued by a forwarder) when exporting. An arrival notice is a notice of costs to be borne sent to the consignee (importer, consignee) when importing. In this case, documents related to exports and imports are sent to the shipper for exports and the consignee for imports. In the "Invoice Type" field, if the documents issued for exports and imports are considered qualified invoices, the value of "Freight Memo / Arrival Notice" is retained as the value of that field. If a qualified invoice is issued separately in addition to the documents issued for exports and imports, the value of "Invoice" is retained as the value of that field. Here, "Freight Memo / Arrival Notice" is interpreted as a freight memo for exports and an arrival notice for imports.

[0028] 3 shows an example of information stored in billing information data table 106b. Billing information data table 106b is a table that stores information necessary for issuing invoices. For example, billing information data table 106b stores information such as an "HB / DO No.", which is the HBL or DO (Delivery Order) number; a "Voucher No.", which is the slip number; a "Line No.", which is used to manage slips containing multiple items; a "Billing Date," which is the date and time of billing; a "Billing Party," which is the party to whom the billing is made; "Items," which are the invoice items; an "Amount," which is the invoice amount; an "Invoice Type," which indicates whether documents issued for imports and exports are qualified invoices or whether a qualified invoice is issued separately in addition to the documents; and a "Data Type," which indicates whether each row is HBL data / DO data, which is data entered by the user, or HBL-input billing data / DO-input billing data / bill-input billing data, which is data for issuing an invoice. The qualified invoice issuing device 100 outputs an invoice to the output device 114 in response to a user's request based on the invoice information data table 106b.

[0029] In addition, in the "Data Type" field, if the data in the corresponding row is (1) HBL data or DO data entered by the user, "HBL Data" or "DO Data" will be retained as the value in the "Data Type" field. (2) If the document issued at the time of export / import is a qualified invoice, that is, if the "Invoice Type" is "Freight Memo" or "Arrival Notice", the data pertains to the invoice, and (3) if the invoice is issued separately in addition to the issuance of a freight memo or arrival notice, that is, if the "Invoice Type" is "Invoice", the data pertains to the invoice, and "Invoice Input Invoice Data" will be retained.

[0030] Returning to Figure 1, the control unit 102 is a CPU or the like that provides overall control of the qualified invoice issuing device 100. The control unit 102 has internal memory for storing control programs such as an OS, programs that define various processing procedures, required data, etc., and executes various information processing operations based on these stored programs.

[0031] The control unit 102 conceptually includes a selection unit 102a, an issuance unit 102b, a registration unit 102c, and the like. The selection unit 102a receives input from the user selecting whether to make documents issued at the time of import / export qualified invoices or to issue a separate qualified invoice in addition to the documents. The issuance unit 102b issues invoices and documents such as freight memos and arrival notices to be issued at the time of import / export. The registration unit 102c registers data received from the user via the input device 112 in the contract details data table 106a and the billing information data table 106b. These functions will be described in detail later.

[0032] [2. Overview] Next, an overview of the processing performed by the qualified invoice issuing device 100 according to the embodiment will be explained using Figures 4 and 5. Figure 1 is a diagram showing the processing flow when documents related to imports and exports are sent as qualified invoices, and Figure 2 is a diagram showing the processing flow when a qualified invoice is sent separately from documents related to imports and exports.

[0033] As shown in FIG. 4, when documents related to imports and exports are sent as qualified invoices, i.e., when the flag indicating that documents related to imports and exports are sent as qualified invoices is ON and the flag indicating that a separate qualified invoice is to be issued is OFF, the registration unit 102c accepts input of the details of the transaction from the user at the time of the transaction and stores the accepted input in the transaction details data table 106a. As a result, the transaction details table 10 is stored in the transaction details data table 106a. Next, the registration unit 102c accepts input of order information from the user at the time of the transaction order acceptance and updates the billing information data table 106b based on the accepted input. As a result, the order details information 11 is stored in the billing information data table 106b. At this time, the user may update the billing information data table 106b by inheriting the content stored in the transaction details data table 106a, or may update the billing information data table 106b by entering new or new information at the time of the transaction acceptance.

[0034] As shown in the example of Figure 4, when the flag indicating that documents related to imports and exports should be sent as qualified invoices is ON, the issuing unit 102b issues the documents related to imports and exports as qualified invoices 12. The issued qualified invoices 12 are sent to the shipper or consignee. Specifically, in the case of exports, the issuing unit 102b issues a freight memo as a qualified invoice 12. The issued qualified invoice 12 is sent to the shipper. In the case of imports, the issuing unit 102b issues an arrival notice as a qualified invoice 12. The issued qualified invoice 12 is sent to the consignee.

[0035] On the other hand, as shown in Figure 5, when a separate qualified invoice is issued in addition to documents related to imports and exports, i.e., when the flag indicating that documents related to imports and exports will be sent as qualified invoices is OFF and the flag indicating that a separate qualified invoice will be issued is ON, the registration unit 102c similarly accepts input of the details of the transaction from the user at the time of conclusion of the transaction and stores the accepted input in the transaction details data table 106a. Next, the registration unit 102c accepts input of order information from the user at the time of order acceptance of the transaction and updates the billing information data table 106b based on the accepted input. As a result, the order content information 11 is stored in the billing information data table 106b.

[0036] As shown in the example of Figure 5, when the flag indicating that import / export documents are to be sent as qualified invoices is OFF, the flag indicating that a separate qualified invoice is to be issued is ON, so the registration unit 102c accepts input of the information necessary to issue an invoice from the user. As a result, the billing information data table 106b is updated. Meanwhile, the issuing unit 103b issues itemized documents 13. Specifically, in the case of export, the issuing unit 102b issues a freight memo as the itemized documents 13. In the case of import, the issuing unit 102b issues an arrival notice as the itemized documents 13. In addition, the issuing unit 102b issues a qualified invoice 12 based on the billing information data table 106b. The issued qualified invoice 12 (or the qualified invoice 12 and itemized documents 13) is sent to the shipper or consignee.

[0037] [3. Specific examples of processing] A specific example of the processing performed by the qualified invoice issuing device 100 configured as described above will be described with reference to Figure 6 and Figures 7 to 16. Figure 6 is a diagram showing an example of a flowchart of the processing performed by the qualified invoice issuing device according to this embodiment.

[0038] First, in step S100, at the stage of contract, the registration unit 102c accepts contract input from the user and registers the accepted transaction details in the contract detail data table 106a. As an example, the registration unit 120c accepts input of transaction details information, such as the billing date, billing recipient, billing items, and amount, from the user, and updates the contract detail data table based on the accepted information. FIG. 7 shows an example of such a user screen. The registration unit 102c accepts input of transaction details from the user through the contract input screen 20. As an example, the registration unit 102c accepts input of billing recipient information through field 31 on the contract input screen 20. Based on the accepted billing recipient information, the registration unit 102c updates the "billing recipient" information in the contract detail data table 106a in step S300, which will be described later.

[0039] As another example, the registration unit 102c accepts input of information on items and amounts through fields 32, 33, etc. of the deal input screen 20. Based on the accepted information, the registration unit 102c updates the information on "items" and "amounts" in the deal details data table 106a in step S300, which will be described later. Note that for these items, default values ​​may be entered in advance, and the registration unit 102c may update the deal details data table 106a only when the user takes action to change the previously entered values.

[0040] In step S200, the selection unit 102a also receives an input of an invoice type from the user, for example, via the pull-down menu 34 on the transaction entry screen 20. Here, the invoice type refers to the type of invoice to be issued. More specifically, it refers to whether the documents issued for exports and imports are qualified invoices or whether a separate qualified invoice is issued in addition to the documents. In the former case, the freight memo is the qualified invoice for exports, and in the latter case, the arrival notice is the qualified invoice. In the latter case, the separately issued invoice is the qualified invoice. Therefore, the pull-down menu 34 is preset with the values ​​"Freight Memo / Arrival Notice" for the former case and "Invoice" for the latter case. In this way, the selection unit 102a receives an input from the user selecting whether the documents issued for exports and imports are qualified invoices or whether a separate qualified invoice is issued in addition to the documents. The user selects one of these values. Based on the selected value, the selection unit 102a updates the value of "Invoice Type" in the transaction detail data table 106a in step S300 (described later).

[0041] If the user selects "Freight Memo / Arrival Notice" from the pull-down menu 34 and inputs that the document to be issued (Freight Memo / Arrival Notice) at the time of import / export is to be a qualified invoice, processing proceeds to step S250A, and when updating the billing information data table 106b, a flag indicating that HBL / DO input billing data will be generated is turned ON.

[0042] On the other hand, if the user selects "Invoice" from the pull-down menu 34 and enters an input indicating that a separate qualified invoice will be issued, processing proceeds to step S250B, and when updating the invoice information data table 106b, a flag indicating that invoice input invoice data will be generated is turned ON.

[0043] Next, the process proceeds to step S300, where the registration unit 102c updates the deal detail data table. That is, the registration unit 102c updates the deal detail data table 106a, which is the first table showing the deal detail data, based on the transaction details input at the conclusion of the transaction. For example, the registration unit 102c updates the "Billing Address" information in the deal detail data table 106a based on the information received from the user in field 31. The registration unit 102c also updates the "Item" and "Amount" information in the deal detail data table 106a based on the information received from the user in fields 32 and 33. The registration unit 102c also updates the value of the "Invoice Type" in the deal detail data table 106a based on the information received via the pull-down menu 34.

[0044] Next, in step S400, the registration unit 102c registers the registration details. There are two main methods for registering the registration details. The first method is to carry over the details of the deal input and enter them, and the second method is to enter them anew. That is, the registration unit 102c registers the transaction details in the transaction details input (HBL / DO input) by carrying over information from the first table, the deal details data table 106a, or by entering new information, and generates the second table, the billing information data table 106b, which shows the billing information.

[0045] FIG. 8 shows an example of the transaction details input screen 21a when transaction details are input using the first method of inputting the details of the deal subsequently.

[0046] In FIG. 8, the registration unit 102c receives a selection input from the user using the pull-down menu 40 as to whether the transaction to be entered is an export or an import. The registration unit 102c selects the document to be used for the import / export based on the selection input received from the user. As an example, if the user selects "export" in the pull-down menu 40, the document to be used for the import / export will be a freight memo. If the user selects "import" in the pull-down menu 40, the document to be used for the import / export will be an arrival notice.

[0047] The registration unit 102c also accepts input of the deal number of the deal to be handed over via field 42. The registration unit 102c updates the billing information data table 106b based on the deal details data table 106a corresponding to the accepted deal number. As an example, when a user specifies "SYNO2402001" as the deal number of the deal to be handed over in field 42, the registration unit 102c retrieves data row 1 from the deal details data table 106a shown in FIG. 2. The registration unit 102c creates data row 2 shown in FIG. 3 based on data row 1 retrieved from the deal details data table 106a and stores it in the billing information data table 106b. Here, data row 2 is basically the same data as data row 1, but with the value "HBL data" added to the "data type" field. "HBL data" and "DO data" indicate that the billing information data table 106b for that data row was created based on the transaction details input in step S400. More specifically, "HBL data" is assigned as the value of "data type" in the case of export, and "DO data" is assigned as the value of "data type" in the case of import.

[0048] The registration unit 102c also displays various information on the transaction detail input screen 21a based on the contents of the created billing information data table 106b. As an example, the registration unit 102c displays the "billing destination" information in the billing information data table 106b in the display area 43. The registration unit 102c also displays the "bill type" information in the billing information data table 106b in the display area 44. The registration unit 102c also displays the billing detail information in the billing information data table 106b on the billing detail registration screen 41.

[0049] The registration unit 102c may further accept input of corrections from the user for each displayed item. When the registration unit 102c accepts input of corrections from the user, the registration unit 102c updates the values ​​in the billing information data table 106b based on the input correction information.

[0050] Next, a case where new transaction details are entered during order entry will be described with reference to Figure 9. Figure 9 shows an example of the transaction details entry screen 21b when transaction details are entered using the second method for newly entering transaction details. In the case of Figure 9, consider the process of newly registering data from order entry for a transaction with a slip number of "TKSQ2402002." The registration unit 102c creates a second table showing invoice information based on HBL (House Bill of Lading) input data or DO (Delivery Order) input data.

[0051] In FIG. 9, the registration unit 102c uses the pull-down menu 40 to receive a selection input from the user as to whether the transaction is an export or an import. The registration unit 102c selects the document to be used for the import / export based on the selection input received from the user. As in the case of FIG. 8, if the user selects "export" in the pull-down menu 40, the document to be used for the import / export will be a freight memo. If the user selects "import" in the pull-down menu 40, the document to be used for the import / export will be an arrival notice.

[0052] The registration unit 102c also accepts input of billing destination information through field 31. As an example, if a user enters "A Trading Company" as billing destination information in field 31, the registration unit 102c updates the value of "Billing Destination" in the data in data rows 3 and 4 in FIG. 3, which corresponds to the slip number "TKSQ2402002" in the billing information data table 106b, to "A Trading Company." The registration unit 102c also accepts input of invoice type through pull-down menu 34. As an example, if a user enters "Invoice" as invoice type information through pull-down menu 34, the registration unit 102c updates the value of "Invoice Type" in the data in data rows 3 and 4 in FIG. 3, which corresponds to the slip number "TKSQ2402002" in the billing information data table 106b, to "Invoice."

[0053] The registration unit 102c may also accept input of other information through the information input acceptance area 51. As an example, the registration unit 102c accepts new input or correction input of items such as "Billing Date," "Item," and "Amount" in the billing information data table 106b corresponding to the voucher number "TKSQ2402002" through the information input acceptance area 51. Based on the accepted input, the registration unit 102c updates the values ​​of the items corresponding to the user input in data row 3 and data row 4 in the billing information data table 106b corresponding to the voucher number "TKSQ2402002." The registration unit 102c may also accept addition or deletion of row numbers from the user through the information input acceptance area 51.

[0054] Next, the processing of S500A and S500B will be explained. When the document issued at the time of import / export is a qualified invoice, that is, when the flag for generating HBL / DO input request data is ON, the processing of steps S500A to S700A is performed. On the other hand, when the flag for generating request input request data is ON, the processing of steps S500B to S700B is performed.

[0055] Next, the processing of step S500A will be described with reference to Fig. 10. In the case where the document issued at the time of import / export is a qualified invoice, the registration unit 102c generates HBL input request data based on the HBL data registered in step S400 (or generates DO input request data based on the DO data registered in step S400).

[0056] This process is shown in Figure 10. Data rows 2, 3, and 4 show the contents of billing information data table 106b generated by the process up to step S400. Here, data rows 2, 3, and 4 are export-related data entered by transaction content registration in step S400, so the data type is "HBL data." The HBL data in data row 2 is, for example, data with content similar to memo 14a, and the HBL data in data rows 3 and 4 is, for example, data with content similar to memo 14b.

[0057] Here, for data row 2, the invoice type is "freight memo / arrival notice," meaning that the document issued for import / export is a qualified invoice, so step S600A is performed. In this case, in step S600A, the registration unit 102c creates HBL input invoice data based on the HBL data, i.e., invoice data created based on HBL data created based on HBL input. Specifically, the registration unit 102c copies data row 2 for all items except "data type" to create new data row 5. Here, the value of "HBL input invoice data" is inserted into "data information" of data row 5. That is, for data where "invoice type," which is a flag indicating whether the document issued for import / export is a qualified invoice, is "freight memo / arrival notice," the registration unit 102c copies the HBL data to generate HBL input invoice data.

[0058] In the above example, in the case of exports, when the "Invoice Type" is "Freight Memo / Arrival Notice," the value of the "Data Type" field will be "HBL Input Invoice Data," but the same process is also used in the case of imports. In the case of imports, when the "Invoice Type" is "Freight Memo / Arrival Notice," the value of the "Data Type" field will be "DO Input Invoice Data." "HBL Input Invoice Data" refers to the data used for qualified invoices when a freight memo is issued as a qualified invoice, and "DO Input Invoice Data" refers to the data used for qualified invoices when an arrival notice is issued as a qualified invoice.

[0059] On the other hand, for data in which the bill type is "bill", the process of step S500A is not performed, and instead the process of step S500B is performed.

[0060] The processing of step S500B will be described with reference to Figures 11 and 12. Figure 11 is an example of the billing input screen 22 displayed to the user in the processing of step S500B. The billing input screen 22 is displayed only for data for which a separate bill is to be issued. In step S500B where the "bill document" is the "claim," a separate bill is to be issued in addition to the documents issued at the time of import / export, so on the billing input screen 22, the registration unit 102c accepts user input regarding the bill information.

[0061] As an example, the registration unit 120c accepts input of transaction information such as the billing date, billing recipient, billing items, and amount from the user. As an example, the registration unit 102c accepts input of whether the transaction is an export or an import from the user via a pull-down menu 40. The registration unit 102c also accepts input of billing recipient information via a field 31. The registration unit 102c also accepts input of various items via a billing detail registration screen 41.

[0062] In this embodiment, default values ​​for the data of these items may already be input, and the user may change the values ​​of only the items that are required to receive input of invoice information.

[0063] The update process for billing information data table 106b will be explained using Figure 12. Here, for data rows 3 and 4, the invoice type is "invoice," meaning that a separate qualified invoice will be issued, so the process of step S600B is performed. In this case, in step S600B, the registration unit 102c generates invoice data for the case where a separate qualified invoice will be issued, based on the data entered by the user. Specifically, the registration unit 102c adds data rows 6 and 7 to billing information data table 10b based on the data entered by the user on billing input screen 22. Here, the value of the "data type" item is "input billing data."

[0064] In addition, on the billing input screen 22, if the registration unit 102c presents the user with the initial values ​​of the billing input billing data using the HBL data of data rows 3 and 4, and the user does not make any changes to the values, data rows 6 and 7 will be equal to data rows 3 and 4 in terms of the values ​​of items other than "data type."

[0065] Although the above example has been described in the case of exports, the same applies to imports.

[0066] The above-described process creates the billing information data table 106b shown in Figure 3. Returning to the data in Figure 3, we summarize the above explanations. In Figure 3, data row 2 shows data for which the "bill type" is "freight memo / arrival notice," i.e., a case where a freight memo is issued as a qualified invoice. Since the "data type" is "HBL data," this is the data created in step S400. Data row 5 shows data for which the "data type" is "HBL input billing data," and is data created in step S500A by copying data row 2. This is the data for a qualified invoice when a freight memo is issued as a qualified invoice.

[0067] Data lines 3 and 4 show data where the "invoice type" is "invoice," i.e., when a separate qualified invoice is to be issued, and since the "data type" is "HBL data," this is data created in step S400. Data lines 6 and 7 show data where the "data type" is "invoice input invoice data," and this is data for the qualified invoice when a separate qualified invoice is to be issued, created based on step S500B.

[0068] Data row 8 is the data for a qualified invoice when no HBL data has been entered. Since no HBL data exists, the "invoice type" is set to "invoice," and the invoice data is the data newly entered by the user in step S500B.

[0069] Next, the processing of steps S600A and S600B will be explained. Both steps S600A and S600B are for printing freight memos / arrival notices, but step S600A is the processing when the documents issued at the time of import / export are qualified invoices, and step S600B is the processing when a separate qualified invoice is issued.

[0070] FIG. 13 shows an example of the freight memo / arrival notice printing screen 23 corresponding to step S600A or step S600B. The document list display screen 50 displays a list of documents. Checking the "Issue Target" checkbox and pressing the F10 key starts printing. The user can select either export or import using the pull-down menu 40. For export, a freight memo is issued based on the HBL input data. If the document issued for import / export is a qualified invoice, the freight memo is printed as a qualified invoice 12, as shown in FIG. 14 (step S600A). Conversely, if a separate qualified invoice is issued, the freight memo is printed as itemized document 13 (internal document) (step S600B). For import, an arrival notice is issued based on the DO input data. If the document issued for import / export is a qualified invoice, the arrival notice is printed as a qualified invoice 12 (step S600A). Conversely, if a separate qualified invoice is to be issued, the arrival notice is printed as itemized document 13 (internal document) (step S600B).

[0071] Next, the processing of steps S700A and S700B will be explained. Both steps S700A and S700B are for printing freight memos / arrival notices, but step S700A is the processing when the documents issued at the time of import / export are qualified invoices, and step S700B is the processing when a separate qualified invoice is issued.

[0072] If the documents issued at the time of import / export are qualified invoices, the processing in steps S600A and S700A is the same, so step S700A may be unnecessary. However, step S600A prints a qualified invoice from the Freight Memo / Arrival Notice printing screen, whereas step S700A prints a qualified invoice from the Qualified Invoice printing screen. If a qualified invoice is printed in either step S600A or step S700A, the processing in the other step can be omitted.

[0073] An example of the screen 24 for printing qualified invoices corresponding to step S700B is shown in Figure 15. A list of vouchers is displayed on the voucher list display screen 60. By checking the "To be issued" checkbox and pressing the F10 key, a qualified invoice 12 is printed, as shown in Figure 16, for example.

[0074] In other words, if the document issued at the time of import / export is a qualified invoice, the document is output as a qualified invoice, and if a separate qualified invoice is issued in addition to the document, a qualified invoice 12 is output based on the separately entered billing input data. From the perspective of billing information data table 106b, if there is a value for "bill input billing data" in the "data type" item, the separately issued invoice is printed as a qualified invoice 12. If there is no "bill input billing data," a freight memo / arrival notice is printed as a qualified invoice in step S600A.

[0075] [4. Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby contributing to the achievement of SDGs Goals 8 and 9.

[0076] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of SDGs Goals 12, 13, and 15.

[0077] Furthermore, this embodiment can contribute to strengthening control and governance, which can contribute to the achievement of Goal 16 of the SDGs.

[0078] 5. Other Embodiments The present invention may be implemented in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

[0079] For example, among the processes described in the embodiments, 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 using known methods.

[0080] Furthermore, the processing procedures, control procedures, specific names, information including parameters such as registered data and search conditions for each process, screen examples, and database configurations shown in this specification and drawings can be changed as desired unless otherwise specified.

[0081] Furthermore, with regard to the qualified bill issuing device 100, the components shown in the figures are functional concepts, and do not necessarily have to be physically configured as shown in the figures.

[0082] For example, all or any part of the processing functions of the qualified invoice issuing device 100, particularly the processing functions performed by the control unit, may be realized by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded on a non-transitory computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the qualified invoice issuing device 100 as needed. In other words, a computer program is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive) for working with the OS to give instructions to the CPU and perform various processes. This computer program is executed by being loaded into RAM, and works with the CPU to form the control unit.

[0083] In addition, this computer program may be stored in an application program server connected to the qualified invoice issuing device 100 via any network, and all or part of it may be downloaded as needed.

[0084] Furthermore, the program for executing the processes described in this embodiment may be stored in a non-transitory computer-readable recording medium or configured as a program product. Here, the term "recording medium" includes any "portable physical medium" such as a memory card, a Universal Serial Bus (USB) memory, a Secure Digital (SD) card, a flexible disk, a magneto-optical disk, a ROM, an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable and Programmable Read Only Memory (EEPROM (registered trademark)), a Compact Disk Read Only Memory (CD-ROM), a Magneto-Optical disk (MO), a Digital Versatile Disk (DVD), and a Blu-ray (registered trademark) disc.

[0085] Furthermore, a "program" is a data processing method written in any language or description method, regardless of the format, such as source code or binary code. Note that a "program" is not necessarily limited to a single structure, but also includes a structure that is distributed as multiple modules or libraries, or a structure that achieves its function by cooperating with a separate program, such as an OS. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in the embodiments, as well as the installation procedure after reading, can use well-known configurations and procedures.

[0086] The various databases stored in the memory unit are storage means such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and providing websites.

[0087] The qualified invoice 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 connected to any peripheral device. The qualified invoice issuing device 100 may also be realized by installing software (including programs or data, etc.) that causes the device to perform the processing described in this embodiment.

[0088] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit depending on various additions or functional loads. In other words, the above-described embodiments can be implemented in any combination, or embodiments can be implemented selectively. [Industrial Applicability]

[0089] The present invention is useful in various industries such as the logistics industry. [Explanation of symbols]

[0090] 100 Qualified bill issuing device 102 Control section 102a Selection section 102b Publishing Department 102c Registration Department 104 Communication interface unit 106 Storage section 106a Transaction details data table 106b Billing Information Data Table 108 Input / Output Interface Section 112 Input Device 114 Output Device 200 servers 300 Network

Claims

1. a selection unit that receives input from a user of whether to make documents issued at the time of import / export into qualified invoices or to issue a separate qualified invoice in addition to the documents; an issuing unit that issues the qualified invoice based on the input; A qualified bill issuing device comprising:

2. The qualified billing device of claim 1 , wherein the document is a freight memo.

3. The qualified bill issuing device according to claim 1 , wherein the document is an arrival notice.

4. Further comprising a registration unit for accepting input of transaction details at the conclusion of the transaction, 2. The qualified invoice issuing device according to claim 1, wherein the registration unit creates a first table showing contract detail data based on the input.

5. 5. The qualified invoice issuing device according to claim 4, wherein the registration unit creates a second table showing invoice information by taking over information from the first table.

6. 6. The qualified invoice issuing device according to claim 5, wherein the registration unit creates the second table based on HBL (House Bill of Lading) input data or DO (Delivery Order) input data.

7. If the document is deemed to be a qualified invoice, the issuing unit outputs the document as the qualified invoice; 2. The qualified invoice issuing device according to claim 1, wherein when the qualified invoice is issued separately in addition to the document, the document is output as a breakdown document.

8. If the document is deemed to be a qualified invoice, the issuing unit outputs the document as the qualified invoice; 2. The qualified invoice issuing device of claim 1, wherein when the qualified invoice is issued separately in addition to the document, the qualified invoice is output based on separately entered billing input data.

9. a selection step in which the selection unit receives an input from a user selecting whether to make documents issued at the time of import / export into qualified invoices or to issue a qualified invoice separately in addition to the documents; an issuing step in which an issuing unit issues the qualified invoice based on the input; A method for issuing qualified invoices, comprising:

10. An information processing device a selection means for receiving from a user a selection input as to whether documents to be issued at the time of import / export should be qualified invoices or whether a qualified invoice should be issued separately in addition to the documents; issuing means for issuing the qualified invoice based on the input; Qualified invoicing program to function as.

Images