Export transaction management device, export transaction management method, and export transaction management program

Abstract

To enable business related to export trading to handle business flow having a different process order.SOLUTION: An order reception input acceptance unit accepts designation of either business flow of control oriented flow or business efficiency oriented flow through an order reception input screen for accepting an input of order reception data in an order reception input step. A first sales input screen display unit displays a first invoice input screen for accepting an input of invoice data at at least one of timing between the order reception input step and a shipping input step, and timing between the shipping input step and a sales input step in the case of accepting the designation of the business efficiency oriented flow as business flow. A first invoice data output unit outputs the invoice data accepted through the first invoice input screen.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to an export transaction management device, an export transaction management method, and an export transaction management program. [Background technology]

[0002] Systems that support operations related to export transactions are known, such as ERP (Enterprise Resource Planning) systems that manage operations by having users enter order entry, shipment entry, invoice entry, and sales entry in this order according to a predetermined, fixed workflow. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2009-256071 Summary of the Invention [Problem to be solved by the invention]

[0004] However, conventional export transaction systems use a fixed workflow, making it difficult to accommodate workflows with different process orders.

[0005] The present invention has been made in consideration of the above-mentioned problems, and aims to provide an export transaction management device, an export transaction management method, and an export transaction management program that can accommodate business flows with different process orders for work related to export transactions. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, an export transaction management device according to the present invention is an export transaction management device that includes a control unit and is used to manage operations related to export transactions, wherein the control unit provides a control-oriented flow, which is a business flow that manages operations related to an order entry process, a shipment entry process, an invoice entry process, and a sales entry process in that order, and a business efficiency-oriented flow, which is a business flow that manages the invoice document creation entry process, which is the invoice entry process in the control-oriented flow, at least one of the timings between the order entry process and the shipment entry process and between the shipment entry process and the sales entry process. an order input receiving unit that receives the designation of any of the business flows via an order input screen for receiving input of order data in the order input process; a first invoice input screen display unit that, when the designation of the business efficiency-oriented flow is received as the business flow, displays a first invoice input screen for receiving input of invoice data at least at one of the timings between the order input process and the shipping input process and between the shipping input process and the sales input process; and a first invoice data output unit that outputs the invoice data input received via the first invoice input screen.

[0007] Furthermore, the export transaction management device according to the present invention, when it receives the designation of the business efficiency-oriented flow as the business flow, comprises: a first sales input screen display unit that displays a first sales input screen for accepting input of sales data in the sales input process; and a consistency check result display unit that displays the result of checking the consistency between the sales data accepted as input via the first sales input screen and the invoice data output by the first invoice data output unit.

[0008] The order data also includes an item that indicates the business flow for which the designation has been accepted.

[0009] In addition, the first invoice input screen display unit displays, among one or more of the order data, the order data in which the business flow represented by the items is the business efficiency-oriented flow on the first invoice input screen.

[0010] Furthermore, the export transaction management device according to the present invention includes a second invoice input screen display unit that, when it receives a designation of the control-oriented flow as the business flow, displays a second invoice input screen for accepting input of the invoice data at a timing between the shipment input process and the sales input process, and the second invoice input screen display unit displays, on the second invoice input screen, one or more of the order data whose business flow represented by the items is the control-oriented flow.

[0011] The export transaction management method according to the present invention is an export transaction management method that is executed by an export transaction management device that includes a control unit and that manages operations related to export transactions, and includes a control-emphasized flow that is a workflow that manages operations related to an order entry process, a shipment entry process, an invoice entry process, and a sales entry process executed by the control unit in this order, and a workflow that manages an invoice document creation entry process that is the invoice entry process in the control-emphasized flow at least one of the timings between the order entry process and the shipment entry process and between the shipment entry process and the sales entry process. a step of accepting designation of the business flow, either a business efficiency-oriented flow or a certain business efficiency-oriented flow, via an order input screen for accepting input of order data in the order input process; when designation of the business efficiency-oriented flow is accepted as the business flow, a step of displaying a first invoice input screen for accepting input of invoice data at least at one of the timings between the order input process and the shipping input process and between the shipping input process and the sales input process; and a step of outputting the invoice data input accepted via the first invoice input screen.

[0012] An export transaction management program according to the present invention is an export transaction management program that is executed by an export transaction management device that includes a control unit and that manages operations related to export transactions, and includes a control-emphasized flow that is a business flow that manages operations related to an order entry process, a shipment entry process, an invoice entry process, and a sales entry process executed by the control unit in this order, and a business flow that manages an invoice document creation entry process that is the invoice entry process in the control-emphasized flow at least one of the timings between the order entry process and the shipment entry process and between the shipment entry process and the sales entry process. a step of accepting designation of either the business flow that prioritizes business efficiency or the business flow that prioritizes business efficiency via an order input screen for accepting input of order data in the order input process; when designation of the business flow that prioritizes business efficiency is accepted as the business flow, a step of displaying a first invoice input screen for accepting input of invoice data at least at one of the timings between the order input process and the shipping input process and between the shipping input process and the sales input process; and a step of outputting the invoice data input accepted via the first invoice input screen. [Effects of the Invention]

[0013] The present invention has the effect of being able to accommodate business flows with different process orders for business related to export transactions. [Brief explanation of the drawings]

[0014] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of an export transaction management device. [Figure 2A] FIG. 2A is an explanatory diagram of an example of an actual business flow related to export transactions. [Figure 2B] FIG. 2B is an explanatory diagram of the control-oriented flow. [Figure 2C] FIG. 2C is an explanatory diagram of a flow that prioritizes business efficiency. [Figure 3] FIG. 3 is a schematic diagram showing an example of the data configuration of the transaction classification master. [Figure 4A] FIG. 4A is a schematic diagram of an example of an order entry screen. [Figure 4B] FIG. 4B is an explanatory diagram of an example of the data configuration of the order header data. [Figure 4C] FIG. 4C is an explanatory diagram of an example of the data configuration of the order detail data. [Figure 5A] FIG. 5A is a schematic diagram of an example of a shipping input screen. [Figure 5B] FIG. 5B is a schematic diagram of an example of the data configuration of the shipping header data. [Figure 5C] FIG. 5C is a schematic diagram of an example of the data configuration of shipping detail data. [Figure 6A] FIG. 6A is a schematic diagram of an example of a second invoice input screen. [Figure 6B] FIG. 6B is a schematic diagram showing an example of the data structure of invoice header data. [Figure 6C] FIG. 6C is a schematic diagram showing an example of the data structure of invoice detail data. [Figure 7A] FIG. 7A is a schematic diagram of an example of the second sales input screen. [Figure 7B] FIG. 7B is a schematic diagram showing an example of the data configuration of sales header data. [Figure 7C] FIG. 7C is a schematic diagram showing an example of the data configuration of sales statement data. [Figure 8A] FIG. 8A is a schematic diagram of an example of an order entry screen. [Figure 8B] FIG. 8B is a schematic diagram of an example of the data configuration of the order header data. [Figure 8C] FIG. 8C is a schematic diagram of an example of the data configuration of the order detail data. [Figure 9A] FIG. 9A is a schematic diagram of an example of the first invoice input screen. [Figure 9B] FIG. 9B is a schematic diagram of an example of the data structure of invoice header data. [Figure 9C] FIG. 9C is a schematic diagram showing an example of the data structure of invoice detail data. [Figure 10A]FIG. 10A is a schematic diagram of an example of a shipping input screen. [Figure 10B] FIG. 10B is a schematic diagram showing an example of the data configuration of the shipping header data. [Figure 10C] FIG. 10C is a schematic diagram showing an example of the data configuration of shipping detail data. [Figure 11A] FIG. 11A is a schematic diagram of an example of the first invoice input screen. [Figure 11B] FIG. 11B is a schematic diagram showing an example of the data structure of invoice header data. [Figure 11C] FIG. 11C is a schematic diagram showing an example of the data structure of the invoice specification data. [Figure 12A] FIG. 12A is a schematic diagram of an example of the first sales input screen. [Figure 12B] FIG. 12B is a schematic diagram of an example of an invoice posting slip consistency check screen. [Figure 12C] FIG. 12C is a schematic diagram showing an example of the data configuration of sales header data. [Figure 12D] FIG. 12D is a schematic diagram showing an example of the data configuration of sales statement data. [Figure 13A] FIG. 13A is a schematic diagram showing an example of the first sales input screen. [Figure 13B] FIG. 13B is a schematic diagram of an example of an invoice posting slip consistency check screen. [Figure 14] FIG. 14 is a flowchart showing an example of the flow of information processing executed by the export transaction management device. DETAILED DESCRIPTION OF THE INVENTION

[0015] Hereinafter, an embodiment of an export transaction management device, an export transaction management method, and an export transaction management program according to the present invention will be described in detail with reference to the accompanying drawings. However, the present invention is not limited to the embodiment.

[0016] [1. Configuration] An example of the configuration of the export transaction management device 100 according to this embodiment will be described with reference to Fig. 1. Fig. 1 is a block diagram showing an example of the configuration of the export transaction management device 100.

[0017] The export transaction management device 100 of this embodiment is a device that manages operations related to export transactions.

[0018] The export transaction control device 100 is a commercially available desktop personal computer. The export transaction control device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may also be a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

[0019] The export transaction management device 100 comprises a control unit 102, a communication interface unit 104, a memory unit 106, and an input / output interface unit 108. The units of the export transaction management device 100 are connected to each other so as to be able to communicate with each other via any communication path.

[0020] The communication interface unit 104 communicatively connects the export transaction management 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 a function of communicating data with other devices via the communication line. Here, the network 300 has a function of connecting the export transaction management 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 various data stored in the memory unit 106 may also be stored in the server 200, for example.

[0021] 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. In the following, the output device 114 may be referred to as the monitor 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

[0022] 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.

[0023] The storage unit 106 stores, for example, a transaction classification master 106a, an order data DB (database) 106b, a shipping data DB 106e, an invoice data DB 106h, and a sales data DB 106k. In this embodiment, the order data DB 106b will be described as being configured by order header data 106c and order detail data 106d. The shipping data DB 106e will be described as being configured by shipping header data 106f and shipping detail data 106g. The invoice data DB 106h will be described as being configured by invoice header data 106i and invoice detail data 106j. The sales data DB 106k will be described as being configured by sales header data 106m and sales detail data 106n.

[0024] The transaction classification master 106a, order data DB 106b, order header data 106c, order detail data 106d, shipping data DB 106e, shipping header data 106f, shipping detail data 106g, invoice data DB 106h, invoice header data 106i, invoice detail data 106j, sales data DB 106k, sales header data 106m, and sales detail data 106n are databases and tables in which various information is registered. In this embodiment, the structures of the databases, tables, and data used in this embodiment are described in simplified form. The actual structures of these databases, tables, and data are more complex, but parts not directly related to the present invention are shown in simplified form.

[0025] These databases are updated by processing performed by the control unit 102, which will be described later. The data configurations of these databases will be described in detail later.

[0026] The control unit 102 is a CPU or the like that performs overall control of the export transaction control device 100. The control unit 102 has an internal memory for storing control programs such as an OS (operating system), programs that define various processing procedures, required data, etc., and executes various information processing operations based on these stored programs.

[0027] The control unit 102 manages the processing related to the business flow of export transactions.

[0028] Figure 2A is an explanatory diagram of an example of the actual business flow for export transactions. In export transactions, an export contract is concluded and goods are shipped. In export transactions, the shipped goods are then loaded onto transportation equipment such as ships or airplanes, and depart for the destination country. Once the goods arrive at the destination country, they go through customs clearance in the destination country, are transported to a trading company in the destination country, and are stored in warehouses.

[0029] The control unit 102 of the export transaction management device 100 of this embodiment can handle multiple types of business flows with different process orders as business flows related to export transactions. The control unit 102 of this embodiment can handle two types of business flows: a control-oriented flow and a business efficiency-oriented flow.

[0030] FIG. 2B is an explanatory diagram of the control-oriented flow.

[0031] The control-oriented flow is an example of a business flow managed by the export transaction management device 100. The control-oriented flow is a business flow that manages business operations related to the order entry process, shipment entry process, invoice entry process, and sales entry process in this order. For example, a user enters order data upon contract conclusion, and enters shipping data such as the shipping quantity at the time of shipment. The user then inputs and outputs invoices at the time of departure, and enters sales data when the goods are delivered to a trading company in the export destination country. In other words, the control-oriented flow is a system management flow that follows the flow of business operations related to export transactions shown in Figure 2A.

[0032] An invoice is a commercial document that serves as a shipping guide, product specification, billing statement, etc., and contains information such as a product overview, shipping schedule, quantity, and unit price. Invoices are also sometimes called forms, trade documents, etc. Invoice data is data that represents an invoice. In the invoice input process, invoice data is created and output by accepting invoice data input by the user.

[0033] FIG. 2C is an explanatory diagram of a flow that prioritizes business efficiency.

[0034] The business efficiency-oriented flow is an example of a business flow managed by the export transaction management device 100. The business efficiency-oriented flow is a business flow that manages the invoice document creation input process, which is the invoice input process in the control-oriented flow, at least one of the following timings: between the order entry process and the shipment entry process, and between the shipment entry process and the sales entry process. In other words, the business efficiency-oriented flow is a business flow in which the invoice document creation input process can be executed either after the order entry process or after the shipment entry process.

[0035] In a control-oriented flow, tasks related to the Order Entry Process, Shipping Entry Process, Invoice Entry Process, and Sales Entry Process are managed in this order. As a result, in a control-oriented flow, users can input invoices and output reports according to a set procedure and timing. On the other hand, while a control-oriented flow maintains control over system management, it limits the timing for users to input and output invoice data (report output) after the Shipping Entry Process. In other words, in a control-oriented flow, it is difficult to handle situations where report output is required before goods are shipped.

[0036] In the business efficiency-oriented flow, the timing of inputting and outputting invoice data can be before the shipment input process, after the shipment input process, or both before and after the shipment input process. Therefore, in the business efficiency-oriented flow, the user can input and output invoice data (output reports) at any time. In addition, in the business efficiency-oriented flow, the user can refer to input data (e.g., order data, shipping data, etc.) at any time.

[0037] Continuing the explanation, returning to Fig. 1, the control unit 102 performs control to accommodate both the control-oriented flow and the business efficiency-oriented flow.

[0038] The control unit 102 includes an order input reception unit 102a, a shipping input reception unit 102b, a second invoice input screen display unit 102c, a second invoice data output unit 102d, a second sales input reception unit 102e, a first invoice input screen display unit 102f, a first invoice data output unit 102g, a first sales input screen display unit 102h, a consistency check result display unit 102i, and a sales output unit 102j.

[0039] Some or all of the order input reception unit 102a, shipping input reception unit 102b, second invoice input screen display unit 102c, second invoice data output unit 102d, second sales input reception unit 102e, first invoice input screen display unit 102f, first invoice data output unit 102g, first sales input screen display unit 102h, consistency check result display unit 102i, and sales output unit 102j may be realized, for example, by having a processing device such as a CPU (Central Processing Unit) execute a program, i.e., by software, or by hardware such as an IC (Integrated Circuit), or by a combination of software and hardware.

[0040] The order entry receiving unit 102a receives a designation of either the control-oriented flow or the business efficiency-oriented flow via an order entry screen for receiving entry of order data in the order entry process.

[0041] The shipping input receiving unit 102b receives input of shipping data.

[0042] The order entry receiving unit 102a and the shipping entry receiving unit 102b execute processes in both the control-oriented flow and the business efficiency-oriented flow.

[0043] The second invoice input screen display unit 102c, the second invoice data output unit 102d, and the second sales input receiving unit 102e execute processing in the control-oriented flow.

[0044] The first invoice input screen display unit 102f, the first invoice data output unit 102g, the first sales input screen display unit 102h, the consistency check result display unit 102i, and the sales output unit 102j execute processes in the business efficiency-oriented flow.

[0045] When the first invoice input screen display unit 102f receives the designation of a business efficiency-oriented flow as the business flow, it displays a first invoice input screen for accepting input of invoice data at least one of the timings between the order entry process and the shipment entry process, and between the shipment entry process and the sales entry process. The first invoice data output unit 102g outputs invoice data entered via the first invoice input screen. Outputting invoice data means at least one of creating, storing, outputting to a screen, and printing invoice data.

[0046] The order data includes items that represent the accepted business flow. Therefore, the first invoice input screen display unit 102f displays, on the first invoice input screen, one or more order data whose business flow represented by items is a business efficiency-oriented flow.

[0047] When the first sales input screen display unit 102h receives the designation of the business efficiency-oriented flow as the business flow, it displays the first sales input screen for receiving the input of sales data in the sales input step. The consistency check result display unit 102i displays the check result of checking the consistency between the sales data received as input via the first sales input screen and the invoice data output by the first invoice data output unit 102g.

[0048] When the second invoice input screen display unit 102c receives the designation of a control-oriented flow as the business flow, it displays a second invoice input screen for receiving input of invoice data between the shipping input process and the sales input process. The second invoice input screen display unit 102c displays, on the second invoice input screen, one or more pieces of order data whose business flow represented by items is a control-oriented flow.

[0049] In the present embodiment, a configuration will be described as an example in which the control unit 102 receives operation input by the user from the input device 112 and displays information such as various screens on the monitor 114. However, the control unit 102 may receive operation input by the user from either the input device 112 or an external information processing device connected via the network 300, and is not limited to receiving the information from the input device 112. Furthermore, the control unit 102 may display information such as various screens on either the monitor 114 or the monitor of an external information processing device connected via the network 300, and is not limited to displaying the information on the monitor 114.

[0050] The flow of processing in the control unit 102 will be described in detail below using a specific example.

[0051] First, the details of the processing flow of the control unit 102 in the control-emphasized flow will be explained using a specific example. The control unit 102 determines whether the business flow for the order to be processed is a control-emphasized flow or a business efficiency-emphasized flow based on the transaction category entered by the user. The transaction category is registered in advance in the transaction category master 106a.

[0052] Figure 3 is a schematic diagram showing an example of the data configuration of the transaction category master 106a. The transaction category master 106a is a database that associates user transaction categories / business flows with overseas sales recording categories. The user transaction category is information that represents the transaction category of the order to be processed. The information representing the business flow registered in the transaction category master 106a indicates either control-oriented, which represents a control-oriented flow, or business efficiency-oriented, which represents a business efficiency-oriented flow.

[0053] By operating the input device 112, the user registers in advance in the transaction category master 106a whether the order to be processed corresponds to a control-oriented flow or a business efficiency-oriented flow. If a business flow that is not used for the order to be processed is not registered in the transaction category master 106a, that business flow will become unavailable. In this embodiment, the explanation will continue assuming that information representing both the control-oriented flow and the business efficiency-oriented flow is registered in the transaction category master 106a.

[0054] 4A to 7C are explanatory diagrams of an example of the flow of processing by the control unit 102 in the control-emphasized flow.

[0055] FIG. 4A is a schematic diagram of an example of the order entry screen 20. As shown in FIG.

[0056] First, the order input receiving unit 102a executes the order input step. The order input receiving unit 102a displays the order input screen 20 on the monitor 114. The order input screen 20 is a screen for receiving input of order data.

[0057] The user operates the input device 112 while viewing the order entry screen 20 to input order data via the order entry screen 20. The order data includes items that represent a business flow. The user inputs the designation of a control-oriented flow by specifying the order category of "control-oriented," which represents a control-oriented flow as the business flow (see display field 20A). By specifying the control-oriented flow, the order transaction is managed in accordance with the control-oriented flow.

[0058] Assume that the user inputs the order data and then operates a registration button (not shown). The order input receiving unit 102a registers the order data input via the order input screen 20 in the order data DB 106b.

[0059] 4B and 4C are schematic diagrams showing an example of the data configuration of the order data DB 106b. As described above, in this embodiment, the order data DB 106b is composed of order header data 106c and order detail data 106d. FIG. 4B is an explanatory diagram showing an example of the data configuration of the order header data 106c. FIG. 4C is an explanatory diagram showing an example of the data configuration of the order detail data 106d.

[0060] The order header data 106c is a database that associates order numbers, business locations, order dates, shipping dates, expected sales dates, departments, customers, billing destinations, currencies, and rates. The order detail data 106d is a database that associates order numbers, order classifications / workflows, warehouses, products, quantities, foreign currency sales amounts, and Japanese currency sales amounts.

[0061] The order entry receiving unit 102a registers the header portion of the order data received via the order entry screen 20 in order header data 106c, and registers the details portion in order detail data 106d. As shown in FIG. 4C, the order detail data includes a "business flow" item. In the example shown in FIG. 4C, the "business flow" item includes "control-oriented," which indicates a control-oriented flow (see FIG. 4C). Therefore, export transactions related to orders identified by the order number corresponding to that item are managed in accordance with the control-oriented flow.

[0062] FIG. 5A is a schematic diagram of an example of the shipping input screen 22.

[0063] When the order data is input, the shipping input reception unit 102b executes the shipping input process. The shipping input reception unit 102b displays the shipping input screen 22 on the monitor 114. The shipping input screen 22 is a screen for receiving input of shipping data. The shipping input reception unit 102b displays, on the shipping input screen 22, order data for which the "business flow" item included in the order data is a control-emphasized flow, among one or more order data registered in the order data DB 106b (see display field 22A). Therefore, the user inputs shipping data while referring to the order data entered in the control-emphasized flow. Note that, from the viewpoint of shipping operations, it is not necessary to distinguish between invoices based on a control-emphasized flow and invoices based on a business efficiency-emphasized flow. Therefore, the shipping input reception unit 102b can perform shipping processing for invoices based on a control-emphasized flow and invoices based on a business efficiency-emphasized flow all at once.

[0064] The user inputs shipping data by operating the input device 112 while viewing the shipping input screen 22. Assume that the user inputs the shipping data and then operates a registration button (not shown). The shipping input receiving unit 102b registers the shipping data input via the shipping input screen 22 in the shipping data DB 106e.

[0065] 5B and 5C are schematic diagrams showing an example of the data configuration of the shipping data DB 106e. As described above, in this embodiment, the shipping data DB 106e is composed of shipping header data 106f and shipping detail data 106g. FIG. 5B is a schematic diagram showing an example of the data configuration of the shipping header data 106f. FIG. 5C is a schematic diagram showing an example of the data configuration of the shipping detail data 106g.

[0066] The shipping header data 106f is a database that associates shipping numbers, shipping dates, and warehouses. The shipping detail data 106g is a database that associates shipping numbers, line numbers, products, quantities, order numbers, and line numbers.

[0067] The shipment input receiving unit 102b registers the portion of the shipping data received via the shipment input screen 22 that corresponds to the header in shipment header data 106f, and the portion that corresponds to the details in shipment detail data 106g. Therefore, when shipping data is entered via the shipment input screen 22 shown in Figure 5A, the data shown in Figures 5B and 5C are registered in the shipping header data 106f and the shipping detail data 106g. In the example shown in Figure 5A, the order data referenced on the shipment input screen 22 is order data based on the control-emphasis flow, and therefore the shipping data registered in the shipping data DB 106e is also data based on the control-emphasis flow.

[0068] FIG. 6A is a schematic diagram of an example of the second invoice input screen 24.

[0069] Once the shipping data is entered, the second invoice input screen display unit 102c executes the invoice input process. The second invoice input screen display unit 102c displays the second invoice input screen 24 on the monitor 114. The second invoice input screen 24 is a screen for accepting input of invoice data in the control-oriented flow.

[0070] The second invoice input screen display unit 102c displays at least a portion of the information included in the order data for which the item "business flow" included in the order data is a control-oriented flow, among one or more order data registered in the order data DB 106b, on the shipping input screen 22 (see display field 24A). Therefore, the second invoice input screen 24 displays data on vouchers related to the control-oriented flow, but does not display data on vouchers related to the business efficiency-oriented flow.

[0071] Furthermore, the second invoice input screen display unit 102c displays at least a portion of the shipping data corresponding to order data for which the "business flow" item included in the order data is a control-emphasized flow on the second invoice input screen 24. That is, the second invoice input screen display unit 102c displays at least a portion of the shipping data entered in the immediately preceding shipment input step on the second invoice input screen 24. FIG. 6A shows an example of shipping data such as the shipping number, shipping date, and warehouse displayed on the second invoice input screen 24.

[0072] The user inputs invoice data by operating the input device 112 while referring to the order data and shipping data input in the control-oriented flow. Figure 6A shows the state in which the foreign currency sales amount has been input for each item as invoice data (see display field 24A). By inputting the invoice data, the foreign currency invoice amount to the invoice recipient is determined. We will assume a scene in which the user inputs the foreign currency sales amount and then operates the register button (not shown).

[0073] The second invoice data output unit 102d registers the invoice data input via the second invoice input screen 24 in the invoice data DB 106h.

[0074] 6B and 6C are schematic diagrams showing an example of the data configuration of the invoice data DB 106h. As described above, in this embodiment, the invoice data DB 106h is composed of invoice header data 106i and invoice detail data 106j. FIG. 6B is a schematic diagram showing an example of the data configuration of the invoice header data 106i. FIG. 6C is a schematic diagram showing an example of the data configuration of the invoice detail data 106j.

[0075] The invoice header data 106i is a database that associates invoice numbers, business locations, shipping dates, expected sales dates, departments, billing destinations, and currencies. The invoice detail data 106j is a database that associates invoice numbers, line numbers, products, quantities, foreign currency sales amounts, shipping numbers, order numbers, and order line numbers.

[0076] The second invoice data output unit 102d registers the portion of the invoice data received via the second invoice input screen 24 that corresponds to the header in invoice header data 106i, and the portion that corresponds to the details in invoice detail data 106j. Therefore, by inputting invoice data via the second invoice input screen 24 shown in Figure 6A, the invoice data DB 106h will be in a state where the data shown in Figures 6B and 6C are registered. Furthermore, because the order data referenced on the second invoice input screen 24 is order data based on the control-emphasis flow, the invoice data registered in the invoice data DB 106h will also be data based on the control-emphasis flow.

[0077] Additionally, the second invoice data output unit 102d may create invoice data from the data received via the second invoice input screen 24, and print or output the data to the monitor 114. Through these processes, the invoice data is printed, i.e., a form is printed.

[0078] FIG. 7A is a schematic diagram of an example of the second sales input screen 26.

[0079] When the invoice data is input, the second sales input receiving unit 102e executes the sales input step. The second sales input receiving unit 102e performs export sales lump-sum accounting processing using the invoice data input in the immediately preceding invoice input step, and performs processing to determine sales accounting, the rate, and the Japanese currency amount based on the confirmed foreign currency invoice amount.

[0080] Specifically, the second sales input receiving unit 102e displays the second sales input screen 26 on the monitor 114. The second sales input screen 26 is a screen for receiving input of sales data in the control-oriented flow.

[0081] The second sales input reception unit 102e displays invoice data corresponding to order data in which the item "business flow" included in the order data is a control-oriented flow, among one or more order data registered in the order data DB 106b, on the second sales input screen 26. Therefore, the second sales input screen 26 displays data related to the control-oriented flow, but does not display data related to the business efficiency-oriented flow.

[0082] The user inputs sales data by operating the input device 112 while referring to the invoice data input in the control-oriented flow. The user inputs the officially confirmed foreign currency sales amount in the foreign currency sales amount display field. Figure 7A shows the state in which the rate and Japanese yen sales amount have been input as sales data. The input of the sales data confirms the rate and Japanese yen sales amount for the billing destination. Let us assume a scene in which the user inputs this sales data and then operates the registration button (not shown).

[0083] The second sales input receiving unit 102e registers the sales data input via the second sales input screen 26 in the sales data DB 106k.

[0084] 7B and 7C are schematic diagrams showing an example of the data structure of the sales data DB 106k. As described above, in this embodiment, the sales data DB 106k is composed of sales header data 106m and sales detail data 106n. FIG. 7B is a schematic diagram showing an example of the data structure of the sales header data 106m. FIG. 7C is a schematic diagram showing an example of the data structure of the sales detail data 106n.

[0085] The sales header data is a database that associates the sales number, business establishment, shipping date, sales date, department, customer, billing destination, currency, and rate. The sales detail data 106n is a database that associates the sales number, line number, warehouse, product, quantity, foreign currency sales amount, Japanese currency sales amount, invoice number, and line number.

[0086] The second sales input receiving unit 102e creates sales data from the data received via the second sales input screen 26 and registers it in the sales data DB 106k. When sales data is entered via the second sales input screen 26 shown in FIG. 7A, the data shown in FIGS. 7B and 7C is registered in the sales header data 106m and sales detail data 106n. In the example shown in FIG. 7A, the order data that references the invoice data includes "control-oriented" as an item in the "business flow" field, indicating a control-oriented flow. Therefore, the sales data registered in the sales data DB 106k is the sales data entered via the control-oriented flow, as shown in FIGS. 7B and 7C.

[0087] Next, the flow of processing by the control unit 102 in the business efficiency emphasis flow will be described.

[0088] In this embodiment, an example will be described in which the business efficiency-oriented flow is a business flow that manages the invoice document creation input process, which is the invoice input process in the control-oriented flow, at the timing between the order entry process and the shipping input process, and at the timing between the shipping input process and the sales input process. Note that the timing of the invoice document creation input process and the content of the invoice data can be set arbitrarily by the user.

[0089] 8A to 13B are explanatory diagrams of an example of the flow of processing by the control unit 102 in the business efficiency emphasis flow.

[0090] 8A is a schematic diagram of an example of the order entry screen 30. The order entry screen 30 is similar to the order entry screen 20.

[0091] First, the order input reception unit 102a executes the order input process. The order input reception unit 102a executes processing common to both the business efficiency-oriented flow and the control-oriented flow. The order input reception unit 102a displays the order input screen 30 on the monitor 114. The order input screen 30 is a screen for accepting input of order data, and is similar to the order input screen 20.

[0092] The user operates the input device 112 while viewing the order entry screen 30 to input order data via the order entry screen 30. The order data includes items that represent a business flow. The user inputs the designation of the business efficiency-oriented flow by specifying the order category of "business efficiency-oriented," which represents a business efficiency-oriented flow as the business flow (see display field 30A). By specifying the business efficiency-oriented flow, the order transaction is managed in accordance with the business efficiency-oriented flow.

[0093] Assume that the user inputs the order data and then operates a registration button (not shown). The order input receiving unit 102a registers the order data input via the order input screen 30 in the order data DB 106b.

[0094] 8B and 8C are schematic diagrams showing an example of the data structure of the order data DB 106b. Fig. 8B is a schematic diagram showing an example of the data structure of the order header data 106c. Fig. 8C is a schematic diagram showing an example of the data structure of the order detail data 106d.

[0095] The order input receiving unit 102a registers the header portion of the order data received via the order input screen 30 in order header data 106c, and the details portion in order detail data 106d. When order data is entered via the order input screen 30 shown in FIG. 8A, the order data DB 106b will contain the data shown in FIGS. 8B and 8C. The order detail data will also include an item representing the business flow, "Business Efficiency Emphasis," which indicates a business efficiency-oriented flow (see FIG. 8C). Therefore, export transactions related to orders identified by the order number corresponding to this item will be managed in accordance with the business efficiency-oriented flow.

[0096] 9A is a schematic diagram of an example of the first invoice input screen 34A. The first invoice input screen 34A is an example of the first invoice input screen 34, and is a screen displayed when the invoice document creation input process is executed between the order entry process and the shipping entry process in the business efficiency-oriented flow.

[0097] When the shipping data is input, the first invoice input screen display unit 102f executes the invoice document creation input process. The first invoice input screen display unit 102f displays the first invoice input screen 34A on the monitor 114B. The first invoice input screen 34A is a screen for accepting the input of invoice data in the business efficiency-oriented flow. In this embodiment, the input of invoice data is accepted twice at different times in the business efficiency-oriented flow. For this reason, as an example, the first invoice input screen 34A displayed when accepting the input of the first invoice data displays "Proforma Invoice" as the invoice classification, indicating that it is a provisional invoice.

[0098] The first invoice input screen display unit 102f extracts the order number of order data from one or more order data registered in the order data DB 106b, where the "Business Flow" field included in the order data is "Business Efficiency Emphasis," which indicates a business efficiency-oriented flow, and displays the extracted order number on the first invoice input screen 34A. Figure 9A shows an example of a state in which the referenced document number "JU001" is displayed as the order number. The first invoice input screen display unit 102f also displays at least some of the information included in the order data on the first invoice input screen 34A (see display field 33A). Therefore, the first invoice input screen 34A displays data related to the business efficiency-oriented flow, but not data related to the control-oriented flow. Furthermore, the shipment input process has not yet been performed at this stage. Therefore, the shipping number and shipping line number fields remain blank on the first invoice input screen display unit 102f.

[0099] The user inputs invoice data by operating the input device 112 while referring to the order data entered and displayed in the business efficiency-oriented flow. FIG. 9A shows the state in which the foreign currency sales amount has been entered for each item as invoice data (see display field 33A). By entering invoice data via the first invoice input screen 34A, the foreign currency invoice amount to the invoice recipient is provisionally determined. Furthermore, by operating the input device 112 while viewing the first invoice input screen 34A, the user can input multiple invoice data from the same shipping and order slip. Let us consider a scenario in which the user enters the foreign currency sales amount and then operates the register button (not shown).

[0100] The first invoice data output unit 102g registers the invoice data input via the first invoice input screen 34A in the invoice data DB 106h.

[0101] 9B and 9C are schematic diagrams showing an example of the data configuration of the invoice data DB 106h. As described above, in this embodiment, the invoice data DB 106h is made up of invoice header data 106i and invoice detail data 106j.

[0102] FIG. 9B is a schematic diagram showing an example of the data configuration of the invoice header data 106i. When the business flow is a business efficiency-oriented flow, the invoice header data 106i further includes an invoice classification. In detail, the invoice header data 106i is a database that associates invoice numbers, business establishments, invoice classifications, shipping dates, expected sales dates, departments, billing destinations, and currencies. FIG. 9C is a schematic diagram showing an example of the data configuration of the invoice detail data 106j. The invoice detail data 106j is a database that associates invoice numbers, line numbers, products, quantities, foreign currency sales amounts, shipping numbers, order numbers, and order line numbers.

[0103] The first invoice data output unit 102g registers the part of the invoice data received via the first invoice input screen 34A that corresponds to the header in invoice header data 106i, and registers the part that corresponds to the details in invoice detail data 106j.

[0104] By registering the provisional invoice data entered via the first invoice input screen 34A, the invoice data DB 106h will contain the data shown in Figures 9B and 9C. In particular, the invoice data entered via the first invoice input screen 34B is registered in the invoice detail data 106j in association with the invoice classification "1: Proforma Invoice." At this point, since shipping data for invoice number "IN001" has not yet been entered, no data has been registered in the shipping number and shipping line number fields. Furthermore, since the order data referenced on the first invoice input screen 34A is order data based on the business efficiency-oriented flow, the invoice data registered in the invoice data DB 106h will also be data based on the business efficiency-oriented flow.

[0105] The first invoice data output unit 102g may create invoice data from the data received via the first invoice input screen 34A, and print or output it to the monitor 114.

[0106] FIG. 10A is a schematic diagram of an example of the shipping input screen 32.

[0107] When provisional invoice data is input through the invoice document creation input process, the shipping input reception unit 102b executes the shipping input process. The shipping input reception unit 102b executes processing that is common to both the business efficiency-oriented flow and the control-oriented flow. The shipping input reception unit 102b displays a shipping input screen 32 on the monitor 114. The shipping input screen 32 is a screen for accepting input of order data, and is similar to the shipping input screen 22.

[0108] The shipment input screen 32 is a screen for accepting input of shipping data. The shipment input accepting unit 102b displays, on the shipment input screen 22, order data for which the item "business flow" included in the order data is a business efficiency-oriented flow, among one or more order data registered in the order data DB 106b (see display field 32A). Therefore, the user inputs shipping data while referring to the order data entered in the business efficiency-oriented flow.

[0109] In other words, if the item representing the business flow included in the order data indicates a business efficiency-oriented flow, the shipping data entered for that order data will be shipping data in the business efficiency-oriented flow. From the perspective of shipping operations, it is not necessary to distinguish between invoices based on the control-oriented flow and invoices based on the business efficiency-oriented flow. Therefore, the shipping input receiving unit 102b can process invoices based on both the control-oriented flow and the business efficiency-oriented flow in a single shipment.

[0110] The user inputs shipping data by operating the input device 112 while viewing the shipping input screen 32. Assume that the user inputs the shipping data and then operates a registration button (not shown). The shipping input receiving unit 102b registers the shipping data input via the shipping input screen 32 in the shipping data DB 106e.

[0111] 10B and 10C are schematic diagrams showing an example of the data structure of the shipping data DB 106e. Fig. 10B is a schematic diagram showing an example of the data structure of the shipping header data 106f. Fig. 10C is a schematic diagram showing an example of the data structure of the shipping detail data 106g.

[0112] The shipment input receiving unit 102b registers the part of the shipping data received via the shipment input screen 32 that corresponds to the header in shipment header data 106f, and registers the part that corresponds to the details in shipment detail data 106g.

[0113] 10A is registered, the shipping header data 106f will contain the data shown in Figures 10B and 10C. In addition, since the order data referenced on the shipping input screen 32 is order data based on the business efficiency-oriented flow, the shipping data registered in the shipping data DB 106e will also be data based on the business efficiency-oriented flow.

[0114] 11A is a schematic diagram of an example of the first invoice input screen 34B. The first invoice input screen 34B is an example of the first invoice input screen 34, and is a screen that is displayed when the invoice document creation input process is executed between the shipping input process and the sales input process.

[0115] Once the order data, provisional invoice data, and shipping data have been input, the first invoice input screen display unit 102f executes the invoice document creation input process. The first invoice input screen display unit 102f displays the first invoice input screen 34B on the monitor 114B. The first invoice input screen 34B is a screen for accepting the input of invoice data in the business efficiency-oriented flow. In this embodiment, the input of invoice data is accepted twice at different times in the business efficiency-oriented flow. For this reason, as an example, the first invoice input screen 34B displayed when invoice data is input for the second time displays "Commercial Invoice" as the invoice classification, indicating that it is a formal invoice.

[0116] The first invoice input screen display unit 102f displays, on the first invoice input screen 34B, at least a portion of the information contained in the order data, of one or more order data registered in the order data DB 106b, whose item "business flow" is "business efficiency emphasis," which indicates a business efficiency emphasis flow (see display field 35A). Therefore, the first invoice input screen 34B displays data related to the business efficiency emphasis flow, but does not display data related to the control emphasis flow.

[0117] Furthermore, the first invoice input screen display unit 102f displays, on the first invoice input screen 34B, at least a portion of the shipping data corresponding to order data for which the "Business Flow" item included in the order data is a business efficiency-oriented flow. That is, the first invoice input screen display unit 102f displays, on the first invoice input screen 34B, at least a portion of the shipping data entered in the immediately preceding shipment input step. FIG. 11A shows, as an example, the first invoice input screen 34B displaying shipping data such as the shipping number, shipping date, and shipping line number.

[0118] The user operates the input device 112 while referring to the order data and shipping data entered in the business efficiency-oriented flow to input official invoice data. FIG. 11A shows an example of a situation in which the user operates the input device 112 to change the foreign currency sales amount "$280.00" included in the order data in the business efficiency-oriented flow to "$300.00." By entering invoice data via the first invoice input screen 34B, the official foreign currency invoice amount to the invoice recipient is entered. Furthermore, by operating the input device 112 while viewing the first invoice input screen 34B, the user can enter multiple invoice data from the same shipping and order slip. Let us consider a situation in which the user operates the register button (not shown) after entering the foreign currency sales amount.

[0119] The first invoice data output unit 102g registers the invoice data input via the first invoice input screen 34B in the invoice data DB 106h.

[0120] 11B and 11C are schematic diagrams showing an example of the data structure of the invoice data DB 106h. Fig. 11B is a schematic diagram showing an example of the data structure of the invoice header data 106i. Fig. 11C is a schematic diagram showing an example of the data structure of the invoice detail data 106j.

[0121] By further registering the formal invoice data entered via the first invoice input screen 34B, the invoice data DB 106h will be in the state shown in Figures 11B and 11C. Specifically, the invoice data entered via the first invoice input screen 34B is registered in the invoice header data 106i in association with the invoice classification "2: Commercial Invoice." At this point, shipping data for invoice number "IN002" has already been entered in the previous step. Therefore, values ​​corresponding to the shipping data are registered in the shipping number and shipping line number fields corresponding to the invoice number of the invoice data in the invoice detail data 106j (see Figure 11C). Furthermore, because the order data referenced on the first invoice input screen 34B is order data based on the business efficiency-oriented flow, the invoice data registered in the invoice data DB 106h will also be data based on the business efficiency-oriented flow.

[0122] FIG. 12A is a schematic diagram of an example of the first sales input screen 36.

[0123] When the invoice data is input, the first sales input screen display unit 102h, the consistency check result display unit 102i, and the sales output unit 102j execute the sales input process in the business efficiency-oriented flow. The first sales input screen display unit 102h displays the first sales input screen 36 on the monitor 114. The first sales input screen 36 is a screen for accepting input of sales data in the business efficiency-oriented flow.

[0124] The first sales input screen display unit 102h displays, on the first sales input screen 36, information contained in order data for which the "business flow" item included in the order data is a business efficiency-oriented flow, among one or more order data registered in the order data DB 106b. Therefore, the first sales input screen 36 displays details regarding the business efficiency-oriented flow (see display field 36A), but does not display details regarding the business efficiency-oriented flow. In addition, the first sales input screen 36 displays the foreign currency sales amount "$280.00" included in the order data entered via the order input screen 30.

[0125] The user inputs sales data by operating the input device 112 while referring to the order data entered in the business efficiency-oriented flow. The user inputs the officially confirmed foreign currency sales amount in the foreign currency sales amount display field. Figure 12A shows an example in which the displayed foreign currency sales amount "$280.00" has been changed to "$300.00" by the user's operation instruction of the input device 112 (see display field 36B). The input of sales data confirms the rate for the billing destination and the Japanese currency sales amount. Let us consider a scene in which the user operates the register button 36C after inputting this sales data.

[0126] The consistency check result display unit 102i checks the consistency between the sales data and the invoice data.

[0127] In the business efficiency-oriented flow, the timing of inputting and outputting invoice data may be before the shipment input process, after the shipment input process, or both before and after the shipment input process. Therefore, in the business efficiency-oriented flow, the user can input and output invoice data (output reports) at any time. On the other hand, in the business efficiency-oriented flow, there are cases where the sales data, which is the actual results generated by the business, is not consistent with the invoice data. For this reason, the consistency check result display unit 102i checks the consistency between the sales data and the invoice data when sales are recorded in the sales input process, which is the final process in the business efficiency-oriented flow.

[0128] In detail, when the registration button 36C on the first sales input screen 36 is operated, the consistency check result display unit 102i checks whether the invoice entry, which is the foreign currency sales amount represented by the input invoice data, matches the sales entry, which is the foreign currency sales amount represented by the sales data input via the first sales input screen 36. Then, the consistency check result display unit 102i displays the check result on the monitor 114.

[0129] 12B is a schematic diagram of an example of the invoice recording voucher consistency check screen 38. The consistency check result display unit 102i displays the invoice recording voucher consistency check screen 38, including the check results, on the monitor 114. The invoice recording voucher consistency check screen 38 includes a register button 38B and a cancel button 38C. The register button 38B is a button operated by the user when instructing the registration of sales data. The cancel button 38C is a button operated by the user when returning to the first sales input screen 36.

[0130] As shown in FIG. 12B, assume that the invoice amount represented by the provisional invoice data, invoice classification "1: Pro forma Invoice," is "$280.00" and the sales amount is "$300.00." In this case, the value obtained by subtracting the sales amount from the invoice amount is "$-20.00." In this case, for example, the consistency check result display unit 102i displays "$-20.00" as the foreign currency amount difference corresponding to the invoice number of the invoice classification on the invoice count slip consistency check screen 38 (see display field 38A). Through this display process, the consistency check result display unit 102i displays the check result.

[0131] Also, as shown in FIG. 12B, assume that the invoice amount represented by the invoice classification "2: Commercial Invoice," which is the official invoice data, is "$300.00" and the sales amount is "$300.00." In this case, the value obtained by subtracting the sales amount from the invoice amount is "$0.00." In this case, for example, the consistency check result display unit 102i displays "$0.00" as the foreign currency amount difference corresponding to the invoice number of the invoice classification on the invoice count slip consistency check screen 38 (see display field 38A). Through this display process, the consistency check result display unit 102i displays the check result.

[0132] If the difference between the invoice entry and the sales entry is zero, then they can be said to be consistent. In the example shown in Figure 12B, the invoice entry represented by the invoice classification "1: Proforma Invoice," which is provisional invoice data, does not match the sales entry and is therefore not consistent. On the other hand, the invoice entry represented by the invoice classification "2: Commercial Invoice," which is formal invoice data, matches the sales entry and is therefore consistent.

[0133] Therefore, by visually checking the confirmation results shown in Figure 12B, the user can easily check the consistency between invoice accounting and sales accounting for each of the invoice classification "1: Proforma Invoice", which is provisional invoice data, and the invoice classification "2: Commercial Invoice", which is formal invoice data.

[0134] In the example shown in FIG. 12B, when the user operates the register button 38B, the sales output unit 102j registers the sales data entered via the first sales input screen 36 in the sales data DB 106k. That is, the sales output unit 102j registers the sales data that has been confirmed to be consistent by the consistency check result display unit 102i in the sales data DB 106k. Furthermore, if the sales data is consistent with the invoice entry corresponding to the invoice classification "2: Commercial Invoice," which is the official invoice data, the sales output unit 102j registers the sales data entered via the first sales input screen 36 in the sales data DB 106k.

[0135] Figures 12C and 12D are schematic diagrams showing an example of the data structure of the sales data DB 106k. Figure 12C is a schematic diagram showing an example of the data structure of the sales header data 106m. Figure 12D is a schematic diagram showing an example of the data structure of the sales detail data 106n. Figures 12C and 12D show the state in which consistent sales data entered via the first sales input screen 36 shown in Figure 12A has been registered in the sales data DB 106k.

[0136] The sales output unit 102j creates sales data from the data received via the first sales input screen 36 and registers it in the sales data DB 106k. Because the order data that references the invoice data includes "business efficiency emphasis" as an item "business flow," which indicates a business efficiency emphasis flow, the sales data registered in the sales data DB 106k is the sales data entered using the business efficiency emphasis flow, as shown in Figures 12C and 12D.

[0137] As described above, the sales output unit 102j registers the sales data that has been confirmed to be consistent by the consistency check result display unit 102i in the sales data DB 106k. If the consistency check result display unit 102i derives a confirmation result indicating inconsistency, the sales output unit 102j may be configured not to register the sales data even if the user operates the register button 38B in response to an operational instruction.

[0138] FIG. 13A is a schematic diagram showing an example of the first sales input screen 36 in a state in which sales data that is inconsistent with the invoice amount has been entered. For example, assume that the first sales input screen display unit 102h displays the foreign currency sales amount "$280.00" included in the order data entered via the order input screen 30 (see display field 36B). Then, assume that the user operates the register button 36C without changing the foreign currency sales amount from "$280.00" to "$300.00" as sales data. Also assume that the invoice amount included in the corresponding official invoice data is "$300.00."

[0139] When the registration button 36C on the first sales input screen 36 is operated, the consistency check result display unit 102i checks whether the invoice entry matches the sales entry, which is the foreign currency sales amount represented by the sales data entered via the first sales input screen 36. The consistency check result display unit 102i then displays the check result on the monitor 114.

[0140] 13B is a schematic diagram of an example of the invoice recording voucher consistency check screen 38. The consistency check result display unit 102i displays the invoice recording voucher consistency check screen 38 including the check results on the monitor 114.

[0141] As shown in Figure 13B, assume that the invoice amount represented by the provisional invoice data, invoice classification "1: Pro forma Invoice," is "$280.00" and the sales amount is "$280.00." In this case, the value obtained by subtracting the sales amount from the invoice amount is "$0.00." In this case, the consistency check result display unit 102i displays "$0.00" on the invoice accounting slip consistency check screen 38 as the difference in foreign currency amount corresponding to the invoice number of that invoice classification (see display field 38A).

[0142] Also, as shown in FIG. 13B, assume that the invoice amount represented by the invoice classification "2: Commercial Invoice," which is the official invoice data, is "$300.00" and the sales amount is "$280.00." In this case, the value obtained by subtracting the sales amount from the invoice amount is "$20.00." In this case, the consistency check result display unit 102i displays "$20.00" as the foreign currency amount difference corresponding to the invoice number of the invoice classification on the invoice accounting slip consistency check screen 38 (see display field 38A). Through these display processes, the consistency check result display unit 102i displays the check results.

[0143] If the difference between the invoice entry and the sales entry is zero, then they can be said to be consistent. In the example shown in Figure 13B, the invoice entry represented by the invoice classification "1: Proforma Invoice," which is provisional invoice data, matches the sales entry and is consistent. On the other hand, the invoice entry represented by the invoice classification "2: Commercial Invoice," which is formal invoice data, does not match the sales entry and is not consistent.

[0144] 13B, when the user operates the registration button 38B, the sales output unit 102j does not register the sales data entered via the first sales input screen 36 in the sales data DB 106k. For example, the sales output unit 102j displays an error message indicating that registration is not possible because the official invoice entry and the sales entry do not match.

[0145] By visually checking the invoice recording voucher consistency check screen 38, the user can determine whether the invoice recording and sales recording included in the invoice recording voucher consistency check screen 38 are inconsistent. If they are inconsistent, the user operates the cancel button 38C. When the cancel button 38C is operated, the first sales input screen display unit 102h displays the first sales input screen 36 (see FIG. 13A). This allows the user to modify the foreign currency sales amount, etc., via the first sales input screen 36.

[0146] Next, an example of the flow of information processing executed by the export transaction management device 100 of this embodiment will be described.

[0147] FIG. 14 is a flowchart showing an example of the flow of information processing executed by the export transaction management device 100 of this embodiment.

[0148] The order input reception unit 102a displays the order input screen 20 on the monitor 114 (step S100). The order input reception unit 102a determines whether the business flow specified via the order input screen 20 is a control-oriented flow or a business efficiency-oriented flow (step S102).

[0149] If it is determined that the flow is control-oriented (step S102: Yes), the order entry acceptance unit 102a, the shipping entry acceptance unit 102b, the second invoice entry screen display unit 102c, and the second sales entry acceptance unit 102e execute processing according to the control-oriented flow (step S104), and then this routine ends.

[0150] On the other hand, if it is determined that the flow is one that prioritizes business efficiency (step S102: No), the order entry acceptance unit 102a, shipping entry acceptance unit 102b, first invoice entry screen display unit 102f, first invoice data output unit 102g, first sales entry screen display unit 102h, consistency check result display unit 102i, and sales output unit 102j execute processing in accordance with the flow that prioritizes business efficiency (step S106). Then, this routine ends.

[0151] As described above, the export transaction management device 100 of this embodiment is an export transaction management device that includes a control unit 102 and is used to manage operations related to export transactions. The control unit 102 includes an order entry receiving unit 102a, a first invoice entry screen display unit 102f, and a first invoice data output unit 102g. The order entry receiving unit 102a receives, via an order entry screen 30 (order entry screen 20) for receiving input of order data in the order entry process, a designation of either a control-emphasized flow, which is a workflow that manages operations related to the order entry process, shipment entry process, invoice entry process, and sales entry process in that order, or a workflow that manages the invoice document creation entry process, which is an invoice entry process in the control-emphasized flow, at least one of the timings between the order entry process and the shipment entry process and between the shipment entry process and the sales entry process. When the first sales input screen display unit 102h receives the designation of the business efficiency-oriented flow as the business flow, it displays the first invoice input screen 34 for receiving input of invoice data at least one of the timings between the order entry step and the shipment entry step, and between the shipment entry step and the sales entry step. The first invoice data output unit 102g outputs the invoice data inputted via the first invoice input screen 34.

[0152] Conventional export transaction systems use a fixed workflow, making it difficult to accommodate workflows with different process orders.

[0153] Specifically, unlike domestic transactions, export transactions may involve different timing and personnel for shipping and invoice issuance, and the order of processes may also differ. However, due to the nature of ERP, procedures such as processing and report issuance must be performed in accordance with the system flow. For this reason, with conventional technology, it was necessary to follow a fixed processing flow even in cases where system registration was not required for practical operations.

[0154] On the other hand, the export transaction management device 100 of this embodiment accepts the designation of either a control-oriented flow or a business efficiency-oriented flow, and executes processing in accordance with the designated business flow.

[0155] Therefore, the export transaction management device 100 of this embodiment can accommodate business flows with different process orders for business related to export transactions.

[0156] In addition, the export transaction management device 100 of this embodiment executes a business flow according to the user's specifications, allowing the user to select the desired business flow depending on whether they place importance on control or business efficiency, etc.

[0157] Furthermore, in the export transaction management device 100 of this embodiment, the user can select two business flows: a control-oriented flow and a business efficiency-oriented flow. Therefore, the export transaction management device 100 of this embodiment makes it possible for a company that operates multiple businesses to separate business flows by business or department.

[0158] Furthermore, the user can select the most suitable workflow, thereby improving work efficiency.

[0159] For example, in a control-oriented flow, transaction-related information such as quantity and amount can be determined in the invoice input process, making it possible to match invoice and sales entries in one go in the sales input process.

[0160] Furthermore, in the business efficiency-oriented flow, the invoice document creation and input process can be executed at any time desired by the user, regardless of the timing of shipping operations. Furthermore, in the export transaction management device 100 of this embodiment, in the sales input process of the business efficiency-oriented flow, the consistency check result display unit 102i checks the consistency between sales accounting based on sales data and invoice accounting based on invoice data, and displays the check result. Therefore, by checking consistency in the sales input process, which is the final process of the business efficiency-oriented flow, the export transaction management device 100 of this embodiment can prevent discrepancies from occurring between sales accounting and invoice accounting.

[0161] [2. 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.

[0162] 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.

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

[0164] 3. 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.

[0165] 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.

[0166] 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.

[0167] Furthermore, with regard to the export transaction control 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.

[0168] For example, all or any part of the processing functions of the export transaction control device 100, particularly the processing functions performed by the control unit 102, may be implemented by a CPU and a program interpreted and executed by the CPU, or may be implemented 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 export transaction control device 100 as needed. That is, a computer program is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive) for working with the OS to issue instructions to the CPU and perform various processes. This computer program is executed by being loaded into RAM and cooperates with the CPU to form the control unit.

[0169] This computer program may also be stored in an application program server connected to the export transaction control device 100 via any network, and all or part of it may be downloaded as needed.

[0170] 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.

[0171] Furthermore, a "program" is a data processing method written in any language or description method, and does not matter whether it is in the form of 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 this embodiment, as well as the installation procedure after reading, can use well-known configurations and procedures.

[0172] The various databases stored in the memory unit 106 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.

[0173] The export transaction management device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device to which any peripheral device is connected. The export transaction management device 100 may also be realized by installing software (including programs or data) that causes the device to perform the processing described in this embodiment.

[0174] 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. [Explanation of symbols]

[0175] 100 Export transaction control device 102 Control section 102a Order entry reception section 102c Second invoice input screen display section 102f First invoice input screen display section 102g First invoice data output section 102h 1st sales input screen display section 102i Consistency check result display section

Claims

1. An export transaction management device for managing operations related to export transactions, comprising a control unit, The control unit A control-oriented flow is a workflow that manages the operations related to the Order Entry Process, Shipping Entry Process, Invoice Entry Process, and Sales Entry Process in that order. a business efficiency-oriented flow that is a business flow that manages the invoice document creation input process, which is the invoice input process in the control-oriented flow, at least one of the timings between the order entry process and the shipping entry process and the timing between the shipping entry process and the sales entry process; an order entry receiving unit that receives a designation of any one of the business flows via an order entry screen for receiving entry of order data in the order entry step; a first invoice input screen display unit that displays a first invoice input screen for receiving input of invoice data at least one of the timings between the order entry step and the shipment entry step and the timing between the shipment entry step and the sales entry step when the business efficiency emphasis flow is designated as the business flow; a first invoice data output unit that outputs the invoice data input via the first invoice input screen; An export transaction management device comprising:

2. a first sales input screen display unit that displays a first sales input screen for receiving input of sales data in the sales input step when the business efficiency-oriented flow is designated as the business flow; a consistency check result display unit that displays a check result for checking the consistency between the sales data input via the first sales input screen and the invoice data output by the first invoice data output unit; The export transaction control device according to claim 1 , comprising:

3. The order data includes an item representing the business flow for which the designation has been accepted.

2. The export transaction control device according to claim 1.

4. The first invoice input screen display unit Among the one or more pieces of order data, the order data in which the business flow represented by the items is the business efficiency-oriented flow is displayed on the first invoice input screen.

4. The export transaction control device according to claim 3.

5. a second invoice input screen display unit that displays a second invoice input screen for receiving input of the invoice data at a timing between the shipment input step and the sales input step when the control-emphasized flow is designated as the business flow, The second invoice input screen display unit Among the one or more pieces of order data, the order data in which the business flow represented by the items is the control-emphasized flow is displayed on a second invoice input screen.

4. The export transaction control device according to claim 3.

6. An export transaction management method executed by an export transaction management device for managing operations related to export transactions, the export transaction management method comprising: Executed by the control unit, A control-oriented flow is a workflow that manages the operations related to the Order Entry Process, Shipping Entry Process, Invoice Entry Process, and Sales Entry Process in that order. a business efficiency-oriented flow that is a business flow that manages the invoice document creation input process, which is the invoice input process in the control-oriented flow, at least one of the timings between the order entry process and the shipping entry process and the timing between the shipping entry process and the sales entry process; receiving a designation of any one of the business flows via an order entry screen for receiving input of order data in the order entry step; when the business efficiency-oriented flow is designated as the business flow, displaying a first invoice input screen for receiving input of invoice data at least one of the timings between the order entry step and the shipment entry step and the timing between the shipment entry step and the sales entry step; outputting the invoice data input via the first invoice input screen; Export trade control methods, including:

7. An export transaction management program executed by an export transaction management device for managing operations related to export transactions, the export transaction management program comprising: Executed by the control unit, A control-oriented flow is a workflow that manages the operations related to the Order Entry Process, Shipping Entry Process, Invoice Entry Process, and Sales Entry Process in that order. a business efficiency-oriented flow that is a business flow that manages the invoice document creation input process, which is the invoice input process in the control-oriented flow, at least one of the timings between the order entry process and the shipping entry process and the timing between the shipping entry process and the sales entry process; receiving a designation of any one of the business flows via an order entry screen for receiving input of order data in the order entry step; when the business efficiency-oriented flow is designated as the business flow, displaying a first invoice input screen for receiving input of invoice data at least one of the timings between the order entry step and the shipment entry step and the timing between the shipment entry step and the sales entry step; outputting the invoice data input via the first invoice input screen; Export trade control programs, including:

Images