JP7590215B2 - Logistics management device, logistics management method, and logistics management program - Google Patents

Description

The present invention relates to a logistics management device, a logistics management method, and a logistics management program.

For example, in the import management operations of non-permanent cargo carriers (NVOCs), it is necessary to quickly release (issue instructions to remove) cargo brought into the yard. For example, Patent Document 1 is an example of a system related to NVOCCs.

JP 2004-302723 A

However, Patent Document 1 does not mention anything about quickly releasing cargo and reducing overall logistics costs.

The present invention has been made in consideration of the above, and aims to provide a logistics management device, a logistics management method, and a logistics management program that can quickly release cargo and reduce overall logistics costs.

In order to solve the above-mentioned problems and achieve the object, the present invention is a logistics management device equipped with a control unit, the control unit being configured to be able to access a judgment condition master in which the conditions for the completion and release judgment of various tasks are registered, and characterized in that the control unit is equipped with a business information input processing means for inputting business information including the progress of various tasks such as deposits and withdrawals and work, and a query means for referencing the judgment condition master, making a judgment on the completion and release of each task based on the business information, and displaying the judgment results on a query screen of a display unit.

Furthermore, according to one aspect of the present invention, the various operations may include BL collection operations, payment operations, billing operations, and collection operations.

According to one aspect of the present invention, the condition for terminating the BL collection operation may be to satisfy any one of the following conditions: the BL has been collected at the original location, the BL has been collected, a comprehensive LG agreement has been made with the billing destination, and a SINGLE LG has been collected.

According to one aspect of the present invention, the condition for terminating the payment operation may be that the payment terms of the payee are that the payment has been settled or that payment processing has been completed.

According to one aspect of the present invention, the condition for terminating the billing process may be that an invoice has been issued.

According to one aspect of the present invention, the condition for terminating the collection operation may be to satisfy any one of the following conditions: receipt of a transfer processing notice from the billing destination, receipt of payment from the billing destination and confirmation of receivables (allocation), and creation of import instruction information using the import marine number by the company's customs clearance department.

Furthermore, in order to solve the above-mentioned problems and achieve the objective, the present invention may be such that the release decision is made on the condition that the BL collection operation, the payment operation, the billing operation, and the collection operation have all been completed.

In order to solve the above-mentioned problems and achieve the objective, the present invention is a logistics management method executed by an information processing device equipped with a control unit, the control unit being configured to be able to access a judgment condition master in which the conditions for the completion and release judgment of various tasks are registered, and the method includes a business information input processing step executed by the control unit for inputting business information including the progress of various tasks such as deposits and withdrawals and work, and a query step for referring to the judgment condition master, making a judgment on the completion and release of each task based on the business information, and displaying the judgment results on a query screen of a display unit.

In order to solve the above-mentioned problems and achieve the object, the present invention is characterized in that the logistics management program is executed by an information processing device having a control unit, the control unit being configured to be able to access a judgment condition master in which the conditions for the completion and release judgment of various operations are registered, and the logistics management program causes the control unit to execute a business information input processing step for inputting business information including the progress of various operations such as deposits and withdrawals and work, and an inquiry step for referring to the judgment condition master, making a judgment on the completion and release of each operation based on the business information, and displaying the judgment results on an inquiry screen of a display unit.

The present invention has the effect of enabling cargo release to be carried out quickly, thereby reducing overall logistics costs.

FIG. 1 is a block diagram showing an example of the configuration of a logistics management system according to the present embodiment. FIG. 2 is a diagram showing an example of an ER diagram of the logistics management system according to the present embodiment. FIG. 3 is a diagram illustrating an example of the determination condition information. FIG. 4 is a diagram illustrating an example of the configuration of the determination condition master. FIG. 5 is a flowchart for explaining an outline of the overall operation of the control unit of the logistics management system according to the present embodiment. FIG. 6 is a diagram showing sample data for explaining a specific example of the process of the control unit of the logistics management system according to the present embodiment. FIG. 7 is a diagram showing sample data for explaining a specific example of the process of the control unit of the logistics management system according to the present embodiment. FIG. 8 is a diagram showing sample data for explaining a specific example of the process of the control unit of the logistics management system according to the present embodiment. FIG. 9 is a diagram showing sample data for explaining a specific example of the process of the control unit of the logistics management system according to the present embodiment. FIG. 10 is a diagram showing sample data for explaining a specific example of the process of the control unit of the logistics management system according to the present embodiment. FIG. 11 is a diagram showing sample data for explaining a specific example of the process of the control unit of the logistics management system according to the present embodiment.

An embodiment of the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to this embodiment.

[1. Overview]
For example, in the import management work of non-permanent cargo forwarding companies (NVOCCs), it is necessary to quickly release (issue instructions to remove) cargo brought into the yard. When releasing cargo, it is necessary to grasp the status of each document, the progress of work, the collection status, and the payment status.

However, until now, there has been no system that can comprehensively manage work progress, collection status, and payment status, which has led to work delays due to non-collection and non-payment (e.g., not being able to release goods from the yard unless payment is confirmed), as well as delays and omissions in collection and payment.

Therefore, in this embodiment, we focused on the characteristics of the core system that manages receivables and payables information for each case, and created a system that registers the work required for cargo release and the progress of deposits and withdrawals in the system, automatically determines the completion of each task and release, and allows the user to check the information for each case (work and deposit and withdrawal progress) and release decisions at any time (in real time) on the inquiry screen.

According to this embodiment, cargo can be released quickly, and overall logistics costs can be reduced (e.g., storage fees and late fees can be reduced). In addition, it is possible to reduce erroneous release instructions and prevent missed debt collection. Furthermore, instead of one person handling all the processing for a case, multiple people can handle each process simultaneously, improving business efficiency.

The logistics cost management system of this embodiment can be suitably used in industries such as NVOCC.

2. Configuration
An example of the configuration of a logistics 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 logistics management device 100.

The logistics management device 100 is a commercially available desktop personal computer. Note that the logistics management device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may be a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

The logistics management device 100 includes a control unit 102, a communication interface unit 104, a memory unit 106, and an input/output interface unit 108. Each unit included in the logistics management device 100 is connected to each other so as to be able to communicate with each other via any communication path.

The communication interface unit 104 communicatively connects the logistics 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 a communication line. Here, the network 300 has a function of communicatively connecting the logistics management device 100 to the terminals 400... and the server 200, etc., and is, for example, the Internet or a LAN (Local Area Network). The terminals 400... are terminals used in, for example, the international logistics department, the customs department, the accounting department, etc. The terminals 400... are configured to be able to access the logistics management device 100, and can operate various screens (for example, input screens and inquiry screens) provided by the logistics management device 100 to cause the logistics management device 100 to execute various processes and register information.

The input/output interface unit 108 is connected to an input device 112 and an output device 114. The output device 114 may be a monitor (including a touch panel), 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 realize a pointing device function. In the following, the output device 114 may be referred to as the monitor 114 or the printer 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112. In addition, "output" refers to outputting from the output device 114, and includes, for example, display output to the monitor 114, print output from the printer 114, and sending data to the outside.

The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 records computer programs for cooperating with the OS (Operating System) to give instructions to the CPU (Central Processing Unit) to perform various processes. As the storage unit 106, for example, a memory device such as a RAM (Random Access Memory) or a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, and the like can be used. The storage unit 106 also includes a billing destination master 106a, a billing destination LG information master 106b, a payment destination master 106c, a judgment condition master 106d, and a data table 106e. FIG. 2 shows an ER diagram. FIG. 3 shows an example of judgment condition information stored in the data table 106e. FIG. 4 shows an example of the judgment condition master 106d.

The billing destination master 106a is a master for managing information on billing destinations (shippers), and can be configured as a table in which data such as billing destination code, billing destination name, and whether or not LG is included is associated and registered, as shown in FIG. 2.

The billing destination LG information master 106b can be configured as a table in which the billing destination code, row, LG type, start of transaction, and end of transaction data are associated and registered, as shown in FIG. 2.

Payment destination master 106c is a master for managing information on payment destinations (shipping companies) and holds information such as payment terms. As shown in Figure 2, payment destination master 106c can be configured as a table in which data on payment destination codes, payment destination names, and payment terms are associated and registered.

Data table 106e is a table for storing various data such as judgment condition information, sea import information, cost information, billing information, collection schedule information, deposit allocation information, deposit information, import instruction information, payment request information, and payment settlement information. Sea import information, cost information, billing information, collection schedule information, deposit allocation information, deposit information, import instruction information, payment request information, and payment settlement information are referred to as business information.

As shown in FIG. 2, the sea import information may include data such as sea import number, billing code, billing name (shipper), port of arrival date, HBLNO, origin recovery category, BL recovery category, BL recovery date, SINGLE LG recovery date, transfer notification date, and release date.

The cost information may include data such as ocean import number, line, payee code, payee name, payment item name, and payment amount, as shown in Figure 2.

The billing information may include the ocean import number, line, billing item code, billing item name, and billing amount, as shown in Figure 2.

As shown in FIG. 2, the collection schedule information may include a collection schedule number, a sea import number, a billing code, a billing name, a recording date, a scheduled collection date, a scheduled collection amount, and a transfer number.

The payment request information may be composed of payment request header information and payment request detail information, as shown in FIG. 2. The payment request header information may include data on the payment request number, payee code, payee name, accounting date, and scheduled payment date. The payment request detail information may include data on the payment request number, line, sea import number, and payment amount.

The payment settlement information may be composed of payment settlement header information and payment settlement detail information. The payment settlement header information may include data such as the payment settlement number, payee code, payee name, payment date, and payment amount, as shown in FIG. 2. The payment settlement detail information may include data such as the payment settlement number, line, payment request number, and payment amount, as shown in FIG. 2.

The deposit information may include the deposit number, deposit date, deposit amount, and transfer number, as shown in Figure 2.

The deposit allocation information may be composed of deposit allocation information (header) and deposit allocation detail information.
The deposit reserve information (header) may include a deposit reserve number and a date of withdrawal, as shown in Fig. 2. The deposit reserve detail information may include a deposit reserve number, a line, a deposit number, a deposit reserve amount, a scheduled collection number, and a collection reserve amount, as shown in Fig. 2.

Import instruction (ledger) information may include the import ledger number, ocean import number, and bill-to (shipper) code, as shown in Figure 2.

The judgment condition information indicates the type of completion judgment and route judgment for various operations. It can be referenced when setting the judgment condition master 106d. The judgment condition information includes No., item, classification, and description. For example, No. "4" is the item "BL judgment", classification "BL information", and description "The status is expressed with O or X depending on the conditions of No. 5, 6, and 8." No. "10" is the item "payment judgment", classification "cost related", and description "The status is expressed with O or X depending on the conditions of No. 12 and 15." No. "16" is the item "billing judgment", classification "billing related", and description "Displays O if No. 18 is completed."

No. "19" is the item "Deposit judgment", the category "Deposit related", and the explanation "The status is expressed with a circle or an x depending on the conditions of No. 20, 21, and 22." No. "23" is the item "Release judgment", the category "Release", and the explanation "If No. 4: BL judgment, No. 10: Payment judgment, No. 16: Billing judgment, and No. 19: Deposit judgment are all circled, a circle is displayed."

The judgment condition master 106d is a master that sets the conditions for judging the completion and route of various tasks. Settings are registered when functions are used for items on the inquiry screen. Functions can be set by specifying the table and items to be extracted in the inquiry. As shown in Figure 4, the judgment condition master 106d can be composed of a table or the like that associates and registers the process name, item ID (corresponding to the No. of the judgment condition information), item name, row, and set function. In the example shown in the figure, the first line has the process name "Import Sea Inquiry", item ID "4", item name "BL Determination", line "1", and the setting function "CASE WHEN (isnull([Sea Import Information].[Origin Collection Category],0) = 2) or (ISNULL([Billing LG Information].[LG Type Code],'') = 1) or ([Sea Import Information].[SINGLE LG Collection Date] is not null) or ([Sea Import Information].[BL Collection Date] is not null) THEN 'O' ELSE 'X' END".

The control unit 102 is a CPU or the like that controls the logistics management device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, required data, etc., and executes various information processing based on these stored programs. In terms of functional concept, the control unit 102 includes a business information input processing unit 102a, a query processing unit 102b, a master maintenance unit 102c, and a screen display control unit 102d.

The control unit 102 is configured to be able to access the billing master 106a, billing LG information master 106b, payment master 106c, judgment condition master 106d, and data table 106e stored in the memory unit 106. Note that these master groups and data table 106e may be provided elsewhere (e.g., server 200) as long as they are accessible by the control unit 102.

The business information input processing unit 102a inputs business information including the progress of various business operations such as deposits and withdrawals and work, and stores the information in the data table 106e. The various business operations may include BL collection operations, payment operations, billing operations, and collection operations.

The inquiry processing unit 102b refers to the judgment condition master 106d, judges the completion and release of each task based on the task information, and displays the judgment results on the inquiry screen. In this case, the end condition for the BL collection task may be that any one of the following conditions is met: the BL has been collected at the source, the BL has been collected, a comprehensive LG agreement has been made with the billing destination, and a SINGLE LG has been collected. The end condition for the payment task may be that the payment destination's payment conditions are settling payment or payment processing has been completed. The end condition for the billing task may be that an invoice has been issued.

The conditions for completing collection operations may be any one of the following: notification of transfer processing has been received from the billing destination, payment has been received from the billing destination and confirmation of receivables (allocation) has been made, and import instruction information has been created using the import marine number by the company's customs clearance department. Release may be determined on the condition that BL collection operations, payment operations, billing operations, and collection operations have all been completed.

The master maintenance section 102c is used to perform editing such as registering, adding, changing, and deleting data in the billing destination master 106a, billing destination LG information master 106b, payment destination master 106c, and judgment condition master 106d, for example, in response to an operator's operation on a master maintenance screen (not shown).

The screen display control unit 102d controls the display and input of various screens (e.g., input screens, inquiry screens, etc.) that are displayed on the monitor 114 or provided to the terminal 400....

3. Specific Examples
A specific example of the processing of the control unit 102 of the logistics management device 100 in this embodiment will be described with reference to Figures 1 to 10. Figure 5 is a diagram showing a flow for explaining an outline of the overall processing of the control unit 102 of the logistics management device 100 in this embodiment.

(Overall processing)
With reference to Fig. 5, an outline of the overall processing of the control unit 102 of the logistics management device 100 in this embodiment will be described. In Fig. 5, the business information input processing unit 102a executes a sea import input process (S1). In the sea import input process, the business information input processing unit 102a, for example, in response to an access from a terminal 400 of the international logistics department, in response to an input operation on the input screen of the terminal 400, refers to the billing destination master 106a, the billing destination LG information master 106b, and the payment destination master 106c, inputs sea import information, billing information, and cost information, and registers them in the data table 106e. In the sea import input process, information is managed on a case-by-case basis, a sea import number is assigned, and sea import information, cost information, and billing information are input. The sea import information, cost information, and billing information are linked by the sea import number.

The business information input processing unit 102a executes the invoice issuance process (S2). In the invoice issuance process, the business information input processing unit 102a, for example, in response to access from the terminal 400 in the international logistics department, determines the billing information in response to input operations on the input screen of the terminal, creates collection schedule information and registers it in the data table 106e, and issues an invoice based on the collection schedule information.

The business information input processing unit 102a executes the payment request input process (S3). In the payment request input process, the business information input processing unit 102a, for example, in response to access from the terminal 400 in the international logistics department, determines the cost information in response to input operations on the input screen of the terminal, creates payment request information based on the cost information, registers it in the data table 106e, and issues a payment request form based on the payment request information.

The business information input processing unit 102a executes the payment settlement input process (S4). In the payment settlement input process, the business information input processing unit 102a creates payment settlement information based on the payment request information in response to an access from the accounting department terminal 400, for example, and in response to an input operation on the input screen of the terminal, and registers the payment settlement information in the data table 106e.

The business information input processing unit 102a executes the BL/LG collection input process (S5). In the BL/LG collection input process, the business information input processing unit 102a updates the BL collection date or single BL collection date in the marine import information at the time when the BL or LG is collected in response to an access from the terminal 400 of the international logistics department, for example, and an input operation on the input screen of the terminal.

The business information input processing unit 102a executes the transfer confirmation input process (S6). In the transfer confirmation input process, the business information input processing unit 102a updates (registers) the transfer notification date in the ocean import information when it receives a transfer notification from the shipper for the amount invoiced when the invoice is issued, in response to an access from the terminal 400 in the international logistics department and an input operation on the input screen of the terminal. It determines whether the release is possible even if the payment and allocation have not been processed based on the transfer receipt.

The business information input processing unit 102a executes the deposit input process (S7). In the deposit input process, the business information input processing unit 102a registers the deposit information as the actual deposit in the data table 106e in response to access from, for example, the accounting department terminal 400.

The business information input processing unit 102a executes the deposit allocation input process (S8). In the deposit allocation input process, the business information input processing unit 102a generates deposit allocation information for linking the deposit information and the planned collection information in response to access from, for example, the terminal 400 in the international logistics department, and registers the information in the data table 106e.

The business information input processing unit 102a executes the import instruction input process (S9). In the import instruction input process, the business information input processing unit 102a, for example, in response to access from the terminal 400 of the customs department, acquires information from the previous stage of marine import information when the company undertakes customs clearance even after the release of the cargo, creates import instruction information (ledger), and registers it in the data table 106e. When the company undertakes customs clearance in-house, the collection of the invoice is added to the customs clearance invoice after customs clearance processing, so it is determined that the cargo can be released even if it has not been collected.

The business information input processing unit 102a executes the cargo release input process (S10). In the cargo release input process, the business information input processing unit 102a updates the release date of the import maritime information at the time of cargo release in response to access from the terminal 400 of the international logistics department, for example. Note that only maritime import numbers for which cargo can be released can be registered. If release is not possible, an error message (e.g., "X") is displayed.

The inquiry processing unit 102b executes the import sea freight inquiry process (S11). In the import sea freight inquiry process, the inquiry processing unit 102b, for example, in response to access from the terminal 400 of each department, refers to the judgment condition master 106d according to the specified extraction conditions, judges the completion and release of each task based on the task information, and displays the sea freight import information including the judgment results on the inquiry screen. In other words, it is possible to specify the extraction conditions and refer to the sea freight import information in list format. In addition, the release judgment according to the various data registration status at the time of inquiry is displayed in real time.

The conditions for completing the BL collection process are that the BL has been collected at the source (S1: registered by entering sea imports), the BL has been collected (S5: registered by entering BL/LG collections), there is a comprehensive LG agreement with the billing destination (registered in the LG information in the billing destination master), or a single LG has been collected (S5: registered by entering BL/LG collections).

The condition for completing the payment process is that the payment terms of the payee are met and payment has been settled or processed (S3: payment request has been made, followed by S4: payment settlement input has been processed).

The end condition for billing operations is when an invoice has been issued (S2: invoice issuance processing is being performed).

The collection process is completed when one of the following conditions is met: notification of transfer processing has been received from the billing party (S6: input of transfer confirmation), payment has been received from the billing party and confirmed (allocated) against the receivable (S9: processing by input of payment allocation), or import instruction information has been created by the company's customs clearance department using the import marine number (S10: processing by input of import instruction).

(Sample data)
6 to 11 are diagrams showing sample data for explaining a specific example of the processing of the control unit 102 of the logistics management device 100 in this embodiment. A specific example of the processing of the control unit 102 of the logistics management device 100 in this embodiment will be explained with reference to Fig. 6 to Fig. 11. In the following example, a case where an import sea freight inquiry is made is explained using the data example of the judgment condition master 106d shown in Fig. 4.

The master maintenance unit 102c sets data for the billing master 106a, billing LG information master 106b, and payment master 106c in response to an operator's operation on a master maintenance screen (not shown). Figure 6 shows an example of setting data for the billing master 106a, billing LG information master 106b, and payment master 106c.

In the example of the billing master shown in Figure 6, the first line has billing code "SEI001", billing name "AAA Trading Co., Ltd.", and LG status "Yes". The second line has billing code "SEI002", billing name "BBB Trading Co., Ltd.", LG status "No", billing code "SEI003", billing name "B (Stock) CCC Trading", and LG status "Yes".

In the example of the billing LG information master shown in FIG. 6, the first line has billing code "SEI001", line "1", LG type "SINGLE LG", handling start date "2019/10/01", and handling end date "2020/03/31". The second line has billing code "SEI001", line "2", LG type "Comprehensive LG", handling start date "2020/04/01", and handling end date "2021/03/31". The third line has billing code "SEI003", line "1", LG type "Comprehensive LG", handling start date "2020/04/01", and handling end date "2020/09/30".

In the example of the payee master shown in Figure 6, the first line has the payee code "PAY001", the payee name "DDD Kaiun Co., Ltd.", and the payment terms "Payment terms each time," while the second line has the payee code "PAY002", the payee name "EEE Logistics Co., Ltd.", and the payment terms "Payment by credit."

(S1: Sea import input processing)
7 shows an example of inputting sea freight import information, cost information, and billing information. In the sea freight import input process, the sea freight import information, billing information, and cost information are input by referring to the billing destination master 106a, the billing destination LG information master 106b, and the payment destination master 106c, and are registered in the data table 106e.

In the example of sea import information shown in Figure 7, the first line shows the sea import number "IDO001", billing destination (shipper) "SEI001: AAA Trading Co., Ltd.", port arrival date "2020/12/01", HBLNO "OBHBL12011", and origin recovery classification "normal". The second line shows the sea import number "IDO002", billing destination (shipper) "SEI002: BBB Trading Co., Ltd.", The third line has the ocean import number "IDO003", billing address (shipper) "SEI001: AAA Trading Co., Ltd.", date of arrival "2020/12/01", HBL No. "OBHBL12013", and origin recovery classification "origin recovery".

In the example of cost information shown in Figure 7, the first line has the ocean import number "IDO001", line "1", payee "PAY001: DDD Shipping Co., Ltd.", payment item "OCEAN FREIGHT", and payment amount "5,000 yen". The second line has the ocean import number "IDO001", line "2", payee "PAY001: DDD Shipping Co., Ltd.", payment item "DOC FEE", and payment amount "4,000 yen". The third line has the ocean import number "IDO001", line "3", payee "PAY001: DDD Shipping Co., Ltd.", payment item "THC", and payment amount "2,000 yen".

In the example of billing information shown in Figure 7, the first line has ocean import number "IDO001", line "1", invoice item "D/O FEE", invoice amount "¥1,000", ocean import number "IDO001", line "2", the second line has invoice item "OCEAN FREIGHT", invoice amount "¥6,000", and the third line has ocean import number "IDO001", line "3", invoice item "DOC FEE", invoice amount "¥4,000". Billing information for ocean import number "IDO003" and ocean import number "IDO004" has not been entered.

Figure 8 shows an example of input of collection schedule information, payment request information, and payment settlement information.

(S2: Invoice issuing process)
In the invoice issuing process, the invoice information is finalized, collection schedule information is created and registered in the data table 106e, and an invoice is issued based on the collection schedule information.

In the example of collection schedule information shown in FIG. 8, the first line has the collection schedule number "KAI001," ocean import number "IDO001," billing destination "SEI001: AAA Trading Co., Ltd.", accounting date "2020/12/01," scheduled collection date "2020/12/08," scheduled collection amount "¥13,000," and transfer number "11112." The second line has the collection schedule number "KAI002," ocean import number "IDO002 billing destination "SEI002: BBB Trading Co., Ltd.", accounting date "2020/12/01," scheduled collection date "2020/12/08," scheduled collection amount "¥27,000," and transfer number "11113."

(S3: Payment request input process)
In the payment request input process, cost information is finalized, payment request information is created based on the cost information and registered in the data table 106e, and a payment request form is issued based on the payment request information.

The payment request header information in the payment request information shown in Figure 8 is as follows: on the first line, payment request number "PYI001", payee "PAY001: DDD Shipping Co., Ltd.", accounting date "2020/12/01", scheduled payment date "2020/12/01", and on the second line, payment request number "PYI002", payee "PAY001: DDD Shipping Co., Ltd.", accounting date "2020/12/01", scheduled payment date "2020/12/01".

The payment request details information of the payment request information shown in Figure 8 is as follows: on the first line, payment request number "PYI001", line "1", sea import number "IDO001", payment amount "¥11,000", on the second line, payment request number "PYI001", line "2", sea import number "IDO002", payment amount "¥21,000", on the third line, payment request number "PYI002", line "1", sea import number "IDO001", payment amount "¥7,000".

(S4: Payment settlement input process)
In the payment settlement input process, payment settlement information is created based on the payment request information and registered in the data table 106e.

In the example of the payment settlement header information of the payment settlement information shown in Figure 8, the payment settlement number is "PYP001", the payee is "PAY001: DDD Kaiun Co., Ltd.", the payment date is "2020/12/01", and the payment amount is "￥39,000".

In the example of the payment settlement details information of the payment settlement information shown in Figure 8, the first line has the payment settlement number "PYP001", line "1", payment request number "PYI001", and payment amount "¥32,000", and the second line has the payment settlement number "PYP002", line "1", payment request number "PYI002", and payment amount "¥7,000".

(S5: BL/LG collection input process)
In the BL/LG collection input process, the BL collection date or single BL collection date in the marine import information is updated at the time when the BL or LG is collected. In the example shown in Fig. 9, the BL collection date "2020/12/02" of the marine import number "IDO002" in the second line of the marine import information is updated.

(S6: Transfer confirmation input process)
In the transfer confirmation input process, when a transfer process is received from the shipper for the amount invoiced when the invoice is issued, the transfer notification date in the ocean import information is updated. Based on the transfer receipt, a decision is made as to whether the item can be released even if the payment and allocation have not been processed. In the example shown in Figure 9, the transfer notification date "2020/12/02" for the ocean import number "IDO001" in the first line of the ocean import information is updated.

(S7: Deposit input process)
In the deposit input process, deposit information is registered in the data table 106e as a deposit record.
In the example of deposit information shown in Figure 9, the first line has the deposit number "NYK001," the deposit date "2020/12/02," and the deposit amount "¥13,000," and the second line has the deposit number "NYK002," the deposit date "2020/12/02," the deposit amount "¥27,000," and the transfer number "11113."

(S8: Deposit reserve input process)
In the deposit allocation input process, deposit allocation information for linking deposit information with scheduled collection information is generated and registered in data table 106e.

In the example header of the deposit allocation information shown in Figure 10, the first line has the deposit allocation number "NKH001" and the draw date "2020/12/02", and the second line has the deposit allocation number "NKH002" and the draw date "2020/12/02". In the example of the deposit reserve detail information in the deposit reserve information shown in Figure 9, the first line has deposit reserve number "NKH001", line "1", deposit number "NYK001", deposit reserve amount "¥13,000", collection schedule number "KAI001", and collection reserve amount "¥13,000". The second line has deposit reserve number "NKH002", line "1", deposit number "NYK002", deposit reserve amount "¥27,000", collection schedule number "KAI002", and collection reserve amount "¥27,000".

(S9: Import instruction input process)
In the import instruction input process, when the company undertakes customs clearance even after the release of the cargo, the company obtains information from the previous marine import information, creates import instruction information (ledger), and registers it in the data table 106e. When the company undertakes customs clearance, the collection of the invoice is added to the customs clearance invoice after the customs clearance process, so it is determined that the cargo can be released even if it has not been collected.

In the example of import instruction information shown in Figure 10, the import ledger number is "III001," the sea import number is "IDO003," and the billing destination (shipper) is "SEI001: AAA Trading Co., Ltd.".

(S10: Cargo release input process)
In the cargo release input process, the release date of the import sea freight information is updated when the cargo is released. Note that only sea freight import numbers that are available for cargo release can be registered. If release is not possible, an error (e.g., ×) is displayed on the inquiry screen.

In the example shown in Figure 10, the release date of the sea import information sea import number "IDO001" is updated to "2020/12/03", and the release date of the sea import number "IDO002" is updated to "2020/12/03".

(S11: Import sea freight inquiry processing)
In the import sea freight inquiry process, the judgment condition master 106d is referenced according to the specified extraction conditions, and the completion and release judgments of each business are made based on the business information, and the sea freight import information including the judgment results is displayed on the inquiry screen. In other words, in the import sea freight inquiry process, it is possible to specify the extraction conditions and refer to the sea freight import information in a list format. In addition, the release judgment according to the various data registration status at the time of inquiry is displayed in real time.

Figure 11 shows an example of the display of the extraction results when judged using the example setting of the judgment condition master 106d in Figure 4. The extraction results are displayed on an inquiry screen not shown. In the example shown in the figure, the first line has the ocean import number "IDO001", billing destination "SEI001: AAA Trading Co., Ltd.", port arrival date "2020/12/01", BL judgment "Yes", origin recovery classification "Normal", LG presence/absence "Yes", LG type "Comprehensive LG", payment judgment "Yes", shipping company payment destination "Y001: DDD Kaiun Co., Ltd.", payment terms "each time", payment amount "￥11,000", payment request number "PYI001", payment settlement number "PYP001", and billing judgment "Yes". , expected collection amount "￥13,000", invoice issued "completed", deposit judgment "Yes", transfer notification date "2020/12/02", deposit reserve number "NKH001", release judgment "Yes", release date "2020/12/03". In this example, when the end judgment is made for the business information of the above sample data using the judgment condition master 106d in FIG. 4, the BL judgment is "Yes", the payment judgment is "Yes", and the billing judgment is "Yes", so the release judgment is "Yes".

As described above, this embodiment includes a judgment condition master 106d that registers the conditions for the completion and release of various operations, a business information input processing unit 102a that inputs business information including the progress of various operations such as deposits and withdrawals, and an inquiry processing unit 102b that refers to the judgment condition master 106d, judges the completion and release of each operation based on the business information, and displays the judgment results on the inquiry screen of the display unit. This makes it possible to quickly judge the completion and release of each operation, thereby quickly releasing cargo and reducing overall logistics costs.

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

In addition, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, which can contribute to the achievement of SDGs goals 12, 13, and 15.

In addition, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

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

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 a known method.

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

Furthermore, with regard to the logistics management device 100, each component shown in the figure is a functional concept, and does not necessarily have to be physically configured as shown in the figure.

For example, the processing functions of the logistics management device 100, particularly the processing functions performed by the control unit 102, may be realized in whole or in part by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded on a non-transient computer-readable recording medium that contains programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the logistics management device 100 as necessary. That is, a computer program is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive) for working with an OS to give instructions to the CPU and perform various processes. This computer program is executed by being loaded into RAM, and works with the CPU to form the control unit.

This computer program may also be stored in an application program server connected to the logistics management device 100 via any network, and all or part of it may be downloaded as needed.

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

A "program" is a data processing method written in any language or description method, and may be in any format, such as source code or binary code. Note that a "program" is not necessarily limited to a single configuration, but also includes a distributed configuration consisting of multiple modules or libraries, and a program that works in conjunction with a separate program, such as an OS, to achieve its function. 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.

The various databases stored in the memory unit 106 are storage devices 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 website provision.

The logistics 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 logistics management device 100 may be realized by implementing software (including programs or data, etc.) that causes the device to realize the processing described in this embodiment.

Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the figures, and all or part of them can be functionally or physically distributed and integrated in any unit depending on various additions or functional loads. In other words, the above-mentioned embodiments can be implemented in any combination, or the embodiments can be implemented selectively.

100 Logistics management device 102 Control unit 102a Business information input processing unit 102b Inquiry processing unit 102c Master maintenance unit 102d Screen display control unit 104 Communication interface unit 106 Storage unit 106a Billing destination master 106b Billing destination LG information master 106c Payment destination master 106d Judgment condition master 106e Data table 200 Server 300 Network 400 Terminal

Claims (7)

A logistics management device including a control unit,
The control unit is
It is structured to be accessible to the judgment condition master that registers the conditions for completing various operations and the conditions for release judgment.
A business information input processing means for inputting business information including the progress of various business operations such as deposits and withdrawals, and work;
a query means for referencing the judgment condition master, determining whether each task should be completed or released based on the task information, and displaying the result of the determination on a query screen of a display unit;
Equipped with
The various operations include BL collection operations, payment operations, billing operations, and collection operations,
The physical distribution management device is characterized in that the release judgment is made on the condition that the BL collection operation, the payment operation, the billing operation, and the collection operation have all been completed . 2. The logistics management device according to claim 1, wherein the condition for terminating the BL collection operation is that any one of the following conditions is satisfied: the BL has been collected at its original location, the BL has been collected, a comprehensive LG agreement has been made with the billing destination , and a SINGLE LG has been collected. 2. A physical distribution management device according to claim 1 , wherein the condition for terminating the payment operation is that the payment condition of the payee is that the final payment or payment processing has been completed. 2. The physical distribution management device according to claim 1 , wherein the condition for terminating the billing process is that an invoice has been issued. The logistics management device according to claim 1, characterized in that the condition for terminating the collection operation is that any one of the following conditions is satisfied: notification of transfer processing has been received from the billing party; payment has been received from the billing party and confirmation (allocation) of the receivable has been made; and import instruction information has been created by the company's customs clearance department using the import marine number . A logistics management method executed by an information processing device having a control unit,
The control unit is
It is structured to be accessible to the judgment condition master that registers the conditions for completing various operations and the conditions for release judgment.
Executed in the control unit,
a business information input processing step for inputting business information including the progress of various business operations such as deposits and withdrawals;
a query step of referring to the judgment condition master, judging the completion or release of each task based on the task information, and displaying the judgment result on a query screen of a display unit;
Including,
The various operations include BL collection operations, payment operations, billing operations, and collection operations,
The physical distribution management method is characterized in that the release judgment is made on the condition that the BL collection operation, the payment operation, the billing operation, and the collection operation have all been completed . A logistics management program to be executed by an information processing device having a control unit,
The control unit is
It is structured to be accessible to the judgment condition master that registers the conditions for completing various operations and the conditions for release judgment.
The control unit ,
a business information input processing step for inputting business information including the progress of various business operations such as deposits and withdrawals;
a query step of referring to the judgment condition master, judging the completion or release of each task based on the task information, and displaying the judgment result on a query screen of a display unit;
It is a logistics management program to execute the above.
The various operations include BL collection operations, payment operations, billing operations, and collection operations,
The physical distribution management program is characterized in that the release judgment is made on the condition that the BL collection operation, the payment operation, the billing operation, and the collection operation have all been completed.

Images