JP7590367B2 - L/C management device, L/C management method, and L/C management program - Google Patents

Description

The present invention relates to an L/C management device, an L/C management method, and an L/C management program.

Traditionally, L/C (letter of credit) management was done outside the system, making it difficult to manage balances and link them to transactions. For example, Patent Document 1 describes an L/C system.

JP 2006-343998 A

However, Patent Document 1 does not state anything about how centralized management of L/C transactions can be used to quickly grasp L/C balances and transaction status, thereby reducing a company's transaction risks.

The present invention has been made in consideration of the above, and aims to provide an L/C management device, an L/C management method, and an L/C management program that can centrally manage L/C transactions, quickly grasp L/C balances and transaction status, and reduce a company's transaction risks.

In order to solve the above-mentioned problems and achieve the object, the present invention provides an L/C (Letter of Credit) management device equipped with a control unit and a memory unit, which includes an L/C input means for inputting L/C detail data including an L/C slip number, supplier, currency, and contract amount when an L/C is concluded, and registering the data in the memory unit; an order input means for inputting order detail data including an order number, order date, currency, supplier, payee, product, order amount, and debt item, and L/C order data including an L/C slip number, transaction date, order number, and order amount when ordering goods, and registering the data in the memory unit; and an order input means for inputting purchase detail data including a purchase number, purchase date, currency, supplier, payee, product, purchase amount, and debt item, and L/C purchase data including an L/C slip number, transaction date, purchase number, and purchase amount when importing goods, and registering the data in the memory unit based on the purchase detail data. and a purchase input means for creating and registering in the storage unit payment schedule data including the payment schedule number, payment schedule date, purchase number, payee, payment schedule amount, paid amount, debt item as accounts payable, payment method as L/C, and payment notice number, and wherein the order amount of the L/C order data is the allocated amount of the order amount to the contract amount, and/or the purchase amount of the L/C purchase data is the allocated amount of the purchase amount to the contract amount, and the L/C input means displays information including the L/C order amount, L/C purchase amount, and L/C balance on the inquiry screen displayed on the display unit in response to an operator's operation, by referring to the data registered in the storage unit using the L/C slip number as a key.

According to one aspect of the present invention, the control unit may further include a payment method determination processing means for, when determining the payment method, aggregating the scheduled payment data registered in the storage unit by business partner, scheduled payment date, and currency, creating scheduled payment data by denomination including a scheduled payment number by denomination, a scheduled payment date, a payee, a scheduled payment amount, a payment method, a payment notification number, and a payment completion flag, and registering the data in the storage unit.

According to one aspect of the present invention, the control unit may further include a debt transfer input means for inputting debt transfer header data including the debt transfer number, transfer date, lump-sum settlement conditions, lump-sum settlement destination, currency, and transfer item such as import acceptance bill, and debt transfer detail data including the debt transfer number, payment notice number, payee, payment due date, and transfer amount, registering the data in the storage unit, and updating the payment schedule data and the payment schedule data by denomination.

According to one aspect of the present invention, the control unit may further include a payment settlement input means for creating payment data including a payment number, a payment date, a payee, a payment method, and a payment amount, and registering the data in the storage unit.

In order to solve the above-mentioned problems and achieve the object, the present invention provides an L/C management method executed by an information processing device having a control unit and a storage unit, the method including: an L/C input process executed by the control unit, in which, when an L/C is concluded, L/C detail data including an L/C slip number, supplier, currency, and contract amount are input and registered in the storage unit; an order input process, in which, when ordering goods, order detail data including an order number, order date, currency, supplier, payee, goods, order amount, and debt item are input and registered in the storage unit, and L/C order data including an L/C slip number, transaction date, order number, and order amount are input and registered in the storage unit; and, in which, when importing goods, purchase detail data including a purchase number, purchase date, currency, supplier, payee, goods, purchase amount, and debt item are input and registered in the storage unit, and a payment forecast is calculated based on the purchase detail data. and a purchase input process for inputting and registering in the storage unit payment schedule data including the contract number, expected payment date, purchase number, payee, expected payment amount, paid amount, payable item as accounts payable, payment method as L/C, and payment notice number, and inputting and registering in the storage unit L/C purchase data including the L/C slip number, transaction date, purchase number, and purchase amount, the order amount of the L/C order data is the allocated amount of the order amount to the contract amount, and/or the purchase amount of the L/C purchase data is the allocated amount of the purchase amount to the contract amount, and the L/C input process further includes displaying information including the L/C order amount, L/C purchase amount, and L/C balance on a reference screen displayed on a display unit in response to an operator's operation, by referring to the data registered in the storage unit using the L/C slip number as a key.

In order to solve the above-mentioned problems and achieve the object, the present invention provides an L/C management program to be executed by an information processing device having a control unit and a storage unit, the control unit including an L/C input process for inputting L/C detail data including an L/C slip number, supplier, currency, and contract amount when concluding an L/C, and registering the data in the storage unit; an order input process for inputting order detail data including an order number, order date, currency, supplier, payee, product, order amount, and debt item when ordering goods, and inputting L/C order data including an L/C slip number, transaction date, order number, and order amount, and registering the data in the storage unit; and an order input process for inputting purchase detail data including a purchase number, purchase date, currency, supplier, payee, product, purchase amount, and debt item when importing goods, and registering the purchase detail data in the storage unit, and registering a payment schedule number, payment A purchase input process inputs payment schedule data including the scheduled date, purchase number, payee, scheduled payment amount, paid amount, payable item as accounts payable, payment method as L/C, and payment notice number and registers it in the storage unit, and inputs L/C purchase data including L/C slip number, transaction date, purchase number, and purchase amount and registers it in the storage unit, and the order amount of the L/C order data is the allocated amount of the order amount to the contract amount, and/or the purchase amount of the L/C purchase data is the allocated amount of the purchase amount to the contract amount, and the L/C input process further displays information including the L/C order amount, L/C purchase amount, and L/C balance on the inquiry screen displayed on the display unit in response to an operator's operation, referring to the data registered in the storage unit using the L/C slip number as a key.

According to the present invention, by centrally managing L/C transactions, it is possible to quickly grasp the L/C balance and transaction status, thereby reducing a company's transaction risk.

FIG. 1 is a block diagram showing an example of the configuration of an L/C management device according to the present embodiment. FIG. 2 is a diagram showing an example of the configuration of the subject category master. FIG. 3 is a diagram showing an example of the configuration of the currency master. FIG. 4 is a diagram showing an example of the configuration of the payment method master. FIG. 5 is a diagram showing an example of the configuration of the supplier master. FIG. 6 is a diagram illustrating an example of the configuration of the lump-sum payment condition master. FIG. 7 is a diagram showing an example of the configuration of the payment destination master. FIG. 8 is a flow chart for explaining an example of an outline of the overall processing of the control unit of the L/C management device according to this embodiment. FIG. 9 is a diagram for explaining a specific example of the process of the control unit of the L/C management device according to the present embodiment. FIG. 10 is a diagram for explaining a specific example of the process of the control unit of the L/C management device according to the present embodiment. FIG. 11 is a diagram for explaining a specific example of the process of the control unit of the L/C management device according to the present embodiment. FIG. 12 is a diagram for explaining a specific example of the process of the control unit of the L/C management device according to the present embodiment. FIG. 13 is a diagram for explaining a specific example of the process of the control unit of the L/C management device according to the present embodiment. FIG. 14 is a diagram for explaining a specific example of the process of the control unit of the L/C management device according to the present embodiment. FIG. 15 is a diagram for explaining a specific example of the process of the control unit of the L/C management device according to the present embodiment. FIG. 16 is a diagram for explaining a specific example of the process of the control unit of the L/C management device according to the present embodiment. FIG. 17 is a diagram for explaining a specific example of the process of the control unit of the L/C management device 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]
In the past, the management of L/C (Letter of Credit) balances was outside the system, making it difficult to manage the L/C balance and the status of transactions. Therefore, operators who register transaction slips were unable to apply the L/C balance to the transaction amount because the L/C was managed outside the system.

Therefore, in this embodiment, the process of concluding, allocating, and settling L/Cs is managed in a centralized manner, making it possible to quickly grasp L/C balances and transaction status, thereby reducing a company's transaction risk.

Specifically, in this embodiment, (1) it is possible to manage transactions and balances linked to L/Cs by managing the conclusion of L/Cs and applying L/Cs concluded at the time of ordering and purchasing. (2) It is possible to transfer accounts payable that arise from debt transfer to accepted import bills in foreign currency to the bank that concluded the L/C.

The L/C management device of this embodiment is applicable to all companies that have import transactions.

2. Configuration
An example of the configuration of an L/C 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 L/C management device 100.

The L/C management device 100 is a commercially available desktop personal computer. Note that the L/C 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 L/C 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 L/C 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 L/C management device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via the communication line. Here, the network 300 has a function of connecting the L/C management device 100 and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network).

An input device 112 and an output device 114 are connected to the input/output interface unit 108. The output device 114 may be a monitor (including a home television), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that works with a mouse to achieve a pointing device function. In the following, the output device 114 may be referred to as the monitor 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112. Displaying information on the monitor 114 and the user operating the input device 112 may be referred to as "user operation via a UI."

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

The memory unit 106 includes an account category master 106a, a currency master 106b, a payment method master 106c, a supplier master 106d, a lump-sum payment condition master 106e, a payment destination master 106f, and a data file 106g. Figure 2 is a diagram showing an example of the configuration of the account category master 106a. Figure 3 is a diagram showing an example of the configuration of the currency master 106b. Figure 4 is a diagram showing an example of the configuration of the payment method master 106c. Figure 5 is a diagram showing an example of the configuration of the supplier master 106d. Figure 6 is a diagram showing an example of the configuration of the lump-sum payment condition master 106e. Figure 7 is a diagram showing an example of the configuration of the payment destination master 106f.

As shown in Figure 2, the subject category master 106a can be configured as a table in which subject category codes, subject category names, and subject classifications are associated and registered. The subject category master 106a is referenced when converting subject category codes into subject category names and subject classifications.

As shown in FIG. 3, the currency master 106b can be configured as a table in which currency codes and currency names are associated and registered. The currency master 106b is referenced when converting currency codes into currency names.

The payment method master 106c can be configured as a table in which payment method codes and payment method names are associated and registered, as shown in FIG. 4. The payment method master 106c is referenced when converting a payment method code into a payment method name.

As shown in FIG. 5, the supplier master 106d can be configured as a table in which supplier codes, supplier names, and payment destination codes are associated and registered. The supplier master 106d is referenced when converting supplier codes into supplier names and payment destination codes.

As shown in FIG. 6, the lump-sum payment condition master 106e can be configured as a table in which the lump-sum payment condition code, post-transfer payment method, and transfer item are associated and registered. The lump-sum payment condition master 106e is referenced when converting the lump-sum payment condition code into the post-transfer payment method and transfer item.

The payee master 106f can be configured as a table in which payee codes and payee names are associated and registered, as shown in FIG. 7. The payee master 106f is referenced when converting payee codes into payee names.

Data file 106g is a file for storing various data such as L/C detail data, order detail data, L/C order data, purchase detail data, payment schedule data, L/C purchase data, L/C order return data, payment schedule data by denomination, debt transfer header data, debt transfer detail data, and payment data.

The L/C detail data may include the L/C document number, L/C number, supplier, currency, and contract amount.

The L/C order data may include the L/C document number, transaction date, order number, and order amount (allocated amount).

Purchase detail data may include purchase number, line number, purchase date, currency, supplier, payee, product, purchase amount, and payable item.

The L/C purchase data may include the L/C document number, transaction date, purchase number, and purchase amount (allocated amount).

The payment schedule data may include the payment schedule number, the scheduled payment date, the document number, the line number, the payee, the scheduled payment amount, the amount paid, the debt item, the payment method, and the payment notice number.

The L/C order return data may include the L/C document number, purchase number, transaction date, purchase order number, and order amount (allocated amount).

The payment schedule data by denomination may include the payment schedule number by denomination, the scheduled payment date, the payee, the scheduled payment amount, the payment method, the payment notification number, and a payment completion flag (e.g., "0" for unpaid, "1" for paid).

The debt transfer header data may include the debt transfer number, transfer date, lump-sum settlement terms, lump-sum settlement destination, currency, and transfer item.

The debt transfer details data may include the debt transfer number, payment notice number, payee code, payment due date, and transfer amount.

Payment data may include payment number, payment date, payee, payment method, and payment amount.

The control unit 102 is a CPU or the like that performs overall control of the L/C 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.

The control unit 102 is configured to be able to access the subject category master 106a, currency master 106b, payment method master 106c, supplier master 106d, lump-sum payment condition master 106e, payee master 106f, data file 106g, and the like, which are stored in the memory unit 106. Note that the subject category master 106a, currency master 106b, payment method master 106c, supplier master 106d, lump-sum payment condition master 106e, payee master 106f, and data file 106g may be provided elsewhere (e.g., server 200), as long as the control unit 102 is able to access them.

The control unit 102, in terms of its functional concept, includes an L/C input unit 102a, an order input unit 102b, a purchase input unit 102c, a payment method determination unit 102d, a debt transfer input unit 102e, a payment settlement input unit 102f, a master maintenance unit 102g, and a screen display control unit 102h.

The L/C input unit 102a, for example, inputs L/C detail data including the L/C slip number, L/C number, supplier, currency, and contract amount when an L/C is concluded in response to an operator's operation on the L/C input screen displayed on the monitor 114, and registers the data in the data file 106g.

The L/C input unit 102a, for example, in response to an operator's operation on the L/C input screen displayed on the monitor 114, uses the L/C slip number as a key to refer to data registered in the data file 106g and displays information including the L/C order amount, the L/C purchase amount, and the L/C balance.

When ordering goods, for example, in response to the operator's operations on the order input screen or L/C allocation screen displayed on the monitor 114, the order input unit 102b inputs order detail data including the order number, order date, currency, supplier, payee, goods, order amount, and debt item, and L/C order data including the L/C slip number, transaction date, order number, and order amount, and registers them in the data file 106g.

The purchase input unit 102c, for example, inputs purchase detail data including purchase number, purchase date, currency, supplier, payee, product, purchase amount, and debt item, and L/C purchase data including L/C slip number, transaction date, purchase number, and purchase amount, when goods are imported in response to the operator's operations on the purchase input screen or L/C allocation screen displayed on the monitor 114, and registers them in the data file 106g. Based on the purchase detail data, it also inputs payment schedule data including payment schedule number, payment schedule date, purchase number, payee, payment schedule amount, paid amount, debt item designated as accounts payable, payment method designated as L/C, and payment notice number, and registers them in the data file 106g.

The order amount in the L/C order data is the amount of the order amount allocated to the contract amount in the L/C detail data, and/or the purchase amount in the L/C purchase data is the amount of the purchase amount allocated to the contract amount in the L/C detail data, and the allocation to the contract amount of the L/C is performed at the time of order and/or purchase.

When determining the payment method, the payment method determination unit 102d aggregates the scheduled payment data registered in the data file 106g by business partner, scheduled payment date, and currency, creates scheduled payment data by denomination including the scheduled payment number by denomination, the scheduled payment date, the payee, the scheduled payment amount, the payment method, the payment notification number, and a payment completion flag, and registers this in the data file 106g.

For example, in response to the operator's operations on the debt transfer input screen displayed on the monitor 114, the debt transfer input unit 102e inputs debt transfer header data including the debt transfer number, transfer date, lump-sum settlement conditions, lump-sum settlement destination, currency, and transfer item set as an import acceptance bill, and debt transfer detail data including the debt transfer number, payment notice number, payee, payment due date, and transfer amount, registers the data in the data file 106g, and updates the payment schedule data and payment schedule data by denomination in the data file 106g.

The payment settlement input unit 102f creates payment data including the payment number, payment date, payee, payment method, and payment amount in response to, for example, the operator's operations on the payment settlement input screen displayed on the monitor 114, and registers the data in the data file 106g.

The master maintenance unit 102g performs settings such as inputting, adding, changing, and updating data for the subject classification master 106a, currency master 106b, payment method master 106c, supplier master 106d, lump-sum payment condition master 106e, and payment destination master 106f, for example, in response to an operator's operation on a master maintenance screen (not shown) displayed on the monitor 114.

The screen display control unit 102h controls the display and input of various screens (e.g., L/C input screen, order input screen, L/C allocation screen, purchase input screen, debt transfer input screen, payment settlement input screen, etc.) displayed on the monitor 114.

3. Specific Examples
2 to 11, a specific example of the process performed by the control unit 102 of the L/C management apparatus 100 in this embodiment will be described.

(3-1. Overall processing)
FIG. 8 is a flowchart for explaining an outline of the overall processing of the control unit 102 of the L/C management apparatus 100 in this embodiment.

With reference to FIG. 8, an overview of the overall processing of the control unit 102 of the L/C management device 100 in this embodiment will be described. In FIG. 8, the L/C input unit 102a executes the L/C input process (step S1). Specifically, in the L/C input process, the L/C input unit 102a inputs L/C detail data including the L/C slip number, L/C number, supplier, currency, and contract amount when an L/C is concluded in response to, for example, an operator's operation on the L/C input screen displayed on the monitor 114, and registers the data in the data file 106g.

The L/C input unit 102a also inquires about the LC balance and transaction status, and, for example, in response to an operator's operation on the L/C input screen displayed on the monitor 114, uses the L/C slip number as a key to refer to data registered in the data file 106g and displays information including the L/C order amount, L/C purchase amount, and L/C balance. Inquiries about the LC balance and transaction status can be made at any time.

The order input unit 102b executes the order input process (step S2). Specifically, the order input process registers the order and allocates the L/C. For example, when ordering goods, the order input unit 102b inputs order detail data including the order number, order date, currency, supplier, payee, goods, order amount, and debt item and registers it in the data file 106g in response to the operator's operation on the order input screen or L/C allocation screen displayed on the monitor 114, and also inputs L/C order data including the L/C slip number, transaction date, order number, and order amount (allocated amount) and registers it in the data file 106g.

The purchase input unit 102c executes the purchase input process (step S3). Specifically, in the purchase input process, the purchase registration and the L/C at the time of the order are taken over, and the purchase input unit 102c, for example, inputs purchase detail data including the purchase number, purchase date, currency, supplier, payee, product, purchase amount, and debt item, and L/C purchase data including the L/C slip number, transaction date, purchase number, and purchase amount, when the product is imported, in response to the operator's operation on the purchase input screen or L/C allocation screen displayed on the monitor 114, and registers them in the data file 106g. Also, based on the purchase detail data, inputs payment schedule data including the payment schedule number, payment schedule date, purchase number, payee, payment schedule amount, paid amount, debt item set as accounts payable, payment method set as L/C, and payment notice number, and registers them in the data file 106g.

The payment method determination unit 102d executes the payment method determination process (step S4). Specifically, in the payment method determination process, a process for preparing for payment is executed, and when determining the payment method, the payment method determination unit 102d aggregates the scheduled payment data registered in the data file 106g by business partner, scheduled payment date, and currency, creates scheduled payment data by denomination including the scheduled payment number by denomination, the scheduled payment date, the payee, the scheduled payment amount, the payment method, the payment notification number, and a payment completion flag, and registers the data in the data file 106g.

The debt transfer input unit 102e executes the debt transfer input process (step S5). Specifically, in the debt transfer input process, the accounts payable to the business partner is transferred to the import acceptance bill debt to the bank, and the debt transfer input unit 102e inputs, for example, debt transfer header data including the debt transfer number, transfer date, lump-sum settlement conditions, lump-sum settlement destination, currency, and transfer item set as the import acceptance bill, and debt transfer detail data including the debt transfer number, payment notice number, payee, payment due date, and transfer amount in response to the operator's operation on the debt transfer input screen displayed on the monitor 114, registers it in the data file 106g, and updates the payment schedule data and the payment schedule data by denomination in the data file 106g.

The payment and settlement input unit 102f executes the payment and settlement input process (step S6). Specifically, in the payment and settlement input process, the import acceptance bill is settled, and the payment and settlement input unit 102f creates payment data including the payment number, payment date, payee, payment method, and payment amount in response to the operator's operation on the payment and settlement input screen displayed on the monitor 114, for example, and registers the data in the data file 106g.

(3-2. Sample data)
9 to 17 are diagrams showing sample data for explaining a specific example of the processing by the control unit 102 of the L/C management device 100 in this embodiment. A specific example of the processing by the control unit 102 of the L/C management device 100 in this embodiment will be explained with reference to FIG. 9 to FIG.

(S1: L/C input process)
A specific example of the L/C input process will be described with reference to Fig. 9. In the L/C input process, information on an concluded L/C is registered. For example, in response to an operator's operation on an L/C input screen displayed on a monitor 114, the L/C input unit 102a inputs L/C detail data including an L/C slip number, an L/C number, a supplier, a currency, and a contract amount when an L/C is concluded, and registers the data in a data file 106g.

Figure 9 (A) is a diagram showing an example of the L/C input screen. The L/C input screen has a header area that displays items such as the L/C slip number, L/C number, supplier, currency, contract amount, L/C order amount, L/C purchase amount, and L/C balance, an order area that displays items such as order number, order date, and order amount, a purchase area that displays items such as purchase number, purchase date, and purchase amount, and a register button (not shown). When the L/C slip number, L/C number, supplier, currency, and contract amount are entered in the header area and the register button (not shown) is pressed, L/C detail data corresponding to the input contents is registered in data file 106g.

In addition, on the L/C entry screen, you can use the L/C document number as a key to inquire about transaction (order, purchase) information and L/C balance linked to the L/C document number.

Figure 9 (B) is a diagram showing an example of L/C detail data. L/C detail data is data for managing concluded L/C information, and includes fields for L/C slip number, L/C number, supplier, currency, and contract amount. In the example shown in Figure 9 (B), the L/C slip number is "LC0001", the L/C number is "Credit001", the supplier is "SI001-01: 〇×Co., Ltd.", the currency is "USD", and the contract amount is "$10,000". The data in Figure 9 (B) corresponds to the data on the L/C input screen in Figure 9 (A).

(S2: Order input process)
The order input process will be described with reference to Figures 10 and 11. In the order input process, order information for an import transaction is registered, and at the same time, the L/C that has been concluded is allocated (note that the allocation of the L/C can be performed at the time of purchase, not at the time of ordering).

When ordering goods, for example, in response to the operator's operations on the order input screen or L/C allocation screen displayed on the monitor 114, the order input unit 102b inputs order detail data including the order number, order date, currency, supplier, payee, goods, order amount, and debt item, and L/C order data including the L/C slip number, transaction date, order number, and order amount (allocation amount), and registers them in the data file 106g.

10A is a diagram showing a display example of an order input screen. The order input screen includes an order number,
It has a header area that displays items such as order date, transaction category, supplier, department, payee, etc., an order details area that displays items such as product, order quantity, order amount, credit item category, etc., an L/C allocation button for displaying the LC transfer screen, and a registration button (not shown).When data is entered in the header area and order details area, and further data is entered on the LC transfer screen, and then a registration screen (not shown) is pressed, the order details data and L/C order data corresponding to the entered data are registered in the data file 106g.

Figure 10 (B) is a diagram showing an example of the L/C allocation screen. The L/C allocation screen has a header area that displays the items of supplier, document amount, currency, and L/C allocation amount, and an L/C allocation area that displays the items of L/C document number, document number, contract amount, allocated amount, current allocated amount, and remaining amount after current allocation. The contract amount is displayed by referring to the L/C detail data, and the allocated amount is displayed by tallying the order amount of the L/C order data, and when a correction is registered, the current allocated amount before correction is deducted. The current allocated amount is manually entered by the operator, and can be changed as long as the current allocated amount is equal to or greater than 0. The current allocated amount is calculated and displayed each time the current allocated amount is entered, and is calculated as contract amount - allocated amount - current allocated amount.

Figure 10 (C) shows an example of order detail data. Order detail data is data for managing order information, and includes the following fields: order number, line number, order date, currency, supplier, payee, product, order amount, and debt item. In the example shown in Figure 10 (C), the fields are order number "HN0001", line number "1", order date "2021/11/01", currency "USD", supplier "SI001-01: Ox Co., Ltd.", payee "SH001: Ox Co., Ltd.", product "ITEM001: Product XXX", order amount "6,000", and debt item "accounts payable".

Figure 10 (D) shows an example of L/C order data, which is data for managing order detail data linked to L/C, and includes fields for L/C slip number, transaction date, order number, and order amount (allocated amount). The transaction date is set to "Order date" on the order input screen, and the order amount (allocated amount) is set to the current allocated amount on the L/C allocation screen. In the example shown in Figure 10 (D), the L/C slip number is "LC0001", the transaction date is "2021/11/01", the order number is "HN0001", and the order amount (allocated amount) is "6,000".

Figure 11 is a diagram for explaining the transaction (order) information and L/C balance linked to the L/C slip number on the L/C input screen at this point. In the example shown in the figure, the L/C slip number is "LC0001", the LC order amount is "6,000", and the LC balance is "4,000". The L/C balance is calculated and displayed as the L/C appropriation balance, calculated as the contract amount - L/C order amount - L/C purchase amount.

(S3: Purchase input process)
The purchase input process will be described with reference to Figures 12 to 14. In the purchase input process, after import, purchase information is input and the allocation information of the L/C at the time of ordering is confirmed (direct input from the purchase without referring to the order is also possible).

The purchase input unit 102c, for example, inputs purchase detail data including purchase number, purchase date, currency, supplier, payee, product, purchase amount, and debt item, and L/C purchase data including L/C slip number, transaction date, purchase number, and purchase amount, when goods are imported, in response to the operator's operation on the purchase input screen or L/C allocation screen displayed on the monitor 114, and registers them in the data file 106g. Based on the purchase detail data, it also inputs payment schedule data including payment schedule number, payment schedule date, purchase number, payee, payment schedule amount, paid amount, debt item set as accounts payable, payment method set as L/C, and payment notice number, and registers them in the data file 106g. The purchase input unit 102c also generates L/C order return data and registers it in the data file 106g.

Figure 12 (A) is a diagram showing an example of the display of the purchase input screen. The purchase input screen has a header area that displays items such as purchase number, order number, purchase date, transaction category, supplier, department, payee, and payment method, a purchase details area that displays items such as product, purchase quantity, purchase amount, and credit item category, an L/C allocation button for displaying the LC transfer screen, and a registration button (not shown).

After entering data in the header area and purchase details area, and then entering data on the LC allocation screen, pressing the register button (not shown) will register the purchase details data and L/C purchase data corresponding to the entered data in data file 106g.

Figure 12 (B) shows an example of the L/C allocation screen display, which is almost the same as Figure 10 (B), so a detailed explanation will be omitted.

Figure 13 (A) shows an example of purchase detail data. Purchase detail data is data for managing purchase information, and includes the following fields: purchase number, line number, purchase date, currency, supplier, payee, product, purchase amount, and debt item. In the example shown in Figure 13 (A), the fields are purchase number "SN0001", line number "1", purchase date "2021/11/01", currency "USD", supplier "SI001-01: Ox Co., Ltd.", payee "SH001: Ox Co., Ltd.", product "ITEM001: Product XXX", purchase amount "6,000", and debt item "accounts payable".

Figure 13 (C) shows an example of L/C purchase data. L/C purchase data is data for managing purchase detail data linked to L/C document numbers, and includes fields for L/C document number, transaction date, purchase number, and purchase amount (allocated amount). The transaction date is set to "Purchase date" on the purchase input screen, and the purchase amount (allocated amount) is set to the current allocated amount on the L/C allocation screen. In the example shown in Figure 13 (D), the L/C document number is "LC0001", the transaction date is "2021/11/01", the purchase number is "HN0001", and the purchase amount (allocated amount) is "6,000".

Figure 13 (D) shows an example of scheduled payment data. Scheduled payment data is data for managing debt information, and includes the following fields: scheduled payment number, scheduled payment date, voucher number/line number, payee, scheduled payment amount, paid amount, debt item, payment method, and payment notice number. In the example shown in Figure 13 (D), the scheduled payment number is "SHY001", the scheduled payment date is "2021/11/24", voucher number/line number is "SN0001-1", payee is "SH001: 〇×Co., Ltd.", scheduled payment amount is "6,000", paid amount is "0", debt item is "accounts payable", payment method is "P002: L/C (accepted import bill)", and payment notice number is "SHT001".

Figure 13 (D) shows an example of L/C order return data. The original L/C order data is retained because the L/C order data is deleted at the same time as the purchase and slides into the L/C purchase data (for example, when L/C purchase data is deleted, it is used to roll back the linked L/C order data). L/C order return data can also be used to analyze orders that were allocated in the past. Note that L/C order return data is only created if the L/C was allocated at the time of ordering. It is not created if the L/C was allocated at the time of purchase.

The L/C order return data has fields for the L/C slip number, purchase number, transaction date, order number, and order amount (allocated amount). The transaction date is set to the transaction date of the L/C order data. The order amount (allocated amount) and the order amount (allocated amount) of the L/C order data are set. In the example shown in Figure 13 (D), the L/C slip number is "LC0001", the purchase number is "SN0001", the transaction date is "2021/11/01", the order number is "HN0001", and the order amount (allocated amount) is "6,000".

Figure 14 is a diagram to explain the transaction (purchase) information and L/C balance linked to the L/C slip number on the L/C input screen at this point. At the same time as the purchase, the purchase information linked to the L/C slip number of the order slides to the purchase information side. In the example shown in the figure, the L/C slip number is "LC0001", the LC order amount is "0", the LC order amount is "6,000", and the LC balance is "4,000".

(S4: Payment method confirmation process)
A specific example of the payment method determination process will be described with reference to Fig. 15. In the payment method determination process, the payment schedule data is aggregated by business partner, scheduled payment date, and currency, and identification numbers (payment schedule number by denomination, payment notice number) are assigned. When determining the payment method, the payment method determination unit 102d aggregates the payment schedule data by business partner, scheduled payment date, and currency, creates payment schedule data by denomination including the payment schedule number by denomination, scheduled payment date, payee, scheduled payment amount, payment method, payment notice number, and paid flag, and registers the data in the data file 106g.

Figure 15 (A) is a diagram showing an example of payment schedule data. Figure 15 (B) is a diagram showing an example of payment schedule data by denomination. The payment schedule data by denomination is used to manage information that aggregates payment schedule data by business partner, scheduled payment date, and currency. The payment schedule data by denomination includes only the following items: payment schedule number by denomination, scheduled payment date, payee, scheduled payment amount, payment method, payment notice number, and payment completion flag (e.g., unpaid "0" and paid "1"). In the example shown in Figure 15 (B), the payment schedule number by denomination is "KSHY001", the scheduled payment date is "2021/11/24", the payee is "SH001: 〇×Co., Ltd.", the scheduled payment amount is "6,000", the payment method is "P002: L/C (accepted import bill)", the payment notice number is "SHT001", and the payment completion flag is "0".

(S5: Debt transfer input process)
A specific example of the debt transfer input process will be described with reference to FIG. 16. In the debt transfer input process, accounts payable to a business partner are transferred to an import acceptance bill to a bank. The debt transfer input unit 102e inputs debt transfer header data including the debt transfer number, transfer date, lump-sum settlement conditions, lump-sum settlement destination, currency, and transfer item, and debt transfer detail data including the debt transfer number, payment notice number, payee code, payment due date, and transfer amount, in response to the operator's operation on the debt transfer input screen displayed on the monitor 114, and registers them in the data file 106g. The debt transfer input unit 102e updates the payment schedule data and the payment schedule data by denomination based on the debt transfer header data and the debt transfer detail data.

Figure 16 (A) is a diagram showing an example of the debt transfer input screen. The debt transfer input screen has a header area that displays the debt transfer number, lump-sum settlement conditions, currency, lump-sum settlement destination, transfer date, and transfer item, a transfer details area that displays the payee, scheduled payment date, payment due date, transfer amount, and transfer items, and a register button (not shown). When data is entered in the header area and transfer details area and the register button (not shown) is pressed, debt transfer header data and debt transfer detail data corresponding to the entered data are registered in data file 106g.

Figure 16 (B) is a diagram showing an example of debt transfer header data. Debt transfer header data is data for managing debt transfer destination information, and includes items such as debt transfer number, transfer date, lump-sum settlement conditions, lump-sum settlement destination, currency, and transfer item. In the example shown in Figure 16 (B), the debt transfer number is "SMH001", the transfer date is "2021/11/24", the lump-sum settlement conditions are "L/C (import bill acceptance)", lump-sum settlement destination is "SH002:□△Bank", the currency is "USD", and the transfer item is "import bill acceptance".

Figure 16 (C) is a diagram showing an example of debt transfer detail data. Debt transfer detail data is data for managing the source information of debt, and includes fields for debt transfer number, payment notice number, payee code, payment due date, and transfer amount. In the example shown in Figure 16 (C), the debt transfer number is "SMH001", the payment notice number is "SHT001", the payee code is "OxCo., Ltd.", the payment due date is "2022/02/28", and the transfer amount is "6,000".

The payment schedule data is updated as shown in Figure 16 (D) to add transfer data that transfers the accounts payable to the payee to an import acceptance bill to the bank. In the example shown in Figure 16 (D), records are added to the second line for the payment schedule number "SHY002", scheduled payment date "2022/02/28", document number/line number "SHN0001-1", payee "SH002:□△Bank", scheduled payment amount "6,000", amount paid "0", debt item "import acceptance bill", payment method "P001:Transfer", and payment notice number "SHT002".

The payment schedule data by denomination is also updated as shown in Figure 16 (E). In the example shown in Figure 16 (E), the paid flag of the record in the first row is updated to "1", and further, a record is added to the second row with the following payment schedule number by denomination "KSHY002", scheduled payment date "2/28/2022", payee "SH002:□△ Bank", scheduled payment amount "6,000", payment method "P001: Transfer", payment notice number "SHT002", and paid flag "0".

(S6: Payment settlement input process)
A specific example of the payment input process will be described with reference to Fig. 17. In the payment input process, payment is made to the bank according to the payment due date. The payment input unit 102f creates payment data including the payment number, payment date, payee, payment method, and payment amount in response to an operator's operation on the payment input screen displayed on the monitor 114, and registers the data in the data file 106g, and transfers the payment amount to the bank via online banking. The payment input unit 102f also updates the payment completion flag of the corresponding denomination-specific payment schedule data to "1: Paid".

Figure 17 (A) is a diagram showing an example of the display of the payment settlement input screen. The payment settlement input screen has a header area that displays the payment number and payment date, a payment details area that displays the payee, payment method, payment amount, and payment check (set "Payment" with a check), and a register button (not shown). When data is entered in the header area and payment details area and the register button (not shown) is pressed, payment data corresponding to the entered data is registered in data file 106g.

Fig. 17(B) shows an example of payment data. Payment data is data for managing payment information, and includes fields for payment number, payment date, payee, payment method, and payment amount. In the example shown in Fig. 17(B), the payment number is "SHR001", the payment date is "2022/02/28", the payee is "SH002:□△Bank", the payment method is "P001:Transfer", and the payment amount is "6,000".

Figure 17 (C) shows an example of scheduled payment data. Figure 17 (D) shows an example of scheduled payment data by denomination, in which the paid flag is updated to "1".

As described above, according to this embodiment, when an L/C is concluded, an L/C input unit 102a inputs L/C detail data including an L/C slip number, supplier, currency, and contract amount, and registers the data in data file 106g; when an order is placed for goods, an order input unit 102b inputs order detail data including an order number, order date, currency, supplier, payee, goods, order amount, and debt item, and an L/C order data including an L/C slip number, transaction date, order number, and order amount, and registers the data in the storage unit; when goods are imported, purchase detail data including a purchase number, purchase date, currency, supplier, payee, goods, purchase amount, and debt item, and an L/C purchase data including an L/C slip number, transaction date, purchase number, and purchase amount are input, and registered in data file 106g; and based on the purchase detail data, a payment schedule number, payment schedule date, purchase number, payee, payment and a purchase input unit 102c that creates payment schedule data including the expected amount, the paid amount, the debt item as accounts payable, the payment method as L/C, and the payment notice number, and registers the data in the data file 106g. The order amount of the L/C order data is the amount of the order amount allocated to the contract amount, or the purchase amount of the L/C purchase data is the amount of the purchase amount allocated to the contract amount. The L/C input unit 102a displays information including the L/C order amount, L/C purchase amount, and L/C balance on the L/C input screen displayed on the monitor 114 in response to the operator's operation, using the L/C slip number as a key and referring to the data registered in the data file 106g. By centrally managing L/C transactions, it is possible to quickly grasp the L/C balance and transaction status, and reduce the transaction risk of the company.

[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 search conditions and other parameters, screen examples, and database configurations shown in this specification and drawings may be changed as desired unless otherwise specified.

Furthermore, with regard to the L/C 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 L/C management device 100, particularly the processing functions performed by the control unit, 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 L/C 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 the OS to give instructions to the CPU and perform various processes. This computer program is executed by being loaded into RAM, and works with the CPU to form the control unit.

This computer program may also be stored in an application program server connected to the L/C 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, or may 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 DVD (registered trademark) or 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 the embodiments, as well as the installation procedure after reading, can use well-known configurations and procedures.

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

The L/C 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 L/C 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 L/C management device 102 Control unit 102a L/C input unit 102b Order input unit 102c Purchase input unit 102d Payment method determination unit 102e Debt transfer input unit 102f Payment settlement input unit 102g Master maintenance unit 102h Screen display control unit 104 Communication interface unit 106 Storage unit 106a Account classification master 106b Currency master 106c Payment method master 106d Supplier master 106e Lump sum payment condition master 106f Payee master 106g Data file 108 Input/output interface unit 112 Input device 114 Output device 200 Server 300 Network

Claims (5)

A Letter of Credit (L/C) management device for use in import transactions, comprising a control unit and a storage unit,
an L/C input means for inputting L/C details data including an L/C slip number, a supplier, a currency, and a contract amount when an L/C is concluded, and registering the data in the storage unit;
an order input means for inputting order detail data including an order number, an order date, a currency, a supplier, a payee, an item, an order amount, and an account payable item, and L/C order data including an L/C slip number, a transaction date, an order number, and an order amount, and registering the data in the storage unit when placing an order for the item;
a purchase input means for inputting purchase detail data including purchase number, purchase date, currency, supplier, payee, product, purchase amount, and debt item when importing goods, and L/C purchase data including L/C slip number, transaction date, purchase number, and purchase amount, and registering the data in the storage unit, and also for creating payment schedule data including payment schedule number, payment schedule date, purchase number, payee, payment schedule amount, paid amount, debt item for accounts payable, payment method for L/C, and payment notice number based on the purchase detail data, and registering the data in the storage unit;
Equipped with
The order amount of the L/C order data is an allocation amount of the order amount to the contract amount, and/or the purchase amount of the L/C purchase data is an allocation amount of the purchase amount to the contract amount,
The L/C input means, in response to an operation by an operator, uses an L/C slip number as a key to refer to data registered in the storage unit and displays information including the L/C order amount, the L/C purchase amount, and the L/C balance on an inquiry screen displayed on a display unit;
The control unit further
An L/C management device characterized by having a payment method determination processing means which, when determining a payment method, aggregates the scheduled payment data registered in the memory unit by business partner, scheduled payment date, and currency, and creates scheduled payment data by denomination including a scheduled payment number by denomination, a scheduled payment date, a payee, a scheduled payment amount, a payment method, a payment notice number, and a paid flag, and registers the data in the memory unit . The control unit further
The L/C management device as described in claim 1 is characterized in that it is equipped with a debt transfer input means for inputting debt transfer header data including the debt transfer number, transfer date, lump-sum payment terms, lump-sum payment destination, currency, and transfer item such as import acceptance bill, and debt transfer detail data including the debt transfer number, payment notice number, payee, payment due date, and transfer amount, registering them in the memory unit, and updating the payment schedule data and the payment schedule data by denomination. The control unit further
3. The L/C management device according to claim 2 , further comprising a payment settlement input means for creating payment data including a payment number, a payment date, a payee, a payment method and a payment amount and registering the data in the memory section. An L/C management method for use in import transactions , executed by an information processing device having a control unit and a storage unit, comprising:
Executed in the control unit,
an L/C input step of inputting L/C details data including an L/C slip number, a supplier, a currency, and a contract amount when an L/C is concluded, and registering the data in the storage unit;
an order input process for inputting order detail data including an order number, an order date, a currency, a supplier, a payee, an item, an order amount, and an account payable item, and L/C order data including an L/C slip number, a transaction date, an order number, and an order amount, and registering the data in the storage unit when placing an order for the item;
a purchase input process for inputting purchase detail data including purchase number, purchase date, currency, supplier, payee, product, purchase amount, and debt item when importing goods, and L/C purchase data including L/C slip number, transaction date, purchase number, and purchase amount, and registering the data in the storage unit, and also creating payment schedule data including payment schedule number, payment schedule date, purchase number, payee, payment schedule amount, paid amount, debt item set as accounts payable, payment method set as L/C, and payment notice number based on the purchase detail data, and registering the data in the storage unit;
Including,
The order amount of the L/C order data is an allocation amount of the order amount to the contract amount, and/or the purchase amount of the L/C purchase data is an allocation amount of the purchase amount to the contract amount,
In the L/C input step, the display unit further displays information including the L/C order amount, the L/C purchase amount, and the L/C balance on the inquiry screen displayed on the display unit in response to an operation by the operator, by referring to the data registered in the storage unit using the L/C slip number as a key;
The L/C management method further comprises a payment method determination processing step of, when determining the payment method, aggregating the scheduled payment data registered in the memory unit by business partner, scheduled payment date, and currency, and creating scheduled payment data by denomination including a scheduled payment number by denomination, a scheduled payment date, a payee, a scheduled payment amount, a payment method, a payment notice number, and a paid flag, and registering the data in the memory unit . An L/C management program for use in import transactions , which is executed by an information processing device having a control unit and a storage unit,
The control unit ,
an L/C input step of inputting L/C details data including an L/C slip number, a supplier, a currency, and a contract amount when an L/C is concluded, and registering the data in the storage unit;
an order input process for inputting order detail data including an order number, an order date, a currency, a supplier, a payee, an item, an order amount, and an account payable item, and L/C order data including an L/C slip number, a transaction date, an order number, and an order amount, and registering the data in the storage unit when placing an order for the item;
a purchase input process for inputting purchase detail data including purchase number, purchase date, currency, supplier, payee, product, purchase amount, and debt item when importing goods, and L/C purchase data including L/C slip number, transaction date, purchase number, and purchase amount, and registering the data in the storage unit, and also creating payment schedule data including payment schedule number, payment schedule date, purchase number, payee, payment schedule amount, paid amount, debt item set as accounts payable, payment method set as L/C, and payment notice number based on the purchase detail data, and registering the data in the storage unit;
This is an L/C management program for executing the above.
The order amount of the L/C order data is an allocation amount of the order amount to the contract amount, and/or the purchase amount of the L/C purchase data is an allocation amount of the purchase amount to the contract amount,
In the L/C input step, the display unit further displays information including the L/C order amount, the L/C purchase amount, and the L/C balance on the inquiry screen displayed on the display unit in response to an operation by the operator, by referring to the data registered in the storage unit using the L/C slip number as a key;
Furthermore, an L/C management program for executing a payment method determination processing step in which, when determining the payment method, the payment schedule data registered in the memory unit is aggregated by business partner, scheduled payment date, and currency, and payment schedule data by denomination including a payment schedule number by denomination, a scheduled payment date, a payee, a scheduled payment amount, a payment method, a payment notice number, and a paid flag is created and registered in the memory unit .

Images