Business support device, business support method, and business support program

Abstract

This reduces the workload on the person in charge, as well as the risk of input errors and omissions in accounting. [Solution] The acquisition unit acquires the work ID and the work type code associated with the work ID. The data generation unit, based on the work standard code that indicates the criteria for recording sales for the work, refers to a storage unit that stores a work accounting classification that includes the work type code and one or two date items to be set as the sales recording date for the work, and sets one of the date items related to the work type from the one or two date items included in the work accounting classification as the sales recording date for the work. When an implementation date is entered in a date item corresponding to one of the multiple date items for entering the implementation dates of multiple steps in the work, the unit generates work data that includes the implementation date as the sales recording date, associated with the work ID. The output control unit outputs the work data to the output target device.

Description

Technical Field

[0001] The present invention relates to a business support device, a business support method, and a business support program.

Background Art

[0002] Patent Document 1 (Japanese Patent Application Laid-Open No. 2022-059878) discloses a monthly sales accounting device used in the logistics industry, which creates journal data of provisional sales accounting data in cooperation with an accounting system for billing details data not billed in the current month.

[0003] This monthly sales accounting device includes sales processing means for inputting sales detail data including data on order numbers, line numbers, sales details, amounts, working days, and provisional sales accounting dates, and sales accounting processing means for creating a journal recorded as provisional sales in cooperation with an accounting system without performing a billing process for details where the current month is not the billing month based on the working day for the sales detail data. This enables easy monthly sales accounting processing in accordance with the new revenue recognition criteria.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] However, in the logistics industry, since a single contract operation includes multiple procedures, it is necessary to select a date item to be set as the sales accounting date according to the operation form from the date items corresponding to the implementation dates of the multiple procedures, which places a heavy workload on the person in charge. In addition, there are problems such as input errors and omissions in the sales accounting date by the person in charge, and an increase in the workload of the person in charge due to the correction work of the sales accounting date.

[0006] Therefore, the present invention has been made in view of the above-mentioned problems, and aims to provide a business support device, a business support method, and a business support program that reduce the workload of the person in charge and reduce the risk of input errors and accounting omissions by the person in charge. [Means for solving the problem]

[0007] To solve the above-mentioned problems and achieve the objective, the business support device according to the present invention comprises: an acquisition unit that acquires a work ID for identifying a task and a work type code for identifying the form of the task, which is associated with the work ID; a storage unit that stores a work accounting classification which includes a work type code and one or two date items to be set as the sales accounting date for the task, based on a work standard code which is associated with the work type code and indicates the criteria for recording sales of the task; a data generation unit that sets one of the one or two date items included in the work accounting classification that is related to the form of the task as the sales accounting date for the task; and when an implementation date is entered in a date item corresponding to one of the multiple date items for inputting the implementation dates of multiple steps in the task, it generates work data which includes the implementation date as the sales accounting date, associated with the work ID; and an output control unit that outputs the work data to an output target device.

[0008] Furthermore, in order to solve the above-mentioned problems and achieve the objective, the business support method according to the present invention includes an acquisition step in which an acquisition unit acquires a work ID for identifying a work and a work type code for identifying the form of work associated with the work ID; a data generation step in which a data generation unit, based on a work standard code that indicates the criteria for recording sales of a work associated with the work type code, refers to a storage unit that stores a classification including a work type code and one or two date items to be set as the sales recording date of a work associated with the work standard code, sets one of the one or two date items included in the classification that relates to the form of work as the sales recording date of the work, and when the implementation date is entered in the date item corresponding to one of the multiple date items for inputting the implementation dates of multiple procedures in the work, generates work data that includes the implementation date as the sales recording date associated with the work ID; and an output control step in which an output control unit outputs the work data to an output target device.

[0009] Furthermore, in order to solve the above-mentioned problems and achieve the objectives, the business support program according to the present invention functions as an acquisition unit that acquires a work ID for identifying a task and a work type code for identifying the form of the task, which is associated with the work ID; a storage unit that stores a classification including a work type code and one or two date items to be set as the sales recording date for the task, which is associated with the work type code, based on a work standard code that indicates the criteria for recording sales of the task, which is associated with the work type code; sets one of the one or two date items included in the classification that is related to the form of the task as the sales recording date for the task; a data generation unit that generates work data including the implementation date as the sales recording date, associated with the work ID, when an implementation date is entered in a date item that corresponds to one of the multiple date items for inputting the implementation dates of multiple steps in the task; and an output control unit that outputs the generated work data to an output target device. [Effects of the Invention]

[0010] This invention reduces the workload on the person in charge, and also reduces the risk of input errors and accounting omissions by the person in charge. [Brief explanation of the drawing]

[0011] [Figure 1] Figure 1 is a block diagram showing the hardware configuration of a business support device according to an embodiment. [Figure 2] Figure 2 shows an example of a work style master. [Figure 3] Figure 3 shows an example of a work standards master. [Figure 4] Figure 4 shows an example of work data stored in the work data storage unit. [Figure 5] Figure 5 shows another example of work data stored in the work data storage unit. [Figure 6] Figure 6 shows an example of work performance data stored in the work performance data storage unit. [Figure 7] Figure 7 shows an example of billing details data stored in the billing details data storage unit. [Figure 8] Figure 8 shows an example of sales accounting data stored in the sales accounting data storage unit. [Figure 9] Figure 9 is a diagram illustrating the operation flow of the business support device according to this embodiment. [Figure 10] Figure 10 shows an example of a new registration screen. [Figure 11] Figure 11 shows an example of a work performance screen. [Figure 12] Figure 12 shows an example of a data inquiry screen. [Figure 13] Figure 13 shows an example of a billing statement creation screen. [Modes for carrying out the invention]

[0012] Hereinafter, a business support device according to an embodiment to which the present invention is applied will be described in detail based on the drawings. Note that the present invention is not limited to the following embodiments.

[0013] [Overview] Conventionally, in the logistics industry, a single contract operation includes multiple procedures, and the criteria for recording sales differ depending on the operation form. For example, such criteria include the implementation dates of the procedures included in the above operations, such as the landing permission date of ship cargo, the confirmation date of warehouse receipt, the date of entry and departure from the port, the delivery performance date, and the receipt performance date. When entering sales data into the system, the person in charge determines which criterion to adopt according to the operation form and enters the date for the sales recording date.

[0014] Therefore, there is a problem that input errors and omissions in the sales recording date are likely to occur by the person in charge, and the workload of the person in charge increases due to the correction work of the sales recording date.

[0015] Therefore, as a result of intensive studies, the inventors of the present application found that by registering the operation form and the sales recording criteria in the master in advance, it is possible to set the date item corresponding to the form of the operation as the sales recording date by referring to the master, so that it is considered that there is no need for the person in charge to judge and input the date item to be adopted for the sales recording date.

[0016] In addition, the inventors of the present application considered that by inputting the implementation dates of a plurality of procedures included in the operation by the person in charge, it is possible to obtain the input data of the date item adopted as the sales recording date, so that the sales recording data of the operation can be created easily and accurately.

[0017] Based on the above, in this embodiment, when the business support device obtains a work type code, it refers to a storage unit that stores the work type code and the work accounting category associated with the work standard code, based on the work standard code associated with the work type code, sets one of the one or two date items included in the work accounting category that is related to the type of work as the sales accounting date for that work, and when an implementation date is entered into a date item that corresponds to one of the multiple date items for entering the implementation dates of multiple steps in the work, it generates work data that includes the implementation date as the sales accounting date, associated with the work ID.

[0018] This reduces the workload on the person in charge, as well as the risk of input errors and omissions in accounting.

[0019] [composition] (Hardware configuration) Figure 1 is a block diagram showing the hardware configuration of the business support device 1 according to an embodiment. As shown in Figure 1, the business support device 1 of this embodiment includes a storage unit 2, a control unit 3, a communication interface unit 4, and an input / output interface unit 5.

[0020] The input / output interface unit 5 is connected to an input device 6 and an output device 7. The output device 7 may be a display unit such as a monitor device (including a home television), a printing device, or a speaker device. The input device 6 may be a keyboard device, a mouse device, a microphone device, or a monitor device that works in conjunction with a mouse device to provide a pointing device function.

[0021] The communication interface unit 4 is connected to a network such as a wide-area network like the Internet or a private network like a LAN (Local Area Network). A server device 11 is connected to the network.

[0022] For the memory unit 2, a storage device such as ROM (Read Only Memory), RAM (Random Access Memory), HDD (Hard Disk Drive), or SSD (Solid State Drive) can be used. The memory unit 2 stores a business support program that reduces the workload of the person in charge and mitigates the risk of input errors and accounting omissions by the person in charge.

[0023] Furthermore, the memory unit 2 is equipped with the following memory areas: a work type master 21, a work standard master 22, a work data storage unit 23, a work performance data storage unit 24, a billing details data storage unit 25, and a sales accounting data storage unit 26. The information in the memory unit 2 may be entered by the person in charge (also called a user) into the input device 6, or it may be obtained from a server device 11 or the like via the network. The method of inputting to the input device 6 is not particularly limited.

[0024] Work Pattern Master 21 is a table that describes the work pattern code, the name of the work pattern, and the work standard code. The work pattern code is a code used to identify the type of work. The work standard code is a code that indicates the basis for recording the revenue of the work (hereinafter also referred to as the work standard). Here, the work refers to work related to logistics operations and includes multiple procedures.

[0025] The work standard is the date on which the final step of the work is performed, in other words, the date on which the closing step of the work is performed, which is the so-called work completion date. For example, in logistics operations related to imports, if the work is "import warehouse customs clearance," the multiple steps include port entry, loading (also called unloading), warehouse entry (referring to transportation to a bonded warehouse), and customs clearance. The basis for recording sales for the work related to this "import warehouse customs clearance" is the "warehouse entry confirmation date," which is the completion date of the work.

[0026] Figure 2 shows an example of a work type master 21. As shown in Figure 2, the work type master 21 contains, for example, a work type code, a work type name, and a work standard code. The work type name indicated by the work type code "1000" is the aforementioned "Import Warehouse Customs Clearance," and the work standard code "02" is associated with this "Import Warehouse Customs Clearance." "Import Warehouse Customs Clearance" is the process of transporting goods imported by air or sea to a bonded warehouse with the approval of the customs director, and then carrying out customs clearance procedures after the goods are placed in the warehouse.

[0027] Furthermore, the work type names indicated by work type codes "1090" and "2090" are "Air Import" and "Air Export," respectively, and work standard code "01" is associated with "Air Import" and "Air Export."

[0028] "Air import" refers to the unloading of goods imported by air transport, and "air export" refers to the loading of goods exported by air transport. The work type code "2000" is "export warehouse customs clearance," and this "export warehouse customs clearance" is associated with work standard code "03." "Export warehouse customs clearance" is the process of transporting goods to a bonded warehouse, storing them in the warehouse, clearing customs, and loading them onto an airplane or ship. The work type code "7000" is "truck transport," and this "truck transport" is associated with work standard code "04."

[0029] "Truck transport" is the operation of transporting imported goods that have gone through customs procedures to the delivery destination. The operation type code "9999" indicates the operation type name "Other," and this "Other" is associated with the operation standard code "06." "Other" is selected when the user sets the revenue recognition date for the operation. For example, if another operation type code is already selected, selecting "Other" will make it possible to add an operation type and allow the user to set the revenue recognition date for the operation.

[0030] The Work Standards Master 22 is a table that describes the work standard code, the name of the work standard, and the work accounting classification. The name of the work standard is the name that represents the date on which the closing procedure for the work is carried out, and is also referred to as the date item below. The work accounting classification is a classification used to determine which of the date items related to multiple business types will be set as the sales accounting date for the work. The work accounting classification includes one or two date items that will be set as the sales accounting date for the work.

[0031] Figure 3 shows an example of a work standard master 22. As shown in Figure 3, the work standard master 22 contains, for example, a work standard code, a work standard name, and a work accounting category. The work standard name indicated by the work standard code "01" is "approval date," and this "approval date" is associated with the work accounting category "A."

[0032] The "permission date" is the date on which permission is granted to unload cargo imported by air or sea from the aircraft or ship, or the date on which permission is granted to load cargo exported by air or sea onto the aircraft or ship. When the user enters a work type code, the data generation unit 32, described later, refers to the work type master 21 and the work standard master 22 and sets a date item as the sales recording date for the work based on the acquired work accounting classification.

[0033] Furthermore, the work standard code "02" is associated with the work standard name "Warehouse Receipt Confirmation Date," and work accounting category "B" is associated with this "Warehouse Receipt Confirmation Date." The "Warehouse Receipt Confirmation Date" is the date on which customs clearance procedures for imported goods delivered to the bonded warehouse are completed.

[0034] The work standard code "03" is named "Arrival / Departure Date," and this "Arrival / Departure Date" is associated with work accounting category "C." In other words, work accounting category "C" includes two date items: "Arrival Date" and "Departure Date." The work standard code "04" is named "Delivery Completion Date," and this "Delivery Completion Date" is associated with work accounting category "D." The "Delivery Completion Date" is the date on which the imported goods were transported by truck to the destination and delivery was completed.

[0035] The work standard code "06" indicates the work standard name "Manual Input," and this "Manual Input" is associated with the work accounting category "Z." "Manual Input" is any date entered by the user as the sales accounting date.

[0036] The work data storage unit 23 stores work IDs that identify a work, along with work type codes and sales recording dates. Figure 4 shows an example of work data stored in the work data storage unit 23.

[0037] As shown in Figure 4, the work data may be stored in the work data storage unit 23 in two separate tables. For example, the work data may include a table describing the work ID and the sales recording date (see Figure 4(a)) and a table describing the work ID and the work type code (see Figure 4(b)).

[0038] Figure 5 shows another example of work data stored in the work data storage unit 23. As shown in Figure 5, the work data may also be a table that associates work ID with work type code and sales recording date. The work data is generated by the data generation unit 32, which will be described later. The specific operation will be described later.

[0039] The work performance data storage unit 24 stores work performance data for managing the progress of work. For example, the work performance data storage unit 24 stores work performance data in a table format, which is associated with the work ID and has multiple date fields for entering the dates on which multiple steps in a task were performed.

[0040] Figure 6 shows an example of work performance data stored in the work performance data storage unit 24. As shown in Figure 6, the work performance data storage unit 24 stores work performance data that is associated with the work ID and includes multiple date items such as departure date, arrival date, delivery date, warehouse delivery confirmation date, permission date, and delivery date.

[0041] The billing details data storage unit 25 stores billing details data in which the date of the sales recording date included in the work data (see Figure 5) is used as the detail recording date, and the work ID is associated with the detail recording date, one or more billing items, and the billing amount for each of those one or more billing items.

[0042] One or more claims included in the billing details data may include a claim code for identifying the claim and the claim name indicated by the claim code, or it may include only the claim name, or only the claim code.

[0043] The storage unit 2 stores a claim master table (not shown in Figure 1) which contains the claim code, claim name, and invoice amount, and the data generation unit 32, which will be described later, generates invoice detail data by referring to the claim master.

[0044] Figure 7 shows an example of billing detail data stored in the billing detail data storage unit 25. As shown in Figure 7, the billing detail data includes, for example, a work ID, a line number (line No.), a claim item code, a detail recording date, and a billing amount (amount (yen)).

[0045] Invoice detail data is created, for example, using a transfer table, and the work ID and detail recording date are transferred from the "Work ID" and "Sales Recording Date" fields of the source data, which is the work data (see Figure 5).

[0046] Furthermore, the storage unit 2 stores a customer information master table (not shown in Figure 1) which contains customer ID, customer name, billing address, billing method, and currency unit, and the data generation unit 32, which will be described later, refers to this master table to set the currency unit for the billing amount.

[0047] Furthermore, rows may be automatically added according to the number of claim items set for each work type, or they may be added by the user. For example, if a user right-clicks on the "Amount (yen)" item in Figure 7, multiple "Amount" items with different currency units may be displayed, and the user may select from among them as appropriate.

[0048] The sales accounting data storage unit 26 stores sales accounting data generated from invoice detail data. Sales accounting data is generated, for example, for each detail accounting date based on multiple invoice detail data.

[0049] The sales recording data includes, for example, the work ID, billing item code, and billing amount, all associated with the date of recording the details. Figure 8 shows an example of sales recording data stored in the sales recording data storage unit 26.

[0050] As shown in Figure 8, the sales recording data includes the work ID "AK24120001", line number (line No.), billing item codes "A110" and "A120", the item recording date (recording date), and the amount (yen). The line details are as described above.

[0051] (Functional configuration of business support equipment) Next, the control unit 3 executes the business support program stored in the memory unit 2, and functions as an acquisition unit 31, a data generation unit 32, a sales accounting processing unit 33, and an output control unit 34, as shown in Figure 1.

[0052] In this example, the acquisition unit 31 to the output control unit 34 are described as being implemented in software based on a business support program, but all or part of the acquisition unit 31 to the output control unit 34 may be implemented in hardware. In either case, the same effects as described later can be obtained.

[0053] The acquisition unit 31 acquires information input to the input device 6, as well as information transmitted from external devices such as the server device 11 and terminal devices (not shown in Figure 1) via the aforementioned network. For example, terminal devices include personal computer devices, tablet terminals, or smartphones. The information input to the input device 6 includes, for example, instructions for executing, starting, or ending various processes in the business support device 1, and data.

[0054] The data includes, for example, work ID, work type code, work standard code, date field, date, billing item code, amount, customer information, and file.

[0055] The data generation unit 32 generates work data, work performance data, and billing detail data. For example, when the data generation unit 32 obtains a work ID and a work type code associated with the work ID, it refers to the storage unit 2, which stores the work type code and the work accounting category (see Figure 3) associated with the work type code, based on the work standard code (see Figure 2) associated with the work type code, and sets one of the date items (work standard name in Figure 3) included in the work accounting category that is related to the type of work (for example, "Warehouse Delivery Confirmation Date" in Figure 3) as the sales accounting date for that work (see Figure 4(a)).

[0056] When the implementation date is entered into one of the date fields corresponding to the one specified above among several date fields for inputting the implementation dates of multiple steps in the work (see Figure 6), the data generation unit 32 generates work data (see Figure 5) that includes the implementation date as the date of sales recognition, associated with the work ID.

[0057] For example, when setting the first date item, the data generation unit 32 sets the first date item to the sales recording date if the referenced work accounting classification includes the first date item, and sets the first date item from the second date item based on whether the information entered by the user relates to exports or imports.

[0058] For example, if the work accounting classification identified based on the work standard code indicates that the date entered by the user should be set as the sales accounting date, the data generation unit 32 generates work data that includes the date entered by the user as the sales accounting date.

[0059] Furthermore, for example, the data generation unit 32 uses the date of the sales recording date included in the work data (see Figure 5) as the detail recording date to generate invoice detail data that includes one or more claim items associated with the work type code, and the invoice amount for each of those one or more claim items.

[0060] In the example in Figure 7, the billing details data includes a claim code that identifies the claim item associated with the work type code, but as described above, it may include both the claim code and the claim item, or only one of them.

[0061] When the invoice detail data (see Figure 7) is generated, the sales recording processing unit 33 performs processing to record sales, or in other words, processing to finalize sales. For example, for multiple tasks, the sales recording processing unit 33 performs sales recording processing to generate sales recording data including the task ID, invoice item code, and invoice amount for each detail recording date, based on multiple detail invoice data. This process records the sales performance for the current month.

[0062] The output control unit 34 outputs various data generated by the data generation unit 32 and the sales accounting processing unit 33 to the output target device (for example, the output device 7). The output control unit 34 may also output the work type master 21, work standard master 22, billing item master, customer information master, transfer table, files, user notifications, etc., stored in the storage unit 2 to the output target device.

[0063] The output device 7 can be a display device, a printing device, or a speaker device. The output control unit 34 converts the various data stored in the storage unit 2 into display information, print information, or audio information and supplies it to each device to obtain display output, print output, or audio output corresponding to the various data. Alternatively, the output device 7 may be the storage unit 2, an external storage device, or a server device on a network.

[0064] [Operation] (Operation of business support equipment) Next, the operation of the business support device 1 according to this embodiment will be described. Figure 9 is a diagram illustrating the operation flow of the business support device 1 according to this embodiment. When the business support device 1 receives an order for work, it reads basic information such as the work type master 21 and work standard master 22, which have been registered in advance, from the storage unit 2, generates work data in which the work type and date items to be entered as the sales recording date are set for the work, and performs registration processing.

[0065] When the business support device 1 receives the dates on which multiple steps included in the work were performed, it inputs the date as the sales recording date for the work data and generates invoice detail data with that sales recording date as the detail recording date. The following will explain this in more detail with reference to Figures 9 to 13.

[0066] (Basic information registration process) First, let's explain the basic information registration process. For example, a user registers the work type and work standards of an ordered job in the work type master 21 (see Figure 2), associating them with the work type code, work type name, and work standard code. The work type code consists of at least one of numbers, letters, and symbols.

[0067] In the example in Figure 2, the work type code consists of four digits consisting only of numbers. For example, work type codes related to import operations are in the 1000s, work type codes related to export operations are in the 2000s, and work type codes related to land transport are in the 7000s. An "other" work type code "9999" is provided to allow user input.

[0068] Furthermore, for example, users register the criteria for recording revenue for work (work criteria) in the work criteria master 22 (see Figure 3), associating the work criteria code, work criteria name, and work accounting category. The work criteria code, like the work type code, is composed of at least one of numbers, letters, and symbols.

[0069] In the example in Figure 3, the work standard code consists of only two digits. The user registers a date item that serves as the basis for recording the revenue of the work, and a work accounting category to which that date item is classified, depending on the type of work. Here, only the work standard code "03" will be explained.

[0070] As mentioned above, the work standard code "03" corresponds to the work standard name "Arrival / Departure Date," which is associated with the work accounting category "C," and this category includes two date fields: "Arrival Date" and "Departure Date." This means that on the export S / I (Shipping Instruction) input screen, the "Departure Date" is set as the sales accounting date, and on the import I / I (Import Instruction) input screen, the "Arrival Date" is set as the sales accounting date.

[0071] By having the user input these conditions, the business support device 1 can set an appropriate sales recording date according to the work type, even if the work accounting category includes two date items.

[0072] (Registration of received work order) Next, we will explain the process of registering an ordered job. Figure 10 shows an example of a new registration screen. In S1 of Figure 9, the process of registering an ordered job, that is, the process of generating job data, takes place. When a user opens the new registration screen, a job ID is assigned and the user enters a job type code. For example, if the user enters the job type code "1000", the job type name "Import Warehouse Customs Clearance" will be displayed on the screen.

[0073] At this time, the data generation unit 32 refers to the work type master 21 and the work standard master 22 and generates work data with the work standard name "Warehouse Delivery Confirmation Date" set as the sales recording date from the work standard code "02" associated with the work type code "1000" (see S1 in Figure 9 and (a) in Figure 4). When the user presses the registration button, the work data (see (a) in Figure 4) is stored in the work data storage unit 23.

[0074] (Registration of work performance) Next, we will explain the process of registering work performance. Figure 11 shows an example of the work performance registration screen. In S2 of Figure 9, the work performance registration process, that is, the process of generating work performance data, takes place. When a user opens the work performance registration screen, multiple date fields are displayed, indicating the dates on which multiple steps associated with the work were performed.

[0075] In import warehouse customs clearance, the port arrival date, actual delivery date, and warehouse delivery confirmation date are associated as input fields. Therefore, users cannot input dates for date fields unrelated to import warehouse customs clearance (departure date, permit date, and actual delivery date). This prevents users from making input errors by entering dates in the wrong fields. Users may enter dates after completing each step, or after completing all steps. Once dates have been entered in all required date fields, the dates will be reflected in the sales recognition date set in S1 (see Figure 5).

[0076] (Data query operation) Next, we will explain the data inquiry operation. Figure 12 shows an example of the data inquiry screen. As described above, once dates are entered in all required date fields, the dates are reflected in the sales recording date of the work data, and the work data stored in the work data storage unit 23 is updated. The user can open the data inquiry screen and enter the work ID to confirm that the sales recording date has been reflected.

[0077] If it becomes necessary to change the sales recording date, the user can add a work type code (not shown in the diagram, but such as by pressing the add button), enter the work type code "9999", and then enter a date in the sales recording date field to change it. After the change, pressing the register button will generate work data that includes the date directly entered by the user as the sales recording date, and the work data stored in the work data storage unit 23 will be updated.

[0078] (Invoice statement creation process) Next, we will explain the process of creating invoice details. Figure 13 shows an example of the invoice details creation screen. In S3 of Figure 9, the invoice details creation process, that is, the invoice details data generation process, takes place. Once the work performance data is generated and the sales recording date for the work data is determined, the invoice details creation process is performed. When the user opens the invoice details creation screen and enters the work ID, invoice details data is generated that includes one or more claim items associated with the work type code, and the invoice amount for each of those one or more claim items, with the sales recording date included in the work data as the detail recording date.

[0079] In the example shown in Figure 13, billing details data is generated that includes two claim items, "Customs clearance application fee" and "Drayage fee," their amounts (in yen), and the date of itemization. When the user presses the registration button, the billing details data (see Figure 7) is stored in the billing details data storage unit 25.

[0080] (Generation of sales accounting data) Next, we will explain the process of generating sales accounting data. In S4 of Figure 9, a sales accounting process is performed to generate sales accounting data from the invoice detail data generated in S3. When a user opens the sales accounting processing screen, the sales accounting processing unit 33 performs a sales accounting process for multiple tasks, based on multiple invoice detail data, to generate sales accounting data for each detail accounting date, including the task ID, the billing item code indicating the billing item, and the billing amount.

[0081] [Effects of the embodiment] As is clear from the above description, when the business support device 1 according to the embodiment obtains a work ID and a work type code, it refers to a storage unit 2 which stores a work accounting classification that includes the work type code and one or two date items set on the day the sales of the work are recorded, based on a work standard code that indicates the basis for recording sales of the work and is associated with the work type code.

[0082] Then, one of the date items included in the work accounting category that relates to the type of work is set as the sales accounting date for that work. When an implementation date is entered into one of the date items that corresponds to one of the date items used to input the implementation dates of multiple steps in the work, work data is generated that includes the implementation date as the sales accounting date, associated with the work ID.

[0083] This reduces the workload on the person in charge, as well as the risk of input errors and omissions in accounting.

[0084] Furthermore, according to the business support device 1 of the embodiment, when setting the first date item, if the referenced work accounting category includes the first date item, the first date item is set as the sales accounting date. If the referenced work accounting category includes the second date item, the first date item is set from the second date item based on whether the information entered by the user is related to exports or imports. As a result, the person in charge can set the appropriate first date item as the sales accounting date without performing any special operations.

[0085] Furthermore, according to the business support device 1 of the embodiment, if the work accounting classification identified based on the work standard code indicates that the date entered by the user should be set as the sales accounting date, work data is generated that includes the date entered by the user and acquired by the acquisition unit 31 as the sales accounting date.

[0086] This allows for correction to the correct sales recording date in case of unexpected problems after the work is completed or if the person in charge made a mistake entering the date.

[0087] Furthermore, according to the business support device 1 of this embodiment, the date of the sales recording date included in the work data is used as the detail recording date, and invoice detail data is generated that includes one or more claim items associated with the work type code, and the invoice amount for each of those one or more claim items. This makes the invoice detail creation process more efficient and reduces errors by the person in charge.

[0088] Furthermore, according to the business support device 1 of the embodiment, based on a plurality of the aforementioned billing detail data, sales accounting processing is performed to generate sales accounting data including a work ID, a billing item code indicating the billing item, and a billing amount for each detail accounting date. This ensures that there are no omissions in accounting and enables efficient sales accounting processing.

[0089] [Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This invention can contribute to improving operational efficiency and promoting appropriate management decisions by companies, and therefore can contribute to SDGs Goals 8 and 9.

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

[0091] Furthermore, this invention can contribute to strengthening control and governance, and therefore can contribute to achieving the 16 goals of the SDGs.

[0092] [Other embodiments] The present invention can be implemented in various different forms within the scope of the technical idea described in the claims, even in embodiments other than those described above.

[0093] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically may be performed manually. Alternatively, all or part of the processes described as being performed manually may be performed automatically by known methods or the like.

[0094] Furthermore, unless otherwise specified, the processing procedures, control procedures, specific names, registration data for each process, information including search conditions and other parameters, screen examples, and database configuration shown in the specification or drawings can be changed at will.

[0095] Furthermore, with respect to the business support device 1, each component shown in the diagram is a functional concept and does not necessarily have to have the physical configuration shown. For example, the processing functions of the business support device 1, particularly the processing functions performed by the control unit 3, may be implemented in whole or in any part by a program interpreted and executed by the control unit 3 (CPU: Central Processing Unit), or by hardware using wired logic.

[0096] The program is recorded on a non-temporary, computer-readable recording medium containing programmed instructions for the information processing device to execute the processes described in the embodiment, and is mechanically read by the business support device 1 as needed. In other words, the storage unit 2, such as ROM or HDD, records a computer program that works in cooperation with the OS (Operating System) to give instructions to the control unit 3 (CPU) and perform various processes. This computer program is loaded into RAM, unpacked, and executed by the control unit 3 as appropriate.

[0097] Furthermore, the business support program for this business support device 1 may be stored on another server device connected to the business support device 1 via any network, and all or part of it may be downloaded and executed as needed.

[0098] Furthermore, the business support program for executing the processes described in the embodiment may be stored on a non-temporary computer-readable recording medium, or it may be configured as a program product.

[0099] Here, any "portable physical medium" can be used as the "recording medium," such as memory cards, USB (Universal Serial Bus) memory, SD (Secure Digital) cards, flexible disks, magneto-optical disks, ROMs, EPROMs (Erasable Programmable Read Only Memory), EEPROMs (Registered Trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROMs (Compact Disk Read Only Memory), MOs (Magneto-Optical Disks), DVDs (Digital Versatile Disks), and Blu-ray (Registered Trademark) Discs.

[0100] Furthermore, "program" refers to a data processing method written in any language or writing method, regardless of whether it is source code or binary code.

[0101] Furthermore, the term "program" is not necessarily limited to a single, monolithic entity, but also includes those that are distributed as multiple modules or libraries, and those that work in cooperation with other programs, such as an operating system, to achieve their functions.

[0102] Furthermore, for the specific configuration, reading procedure, and post-reading installation procedure for the business support device 1 of the embodiment, well-known configurations or procedures can be used.

[0103] The storage unit 2 is a storage means such as a memory device like RAM or ROM, a fixed disk device like a hard disk, a flexible disk, and an optical disk, and stores various programs, tables, databases, and web page files used for various processing or website provision.

[0104] Furthermore, the business support device 1 may be composed of a known personal computer device or an information processing device such as a workstation, or it may be composed of an information processing device to which any peripheral devices are connected. In addition, the information processing device may be implemented by implementing software (including programs or data, etc.) that realizes the processing described in the embodiment.

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

[0106] This invention is particularly suitable for application in logistics operations and the like. [Explanation of Symbols]

[0107] 1 Business support equipment 2 Storage section 3. Control Unit 4. Communication Interface Section 5 Input / Output Interface Section 6 Input devices 7 Output device 11 Server equipment 21 Work Pattern Master 22 Work Standards Master 23. Work Data Storage Unit 24 Work performance data storage unit 25. Billing details data storage unit 26 Sales Recording Data Storage Unit 31 Acquisition Department 32 Data Generation Unit 33 Sales Recognition Processing Department 34 Output Control Unit

Claims

1. An acquisition unit that acquires a work ID to identify a work, and a work type code to identify the form of the work, which is associated with the work ID. A data generation unit, based on a work standard code that indicates the criteria for recording sales of the work and is associated with the work type code, refers to a storage unit that stores a work accounting classification including the work type code and one or two date items to be set as the sales recording date of the work and is associated with the work standard code, sets one of the one or two date items included in the work accounting classification that is related to the type of work as the sales recording date of the work, and when an implementation date is entered in the date item corresponding to the one date item among multiple date items for entering the implementation dates of multiple steps in the work, generates work data that includes the implementation date as the sales recording date, associated with the work ID. An output control unit that outputs the aforementioned work data to the output target device. A business support device equipped with the following features.

2. The data generation unit, in setting the first date item, The business support device according to claim 1, wherein if the referenced work accounting category includes one date item, the first date item is set to the sales accounting date, and if the referenced work accounting category includes two date items, the first date item is set from the second date item based on whether the information entered by the user relates to exports or imports.

3. The data generation unit, If the work accounting category identified based on the work standard code indicates that the date entered by the user will be set as the sales accounting date, the work data is generated that includes the date entered by the user and acquired by the acquisition unit as the sales accounting date. The business support device according to claim 1.

4. The data generation unit, Using the date of the sales recording date included in the work data as the detail recording date, invoice detail data is generated that includes one or more claim items associated with the work type code and the invoice amount for each of the one or more claim items. The output control unit outputs the billing details data to the output target device. A business support device according to any one of claims 1 to 3.

5. moreover, The system includes a sales accounting processing unit that performs sales accounting processing for multiple aforementioned operations, generating sales accounting data for each of the aforementioned detail accounting dates, based on multiple aforementioned billing detail data, including the operation ID, the billing item code indicating the billing item, and the billing amount. The output control unit outputs the sales recording data to the output target device. The business support device according to claim 4.

6. The acquisition step involves the acquisition unit acquiring a work ID that identifies the work and a work type code that identifies the form of the work, which is associated with the work ID. A data generation step in which a data generation unit, based on a work standard code that indicates the criteria for recording sales of the work and is associated with the work type code, refers to a storage unit that stores a classification including the work type code and one or two date items to be set as the sales recording date of the work and is associated with the work standard code, sets one of the one or two date items included in the classification that is related to the type of work as the sales recording date of the work, and when the implementation date is entered in the date item corresponding to the one date item among multiple date items for entering the implementation dates of multiple steps in the work, generates work data that includes the implementation date as the sales recording date and is associated with the work ID, The output control unit performs an output control step in which it outputs the work data to the output target device. A business support method that has the following characteristics.

7. Computers, An acquisition unit that acquires a work ID to identify a work, and a work type code to identify the form of the work, which is associated with the work ID. A data generation unit, based on a work standard code that indicates the criteria for recording sales for the work and is associated with the work type code, refers to a storage unit that stores a classification including the work type code and one or two date items to be set as the sales recording date for the work and is associated with the work standard code, sets one of the one or two date items included in the classification that is related to the work type as the sales recording date for the work, and when an implementation date is entered in the date item corresponding to the one date item among multiple date items for entering the implementation dates of multiple steps in the work, generates work data that includes the implementation date as the sales recording date and is associated with the work ID. Output control unit outputs the generated work data to the output target device. A business support program designed to function as such.

Images