JP7557485B2 - Sales management system, sales management method, and sales management program - Google Patents

Description

The present invention relates to a sales management system, a sales management method, and a sales management program.

For example, in transactions where the period between the contract and the actual transaction is long and the exchange rate is unpredictable, there is a high exchange risk if the contract is made in the currency at the time of the transaction, so a currency at the time of the contract that is different from the transaction currency may be used. For example, Patent Document 1 is an example of a conventional sales management system.

JP 2003-122255 A

However, Patent Document 1 does not state anything about how to accurately manage profits when the transaction currency and the contract currency are different.

The present invention has been made in consideration of the above, and aims to provide a sales management system, a sales management method, and a sales management program that are capable of accurately managing profits when the transaction currency and the contract currency are different.

In order to solve the above-mentioned problems and achieve the object, the present invention is a sales management system having a control unit, the control unit includes an order entry means for inputting order data including an order number, a billing destination, a product, a contract currency, a transaction currency, a contract sales amount, a transaction sales amount, a Japanese yen sales amount, a foreign currency profit, and a Japanese yen profit, and order data including an order number, a payment destination, a product, a contract currency different from the transaction currency, a transaction currency, a contract purchase amount, a transaction purchase amount, and a Japanese yen purchase amount, and registering the order data in a storage unit, and a time when the Japanese yen currency is confirmed as the sales recording date, The system is characterized by having a sales input means for inputting sales data including sales number, billing destination, product, contract currency, transaction currency, contract sales amount, transaction sales amount, Japanese yen sales amount, foreign currency profit, and Japanese yen profit based on the order data, and registering the data in the storage unit; and a purchase input means for inputting purchase data including purchase number, payment destination, product, contract currency different from the transaction currency, transaction currency, contract purchase amount, transaction purchase amount, and Japanese yen purchase amount based on the order data, with the timing of yen currency confirmation as the purchase recording date, and registering the data in the storage unit.

According to one aspect of the present invention, the order data and the sales data may further include foreign currency profit including various charges and yen profit including various charges.

Furthermore, according to one aspect of the present invention, the product items in the order data and the procurement data may include expenses, and only the product price may be expressed in a contract currency different from the transaction currency, while the expenses may remain in the transaction currency.

According to one aspect of the present invention, the control unit may further include a transaction-specific balance inquiry means for outputting a transaction-specific balance table at the time of contract that enables confirmation of foreign currency profits and yen-denominated profits due to receipt and ordering at the time of contract, based on the order data and order data registered in the storage unit.

According to one aspect of the present invention, the transaction-specific balance inquiry means may output a transaction-specific balance table at the time of recording that allows confirmation of foreign currency profits and yen-denominated profits due to sales and purchases at the time of recording, based on the sales data and purchase data registered in the storage unit.

In order to solve the above-mentioned problems and achieve the object, the present invention provides a sales management method executed by an information processing device having a control unit, comprising: an order entry process executed by the control unit, which inputs order data including an order number, billing destination, product, contract currency, transaction currency, contract sales amount, transaction sales amount, Japanese yen sales amount, foreign currency profit, and Japanese yen profit, and order data including an order number, payment destination, product, contract currency different from the transaction currency, transaction currency, contract purchase amount, transaction purchase amount, and Japanese yen purchase amount, and registers them in a storage unit; The method includes a sales input process for inputting sales data including sales number, billing destination, product, contract currency, transaction currency, contract sales amount, transaction sales amount, Japanese yen sales amount, foreign currency profit, and Japanese yen profit based on the order data as the purchase accounting date, and a purchase input process for inputting purchase data including purchase number, payment destination, product, contract currency different from the transaction currency, transaction currency, contract purchase amount, transaction purchase amount, and Japanese yen purchase amount based on the order data, with the timing of the Japanese yen currency confirmation as the purchase accounting date, and registering the purchase data in the storage unit.

In order to solve the above-mentioned problems and achieve the object, the present invention provides a sales management program to be executed by an information processing device having a control unit, the control unit including an order entry process for inputting order data including an order number, billing destination, product, contract currency, transaction currency, contract sales amount, transaction sales amount, Japanese yen sales amount, foreign currency profit, and Japanese yen profit, and order data including an order number, payment destination, product, contract currency different from the transaction currency, transaction currency, contract purchase amount, transaction purchase amount, and Japanese yen purchase amount, and registering the input data in a storage unit; The sales management program executes a sales input process for inputting sales data including sales number, billing destination, product, contract currency, transaction currency, contract sales amount, transaction sales amount, Japanese yen sales amount, foreign currency profit, and Japanese yen profit based on order data, and registering the data in the storage unit; and a purchase input process for inputting purchase data including purchase number, payment destination, product, contract currency different from the transaction currency, transaction currency, contract purchase amount, transaction purchase amount, and Japanese yen purchase amount based on the order data, with the Japanese yen currency confirmation timing set as the purchase recording date, and registering the data in the storage unit.

The present invention has the effect of enabling accurate profit management when the transaction currency and the contract currency are different.

FIG. 1 is a diagram showing a process image of a sales management system according to the present embodiment. FIG. 2 is a diagram for explaining the functions for managing foreign currency transactions and inputting a contract currency different from the transaction currency. FIG. 3 is a diagram for explaining visualization of the currency at the time of contract and the Japanese currency amount converted from the amount. FIG. 4 is a diagram for explaining visualization of the currency at the time of contract and the Japanese currency amount converted from the amount. FIG. 5 is a block diagram showing an example of the configuration of a sales management system according to the present embodiment. FIG. 6 is a flowchart for explaining an outline of the overall processing of the control unit of the sales management system according to the present embodiment. FIG. 7 is a diagram for explaining a specific example of the process of the control unit of the sales management system according to the present embodiment. FIG. 8 is a diagram for explaining a specific example of the process of the control unit of the sales management system according to the present embodiment. FIG. 9 is a diagram for explaining a specific example of the process of the control unit of the sales management system according to the present embodiment. FIG. 10 is a diagram for explaining a specific example of the process of the control unit of the sales management system according to the present embodiment. FIG. 11 is a diagram for explaining a specific example of the process of the control unit of the sales management system according to the present embodiment. FIG. 12 is a diagram for explaining a specific example of the process of the control unit of the sales management system according to the present embodiment. FIG. 13 is a diagram for explaining a specific example of the process of the control unit of the sales management system according to the present embodiment. FIG. 14 is a diagram for explaining a specific example of the process of the control unit of the sales management system according to the present embodiment.

The 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 transactions where there is a long period of time between the contract and the actual transaction and the exchange rate is unpredictable, there may be a high exchange rate risk if the contract is made in the currency at the time of the transaction, so a currency at the time of the contract different from the transaction currency may be used.

Here, the "transaction currency" is the currency in which "actual" monetary transactions take place. The "contract currency" is the currency "stated in the contract." Generally, the transaction currency is the same as the contract currency, but sometimes a contract is made in a currency different from the transaction currency.

Previously, only the transaction currency was managed without being able to manage the currency at the time of the contract. For example, if the transaction currency was yen and the contract currency was dollars, the profit could not be managed correctly. Also, if the transaction currency and the contract currency are different and the transaction cannot be managed in the contract currency, it is difficult to see the actual profit of the transaction and accurate income and expenditure management is difficult. In addition, because only the purchase cost is determined in yen first, there is a possibility that the risk of exchange rate losses may be unilaterally borne. Specifically, for example, managers were unable to manage the risk of the transaction correctly because the risk status of the transaction was not made visible, and the person in charge also had to manage the transaction status outside the system, making management cumbersome.

In this embodiment, in order to accurately manage profits in the sales management system when the transaction currency and the contract currency are different, the impact of exchange rate risk fluctuation risk at the time of contract is reduced by determining the yen currency at the time of recording the purchase and sale (the same timing). More specifically, by constructing a data structure (management of the contract currency) that can manage the "original profit of the transaction" and an input function to realize this (management of foreign currency transactions and input of the contract currency different from the transaction currency), visualization of the contract currency and the Japanese yen amount converted from the amount is realized.

Figure 1 is a diagram showing the processing image of the sales management system of this embodiment. In Figure 1, the company (for example, a trading company) has made a contract with a customer (overseas) to sell goods for 100 dollars, in the transaction currency "USD" and the contract currency "USD". The company also has made a contract with a supplier (domestic) to purchase goods for the equivalent of 80 dollars in yen, in the transaction currency "USD". Here, the company's original profit is 20 dollars, but to reduce the risk of exchange rate fluctuations, the timing of determining the yen currency is set as the purchase recording date and sales recording date.

The key points of the sales management system of this embodiment are explained with reference to Figures 2 to 4.

(1) Functions for managing foreign currency transactions and inputting a contract currency different from the transaction currency With reference to Figure 2, the functions for managing foreign currency transactions and inputting a contract currency different from the transaction currency will be described. At the time of a sales contract, the rate is 100 yen per dollar. In the billing destination master, "USD" is set as the transaction currency. A sales contract is made with a customer (billing destination) for goods at $100, with the contract currency being "USD" and the transaction currency being "USD". In this case, the home currency "JPY" is 10,000 yen (the in-house rate at the time of the contract).

At the time of recording (sales), 1 dollar is 90 yen. The sales amount is $100, so in the home currency "JPY" it is 9,000 yen (forward exchange rate). The settlement is "USD" for deposit and "USD" for accounting.

We will explain the case where the purchase contract was made in the transaction currency (USD) (yen was confirmed). In the payment destination master, the transaction currency is set to "JPY". A purchase contract is made with the payment destination (supplier) for goods at ¥8,000, with the contract currency being "JPY" and the transaction currency being "JPY". The profit in the home currency "JPY" is ¥2,000 (= ¥10,000 - ¥8,000).

At the time of recording (purchase), the purchase amount is the same as ¥8,000 because the yen amount is confirmed in the transaction currency "JPY" at the time of the contract. The profit in the home currency "JPY" is ¥1,000 (= 9,000 - 8,000), which is ¥1,000 less than the profit at the time of the contract. Settlement is made with payment "JPY" and accounting linkage "JPY".

In contrast, in this embodiment, contracts are made and managed in a transaction currency ≠ contract currency. A purchase contract is made with the payee (supplier) for $80 in the contract currency "USD", which is different from the transaction currency "JPY". The foreign currency profit at the time of the contract is $20 (= $100 - $80). The yen profit is ￥2,000.

The yen is confirmed at the time of recording (purchase), the contract currency is "USD", the purchase amount is $80, the transaction currency is "JPY", and the purchase amount is ¥7,200 (TTB at time of purchase). The foreign currency profit at the time of recording is $20 (= $100 - $80). The yen profit is ¥1,800. In this case, the yen profit is ¥800 more than if the transaction currency had been used at the time of contract. In this embodiment, it is possible to manage the foreign currency profit and yen profit at the time of contract and at the time of recording.

(2) Visualization of the Japanese Yen Amount Converted from the Currency at the Time of Contract and the Amount The visualization of the Japanese Yen Amount converted from the currency at the time of contract and the amount will be described with reference to Figures 3 and 4. In this embodiment, the profits (foreign currency profits, yen profits) at the time of contract and at the time of recording can be confirmed in a transaction-by-transaction income/expenses table.

FIG. 3A shows an example of a transaction-specific income/expense table at the time of contract (order input checklist).
The income/expenses table by transaction at the time of contract (order input checklist) has the following items: voucher information (order number, purchase number), selling information (customer, currency at time of contract, transaction currency, contract sales amount, transaction sales amount, Japanese yen sales amount), buying (purchase) information (supplier, currency at time of contract, transaction currency, contract purchase amount, transaction purchase amount, Japanese yen purchase amount), and profit (foreign currency profit, Japanese yen profit).The income/expenses table by transaction at time of contract (order input checklist) is created based on order data and order data, as described below.

FIG. 3B shows an example of a transaction-specific income/expenses table (sales input checklist) at the time of sales.
The income/expenses table by transaction at time of sales (sales input checklist) has the following items: voucher information (sales number, purchase number), selling information (customer, contract currency, transaction currency, contract sales amount, transaction sales amount, Japanese yen sales amount), buying (purchase) information (supplier, contract currency, transaction currency, contract purchase amount, transaction purchase amount, Japanese yen purchase amount), and profit (foreign currency profit, Japanese yen profit).The income/expenses table by transaction at time of contract (order input checklist) is created based on sales data and purchase data, as described below.

In addition, in this embodiment, even if the transaction currency is yen and the contract currency is dollars, and expenses such as commissions and advances not related to the sale of goods are in yen, it is possible to manage them, making it possible to accurately manage profits by transaction. Specifically, only the product amount is not the transaction currency ≠ the contract currency, and a function has been created that allows expenses such as commissions and advances to be contracted in the transaction currency. Figure 4 is a diagram for explaining the profits (foreign currency profits, yen profits) from expenses such as commissions and advances.

In Figure 4 (B), only the product price has a currency of "USD" at the time of the contract, while the commission and advance expenses have a currency of "JPY" at the time of the contract. As shown in Figure 4 (C), the income/expenses by transaction table at the time of the contract allows you to check the product price profit (foreign currency profit, yen profit), charges amount (yen amount), and charges-including profit (foreign currency profit, yen profit).

The sales management system of this embodiment can be widely applied to companies that have a lot of exports and imports, companies where buying and selling currencies are different in matched transactions (buying and selling transactions), companies where the profit margin for each transaction is small and there is a long period between the contract and the actual transaction, and companies where there is a high risk of profit fluctuations due to exchange rate risk, etc. (companies that need to perform detailed profit management on a transaction basis).

2. Configuration
An example of the configuration of the sales management system according to the present embodiment will be described with reference to Fig. 5. Fig. 5 is a block diagram showing an example of the configuration of the sales management system according to the present embodiment.

The sales management system 100 is a commercially available desktop personal computer. Note that the sales management system 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 sales management system 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 sales management system 100 is connected to each other so that they can communicate with each other via any communication path.

The communication interface unit 104 communicatively connects the sales management system 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 sales management system 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 provide 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.

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 commands to the CPU (Central Processing Unit) to perform various processes. The storage unit 106 can be, 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, or the like.

The memory unit 106 also includes a billing destination master 106a, a payment destination master 106b, and a data file 106c.

The billing master 106a can be configured as a table that associates and registers billing codes, billing recipients, and transaction currencies.

Payment destination master 106b can be composed of a table that associates and registers payment destination codes, payment destinations, and transaction currencies.

Data file 106c is a file for storing various data such as order data, order placement data, sales data, planned collection data, purchase data, planned payment data, deposit data, and payment data.

The order data can be composed of order header data and order detail data. The order header data may include the order number, billing destination, contract currency, transaction currency, contract sales amount, transaction sales amount, Japanese yen sales amount, foreign currency profit, yen profit, foreign currency profit including various charges, and yen profit including various charges.

The order detail data may include the order number, line number, product, contract sales amount, transaction sales amount, and sales amount in Japanese yen.

The purchase order data can be composed of purchase order header data and purchase order detail data. The purchase order header data may include the purchase order number, payee, contract currency, transaction currency, contract purchase amount, transaction purchase amount, Japanese currency purchase amount, foreign currency charge amount, and Japanese currency charge amount.

The order detail data may include the order number, line number, product, contract purchase amount, transaction purchase amount, and purchase amount in Japanese yen.

The sales data may be composed of sales header data and sales detail data. The sales header data may include the sales number, billing destination, contract currency, transaction currency, contract sales amount, transaction sales amount, Japanese yen sales amount, foreign currency profit, yen profit, foreign currency profit including various charges, and yen profit including various charges.

Sales detail data may include sales number, line number, product, contract sales amount, transaction sales amount, and sales amount in Japanese yen.

The collection schedule data may include sales number, line number, product, transaction amount to be collected, Japanese yen amount to be collected, transaction amount already applied, and Japanese yen amount already applied.

The purchase data may be composed of purchase header data and purchase detail data. The purchase header data may include the purchase number, payee, contract currency, transaction currency, contract purchase amount, transaction purchase amount, Japanese currency purchase amount, foreign currency charge amount, and Japanese currency charge amount.

The purchase details data may include purchase number, line number, product, contract purchase amount, transaction purchase amount, and purchase amount in Japanese yen.

The payment schedule data may include sales number, line number, product, transaction scheduled payment amount, scheduled payment amount in Japanese yen, transaction reconciled amount, and Japanese yen reconciled amount.

Deposit data may include deposit number, billing address, transaction currency, and transaction deposit amount.

Payment data may include payment number, payee, transaction currency, and transaction payment amount.

The control unit 102 is a CPU or the like that provides overall control of the sales management system 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 operations based on these stored programs.

The control unit 102 is configured to be able to access the billing master 106a, the payment master 106b, and the data file 106c stored in the memory unit 106. Note that these master files may be provided in other locations (e.g., the server 200) as long as they are accessible by the control unit 102.

The control unit 102, in terms of its functional concept, comprises an order entry unit 102a, a sales entry unit 102b, a purchase entry unit 102c, a deposit entry unit 102d, a payment entry unit 102e, a transaction-specific balance inquiry unit 102f, a screen display control unit 102g, and a master maintenance unit 102h.

The order entry unit 102a, for example, inputs order data including the order number, billing destination, product, contract currency, transaction currency, contract sales amount, transaction sales amount, Japanese yen sales amount, foreign currency profit, and Japanese yen profit in response to the operator's operations on the order entry screen (see Figures 13 and 14) displayed on the monitor 114, and registers the data file 106c, and also inputs order data including the order number, payment destination, product, contract currency different from the transaction currency, transaction currency, contract purchase amount, transaction purchase amount, and Japanese yen purchase amount, and registers the data file 106c.

The sales input unit 102b, for example, in response to an operator's operation on a sales screen (not shown) displayed on the monitor 114, inputs sales data including the sales number, billing destination, product, contract currency, transaction currency, contract sales amount, transaction sales amount, Japanese yen sales amount, foreign currency profit, and Japanese yen profit based on the order data, with the timing of confirmation of the yen currency as the sales recording date, and registers the data in the data file 106c. The sales input unit 102b also creates collection schedule data based on the sales data and registers it in the data file 106c.

The purchase input unit 102c, for example, in response to an operator's operation on a purchase input screen (not shown) displayed on the monitor 114, inputs purchase data including the purchase number, payee, product, contract currency different from the transaction currency, transaction currency, contract purchase amount, transaction purchase amount, and Japanese yen purchase amount based on the order data, with the timing of confirmation of the yen currency set as the purchase accounting date, and registers the data in the data file 106c. The purchase input unit 102c creates payment schedule data based on the purchase data and registers it in the data file 106c.

The order data and sales data may further include foreign currency profits including various charges and yen profits including various charges.

Items in the order data and procurement data include expenses (commissions, advances, etc.), and only the product price is in a contract currency different from the transaction currency, while expenses may remain in the transaction currency.

The deposit input unit 102d inputs deposit data and registers it in the data file 106c, for example, in response to an operator's operation on a deposit input screen (not shown) displayed on the monitor 114.

The payment input unit 102e inputs payment data and registers it in the data file 106c, for example, in response to an operator's operation on a payment input screen (not shown) displayed on the monitor 114.

The transaction-specific balance inquiry unit 102f, in response to the operator's operations on an inquiry screen (not shown) displayed on the monitor 114, outputs and displays a transaction-specific balance table at the time of contract that allows confirmation of foreign currency profits and yen-denominated profits from the orders and receipts at the time of contract, based on the order data and purchase order data registered in the data file 106c.

The transaction-specific balance inquiry unit 102f also displays and outputs a transaction-specific balance table at the time of recording that allows confirmation of foreign currency profits and yen-denominated profits from sales and purchases at the time of recording, based on the sales data and purchase data registered in the data file 106c, in response to the operator's operations on an inquiry screen (not shown) displayed on the monitor 114.

The screen display control unit 102g controls the display and input of various screens (e.g., order entry screen, sales entry screen, purchase entry screen, deposit entry screen, payment entry screen, inquiry screen, etc.) displayed on the monitor 114.

The master maintenance section 102h performs settings such as inputting, adding, deleting, and editing data for the billing destination master 106a and the payment destination master 106b in response to, for example, the operator's operations on the master maintenance screen displayed on the monitor 114.

3. Specific Examples
A specific example of the processing of the sales management system 100 in this embodiment will be described with reference to Figures 5 to 14. First, an overview of the overall processing of the sales management system 100 in this embodiment will be described with reference to Figure 6. Figure 6 is a diagram showing a flow for explaining the overview of the overall processing of the sales management system 100 in this embodiment.

(3-1. Overall processing)
6, the order input unit 102a executes an order input process (step S1). Specifically, in the order input process, the order input unit 102a inputs order data including an order number, billing destination, product, contract currency, transaction currency, contract sales amount, transaction sales amount, Japanese yen sales amount, foreign currency profit, Japanese yen profit, foreign currency profit including various charges, and Japanese yen profit including various charges in response to an operation by an operator on an order input screen displayed on a monitor 114, and registers the input data in the data file 106c, and also inputs order data including an order number, payment destination, product, contract currency different from the transaction currency, transaction currency, contract purchase amount, transaction purchase amount, Japanese yen purchase amount, and Japanese yen charges, and registers the input data in the data file 106c.

The sales input unit 102b executes a sales input process (step S2). Specifically, in the sales input process, the sales input unit 102b, for example, in response to an operator's operation on an input screen (not shown) displayed on the monitor 114, inputs sales data including the sales number, billing destination, product, contract currency, transaction currency, contract sales amount, transaction sales amount, Japanese yen sales amount, foreign currency profit, Japanese yen profit, foreign currency profit including various charges, and Japanese yen profit including various charges based on the order data, with the timing of the confirmation of the Japanese yen currency as the sales recording date, and registers the data in the data file 106c.

The purchase input unit 102c executes the purchase input process (step S3). Specifically, in the purchase input process, the purchase input unit 102c, for example, in response to an operator's operation on an input screen (not shown) displayed on the monitor 114, inputs purchase data including the purchase number, payee, product, contract currency different from the transaction currency, transaction currency, contract purchase amount, transaction purchase amount, Japanese yen purchase amount, and Japanese yen charges based on the order data, with the Japanese yen currency confirmation timing set as the purchase accounting date, and registers the data in the data file 106c. The sales input process S2 and the purchase input process S3 are independent processes.

The deposit input unit 102d executes the deposit input process (step S4). Specifically, in the deposit input process, the deposit input unit 102d inputs deposit data and registers it in the data file 106c in response to, for example, an operator's operation on an input screen (not shown) displayed on the monitor 114.

The payment input unit 102e executes the payment receipt process (step S5). Specifically, in the payment purchase process, the payment input unit 102e inputs payment data in response to, for example, an operator's operation on an input screen (not shown) displayed on the monitor 114, and registers the data in the data file 106c.

The transaction-specific balance inquiry unit 102f executes a transaction-specific balance inquiry process (step S6). Specifically, in the transaction-specific balance inquiry process, the transaction-specific balance inquiry unit 102f displays and outputs a transaction-specific balance table at the time of contract that allows confirmation of foreign currency profits and yen-denominated profits due to the order and receipt at the time of contract, based on the order data and purchase data registered in the data file 106c, in response to the operator's operations on an inquiry screen (not shown) displayed on the monitor 114. After inputting the order and receipt, the transaction-specific balance table at the time of contract can be confirmed.

The transaction-specific balance inquiry unit 102f also displays and outputs a transaction-specific balance table at the time of recording that allows confirmation of foreign currency profits and yen-denominated profits from sales and purchases at the time of recording, based on the sales data and purchase data registered in the data file 106c, in response to the operator's operations on an inquiry screen (not shown) displayed on the monitor 114.

(3-2. Sample data)
7 to 14 are diagrams showing sample data for explaining a specific example of the processing of the control unit 102 of the sales management system 100 according to the present embodiment. A specific example of the processing of the control unit 102 of the sales management system 100 according to the present embodiment will be explained with reference to FIGS. 7 to 14.

(Master maintenance processing)
Master maintenance processing is executed with reference to Fig. 7. The master maintenance section 102h sets data in the billing destination master 106a and the payment destination master 106b in response to an operation by an operator on a master maintenance screen displayed on the monitor 114, for example.

Figure 7 (A) shows an example of data in the billing master 106a. The billing master 106a has fields for billing code, billing destination, and transaction currency. In the example shown in Figure 7 (A), the billing code is "R001", the billing destination is "A (overseas)", and the transaction currency is "USD". Using the billing destination as a key, the transaction currency "USD" in the billing master 106a is set in the order data (order header data).

Figure 7 (B) shows an example of data in the payee master 106b. The payee master 106b has fields for payee code, payee, and transaction currency. In the example shown in Figure 7 (B), the payee code is "P001", the payee "A (domestic)", and the transaction currency is "JPY". Using the payee as a key, the transaction currency "USD" in the payee master 106b is set in the order data (order header data).

(Order input process S1)
The order entry process will be described with reference to Fig. 8. The order entry unit 102a inputs order data including the order number, billing destination, product, contract currency, transaction currency, contract sales amount, transaction sales amount, Japanese yen sales amount, foreign currency profit, Japanese yen profit, foreign currency profit including various charges, and Japanese yen profit including various charges in response to the operator's operation on the order entry screen displayed on the monitor 114, and registers the data in the data file 106c, and also inputs order data including the order number, payment destination, product, contract currency different from the transaction currency, transaction currency, contract purchase amount, transaction purchase amount, Japanese yen purchase amount, and Japanese yen charges, and registers the data in the data file 106c. Figs. 13 and 14 show examples of the order entry screen. The exchange rate at this time is 1 dollar = 100 yen.

Figure 8 (A) shows an example of order header data. The order header data has the following fields: order number, billing destination, contract currency, transaction currency, contract sales amount, transaction sales amount, Japanese yen sales amount, foreign currency profit, Japanese yen profit, foreign currency profit including various charges, and Japanese yen profit including various charges. In the example shown in Figure 8 (A), the data are: order number "JU001", billing destination "A (overseas)", contract currency "USD", transaction currency "USD", contract sales amount "$100", transaction sales amount "$100", Japanese yen sales amount "¥10,000", foreign currency profit "$20", Japanese yen profit "¥2,000", foreign currency profit including various charges "$20", and Japanese yen profit including various charges "¥900".

Figure 8 (B) shows an example of order detail data. The order detail data has fields for order number, line number, product, contract sales amount, transaction sales amount, and Japanese yen sales amount. In the example shown in Figure 8 (B), the fields are order number "JU001", line number "1", product "Product A", contract sales amount "$100", transaction sales amount "$100", and Japanese yen sales amount "￥10,000".

Figure 8 (C) shows an example of order header data. The order header data has fields for order number, payee, contract currency, transaction currency, contract purchase amount, transaction purchase amount, Japanese yen purchase amount, foreign currency charge amount, and Japanese yen charge amount. In the example shown in Figure 8 (C), the data are: order number "HA001", payee "A (domestic)", contract currency "USD", transaction currency "JPY", contract purchase amount "$80", transaction purchase amount "¥8,000", Japanese yen purchase amount "¥8,000", foreign currency charge amount "-", and Japanese yen charge amount "¥1,100".

Fig. 8 (D) shows an example of order detail data. The order detail data has fields for order number, line number, product, contract purchase amount, transaction purchase amount, and purchase amount in Japanese yen. Here, "product" includes not only the actual product, but also expenses such as commission and advance payment. Only the product amount is not equal to the contract currency, and expenses such as commission and advance payment remain in the transaction currency.
In the example shown in Figure 8 (C), the first line has order number "HA001", line number "1", product "Product A", contract purchase amount "$80", transaction purchase amount "$80", and Japanese yen purchase amount "¥8,000". The second line has order number "HA001", line number "2", product "Commission", contract purchase amount "¥500 (remaining in transaction currency)", transaction purchase amount "¥500 (remaining in transaction currency)", and Japanese yen purchase amount "¥500". The third line has order number "HA001", line number "3", product "Advance expenses", contract purchase amount "¥600 (remaining in transaction currency)", transaction purchase amount "¥600 (remaining in transaction currency)", and Japanese yen purchase amount "¥600".

(Sales input process S2)
The sales input process will be described with reference to Fig. 9. The sales input unit 102b, for example, in response to an operator's operation on a sales screen (not shown) displayed on the monitor 114, inputs sales data including sales number, billing destination, product, contract currency, transaction currency, contract sales amount, transaction sales amount, Japanese yen sales amount, foreign currency profit, Japanese yen profit, foreign currency profit including various charges, and Japanese yen profit including various charges based on the order data, with the timing of the yen currency confirmation set as the sales posting date, and registers the data in the data file 106c. The sales input unit 102b also creates collection schedule data based on the sales data and registers it in the data file 106c. The exchange rate at this time is 1 dollar = 90 yen.

Figure 9 (A) shows an example of sales header data. Sales header data may include the following items: sales number, billing destination, contract currency, transaction currency, contract sales amount, transaction sales amount, Japanese yen sales amount, foreign currency profit, Japanese yen profit, foreign currency profit including various charges, and Japanese yen profit including various charges. In the example shown in Figure 9 (A), the items are sales number "UR001", billing destination "A (overseas)", contract currency "USD", transaction currency "USD", contract sales amount "$100", transaction sales amount "$100", Japanese yen sales amount "¥9,000", foreign currency profit "$20", Japanese yen profit "¥1,800", foreign currency profit including various charges "$20", and Japanese yen profit including various charges "¥700".

Figure 9 (B) shows an example of sales detail data. Sales detail data has fields for sales number, line number, product, contract sales amount, transaction sales amount, and sales amount in Japanese yen. In the example shown in Figure 9 (B), the data are sales number "UR001", line number "1", product "Product A", contract sales amount "$100", transaction sales amount "$100", and sales amount in Japanese yen "￥9,000".

Figure 9 (C) shows an example of planned collection data. Planned collection data has fields for sales number, line number, product, transaction amount to be collected, Japanese yen amount to be collected, transaction amount already applied, and Japanese yen amount already applied. In the example shown in Figure 9 (C), the sales number is "UR001", line number is "1", product is "Product A", transaction amount to be collected "$100", Japanese yen amount to be collected "¥9,000", transaction amount already applied "$0", and Japanese yen amount already applied "¥0".

(Purchase input process S3)
The purchase input unit 102c, for example, in response to an operator's operation on a purchase input screen (not shown) displayed on the monitor 114, inputs purchase data including a purchase number, a payment destination, a product, a contract currency different from the transaction currency, a transaction currency, a contract purchase amount, a transaction purchase amount, a Japanese yen purchase amount, and a Japanese yen charge amount based on the order data, with the Japanese yen currency fixed at the purchase accounting date, and registers the data in the data file 106c. The purchase input unit 102c creates payment schedule data based on the purchase data and registers it in the data file 106c. The exchange rate at this time is 1 dollar = 90 yen.

Figure 10 (A) is a diagram showing an example of purchase header data. The purchase header data has the following fields: purchase number, payee, contract currency, transaction currency, contract purchase amount, transaction purchase amount, Japanese yen purchase amount, foreign currency charge amount, and Japanese yen charge amount. In the example shown in Figure 10 (A), the fields are purchase number "SI001", payee "A (domestic)", contract currency "USD", transaction currency "JPY", contract purchase amount "$80", transaction purchase amount "￥7,200", Japanese yen purchase amount "￥7,200", foreign currency charge amount "-", and Japanese yen charge amount "￥1,100".

10B is a diagram showing an example of purchase details data. The purchase details data includes fields for purchase number, line number, product, contract purchase amount, transaction purchase amount, and purchase amount in Japanese yen.
Only the product price is not equal to the contract currency in transaction currency; expenses such as commission and advances will remain in transaction currency. In the example shown in Figure 10 (B), the first line has purchase number "SI001", line number "1", product "Product A", contract purchase amount "$80", transaction purchase amount "7,200", and Japanese yen purchase amount "￥7,200". The second line has purchase number "SI001", line number "2", product "Commission", contract purchase amount "￥500 (remaining in transaction currency)", transaction purchase amount "￥500 (remaining in transaction currency)", and Japanese yen purchase amount "￥500". The third line has purchase number "SI001", line number "3", product "Advance expenses", contract purchase amount "￥600 (remaining in transaction currency)", transaction purchase amount "￥600 (remaining in transaction currency)", and Japanese yen purchase amount "￥600".

Figure 10 (C) shows an example of payment schedule data. The payment schedule data includes fields for sales number, line number, product, transaction scheduled payment amount, Japanese yen scheduled payment amount, transaction cleared amount, and Japanese yen cleared amount. In the example shown in FIG. 10(B), the first line has purchase number "SI001", line number "1", product "product A", transaction scheduled payment amount "¥7,200", Japanese yen scheduled payment amount "¥7,200", transaction applied amount "¥0", Japanese yen applied amount "¥0". The second line has purchase number "SI001", line number "2", product "commission", transaction scheduled payment amount "¥500", Japanese yen scheduled payment amount "¥500", transaction applied amount "¥0", Japanese yen applied amount "¥0". The third line has purchase number "SI001", line number "3", product "advance payment", transaction scheduled payment amount "¥600", Japanese yen scheduled payment amount "¥600", transaction applied amount "¥0", Japanese yen applied amount "¥0".

(Deposit input process S4)
The deposit input process will be described with reference to Fig. 11. When a deposit is received from a billing destination, the deposit input unit 102d inputs deposit data and registers it in the data file 106c, for example, in response to an operator's operation on a deposit input screen (not shown) displayed on the monitor 114. The deposit input unit 102d also updates the collection schedule data in the data file 106c based on the deposit data.

Figure 11 (A) shows an example of deposit data. Deposit data has fields for deposit number, billing destination, transaction currency, and transaction deposit amount. In the example shown in Figure 11 (A), the deposit number is "NY001", the billing destination is "A (overseas)", the transaction currency is "USD", and the transaction deposit amount is "$100". Figure 11 (B) shows an example of updated collection schedule data.

(Payment processing S5)
The payment receipt process will be described with reference to Fig. 12. The payment input unit 102e inputs payment data and registers it in the data file 106c in response to, for example, an operator's operation on a payment input screen (not shown) displayed on the monitor 114. The payment input unit 102e also updates the payment schedule data in the data file 106c based on the payment data.

Figure 12 (A) shows an example of payment data. Payment data has fields for payment number, payee, transaction currency, and transaction payment amount. In the example shown in Figure 12 (A), the payment number is SH001, the payee is "A (domestic)", the transaction currency is "JPY", and the amount is "￥8,300". Figure 12 (B) shows an example of updated payment schedule data.

(Transaction-specific income/expense verification process S6)
The transaction-specific balance inquiry process will be described with reference to Figures 3 and 4. The transaction-specific balance inquiry unit 102f, in response to an operator's operation on an inquiry screen (not shown) displayed on the monitor 114, references the order data and order data registered in the data file 106c, and displays and outputs a transaction-specific balance table at the time of contract that allows confirmation of foreign currency profits and yen-denominated profits due to order and order at the time of contract. For example, a transaction-specific balance table at the time of contract can be output using slip information or billing destination/payee destination as keys.

The balance sheet by transaction at contract time may include fields for voucher information (order number, purchase number), selling information (customer, currency at contract time, transaction currency, contract sales amount, transaction sales amount, Japanese yen sales amount), buying (purchase) information (payee, currency at contract time, transaction currency, contract purchase amount, transaction purchase amount, Japanese yen purchase amount), and profit (foreign currency profit, Japanese yen profit) (see Figure 3 (A)). In the above example, the data in the first row of the balance sheet by transaction at contract time in Figure 3 (A) is output.

The transaction-specific balance inquiry unit 102f also displays and outputs a transaction-specific balance table at the time of recording that allows confirmation of foreign currency profits and yen-denominated profits from sales and purchases at the time of recording, based on the sales data and purchase data registered in the data file 106c, in response to the operator's operations on an inquiry screen (not shown) displayed on the monitor 114. For example, a transaction-specific balance table at the time of contract can be output using invoice information or billing and payment destinations as keys.

The balance sheet by transaction at time of recording may include fields for voucher information (sales number, purchase number), selling information (billing party, contract currency, transaction currency, contract sales amount, transaction sales amount, Japanese yen sales amount), buying (purchase) information (payment party, contract currency, transaction currency, contract purchase amount, transaction purchase amount, Japanese yen purchase amount), and profit (foreign currency profit, Japanese yen profit) (see Figure 3 (B)). In the above example, the data in the first row of the balance sheet by transaction at time of recording in Figure 3 (B) is output.

As described above, according to this embodiment, the order entry unit 102a inputs order data including the order number, billing destination, product, contract currency, transaction currency, contract sales amount, transaction sales amount, Japanese yen sales amount, foreign currency profit, and Japanese yen profit, and order data including the order number, payment destination, product, contract currency different from the transaction currency, transaction currency, contract purchase amount, transaction purchase amount, and Japanese yen purchase amount, and registers the data in the data file 106c; and the timing of the confirmation of the Japanese yen currency is set as the sales recording date, and the sales number, billing destination, product, contract currency, transaction currency, contract sales amount, Japanese yen sales amount, foreign currency profit, and Japanese yen profit are input and registered in the data file 106c based on the order data. The system is equipped with a sales input section 102b that inputs sales data including the amount, transaction sales amount, Japanese yen sales amount, foreign currency profit, and Japanese yen profit and registers it in a data file 106c, and a purchase input section 102c that inputs purchase data including the purchase number, payment destination, product, contract currency different from the transaction currency, transaction currency, contract purchase amount, transaction purchase amount, and Japanese yen purchase amount based on the order data, with the timing of the Japanese yen currency confirmation set as the purchase accounting date, and registers it in a data file 106c, so that profit management can be performed accurately when the transaction currency and the contract currency are different.

[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 sales management system 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 sales management system 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 sales management system 100 as necessary. That is, a computer program is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive) to work 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 sales management system 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 sales management system 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 sales management system 100 may also 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 may be implemented in any combination, or the embodiments may be implemented selectively.

100 Sales management system 102 Control unit 102a Order input unit 102b Sales input unit 102c Purchase input unit 102d Deposit input unit 102e Payment input unit 102f Transaction-specific balance inquiry unit 102g Screen display control unit 102h Master maintenance unit 104 Communication interface unit 106 Storage unit 106a Billing destination master 106b Payment destination master 106c Data file 108 Input/output interface unit 112 Input device 114 Output device 200 Server 300 Network

Claims (6)

A sales management system including a control unit for performing profit management when a transaction currency and a contract currency are different ,
The control unit is
an order entry means for entering and registering in a storage unit order data including an order number, a billing destination, a product, a contract currency, a transaction currency, a contract sales amount, a transaction sales amount, a Japanese yen sales amount, a contract currency at the time of receiving the order and a foreign currency profit and a Japanese yen profit calculated using the exchange rate at that time, and order data including an order number, a payment destination, a product, a contract currency different from the transaction currency, a transaction currency, a contract purchase amount, a transaction purchase amount, and a Japanese yen purchase amount;
a sales input means for inputting sales data including a sales number, a billing destination, a product, a contract currency, a transaction currency, a contract sales amount, a transaction sales amount, a Japanese yen sales amount, a foreign currency profit, and a Japanese yen profit based on the order data, with the timing of the Japanese yen currency confirmation being set as the sales posting date, and registering the data in the storage unit;
a purchase input means for inputting purchase data including a purchase number, a payment destination, a product, a contract currency different from the transaction currency, a transaction currency, a contract purchase amount, a transaction purchase amount, and a Japanese yen purchase amount based on the order data, with the timing of the yen currency confirmation being set as the purchase accounting date, and registering the data in the storage unit;
a transaction-specific balance inquiry means for outputting a transaction-specific balance table at the time of contract, which allows confirmation of foreign currency profits and yen-denominated profits due to receipt of orders and orders at the time of contract, based on the receipt data and order data registered in the storage unit;
A sales management system comprising: 2. The sales management system according to claim 1, wherein the order data and the sales data further include foreign currency profit including various charges and yen profit including various charges. The sales management system according to claim 1 or 2, characterized in that the product items in the order data and the purchase data include expenses, and only the product price is in a contract currency different from the transaction currency, while the expenses remain in the transaction currency. A sales management system as described in any one of claims 1 to 3, characterized in that the transaction-specific balance inquiry means outputs a transaction-specific balance table at the time of recording, which allows confirmation of foreign currency profits and yen-denominated profits from sales and purchases at the time of recording, based on the sales data and purchase data registered in the memory unit. A sales management method for managing profits when a transaction currency and a contract currency are different , the method being executed by an information processing device having a control unit, comprising:
Executed in the control unit,
an order entry process for entering order data including an order number, billing destination, product, contract currency, transaction currency, contract sales amount, transaction sales amount, Japanese yen sales amount, contract currency at the time of receiving the order and foreign currency profit and Japanese yen profit calculated using the exchange rate at that time, and order data including an order number, payment destination, product, contract currency different from the transaction currency, transaction currency, contract purchase amount, transaction purchase amount, and Japanese yen purchase amount, and registering the data in the storage unit;
a sales input process for inputting sales data including a sales number, a billing destination, a product, a contract currency, a transaction currency, a contract sales amount, a transaction sales amount, a Japanese yen sales amount, a foreign currency profit, and a Japanese yen profit based on the order data, with the timing of the Japanese yen currency confirmation being set as the sales recording date, and registering the data in the storage unit;
a purchase input process for inputting purchase data including a purchase number, a payment destination, a product, a contract currency different from the transaction currency, a transaction currency, a contract purchase amount, a transaction purchase amount, and a Japanese yen purchase amount based on the order data, with the timing of the yen currency confirmation being set as the purchase accounting date, and registering the data in the storage unit;
a transaction-specific balance inquiry step of outputting a transaction-specific balance table at the time of contract, which allows confirmation of foreign currency profits and yen-denominated profits due to the receipt of orders and orders at the time of contract, based on the receipt data and order data registered in the storage unit;
A sales management method comprising: A sales management program for performing profit management when a transaction currency and a contract currency are different , the program being executed by an information processing device having a control unit, the program comprising:
The control unit ,
an order entry process for entering order data including an order number, billing destination, product, contract currency, transaction currency, contract sales amount, transaction sales amount, Japanese yen sales amount, contract currency at the time of receiving the order and foreign currency profit and Japanese yen profit calculated using the exchange rate at that time, and order data including an order number, payment destination, product, contract currency different from the transaction currency, transaction currency, contract purchase amount, transaction purchase amount, and Japanese yen purchase amount, and registering the data in the storage unit;
a sales input process for inputting sales data including a sales number, a billing destination, a product, a contract currency, a transaction currency, a contract sales amount, a transaction sales amount, a Japanese yen sales amount, a foreign currency profit, and a Japanese yen profit based on the order data, with the timing of the Japanese yen currency confirmation being set as the sales recording date, and registering the data in the storage unit;
a purchase input process for inputting purchase data including a purchase number, a payment destination, a product, a contract currency different from the transaction currency, a transaction currency, a contract purchase amount, a transaction purchase amount, and a Japanese yen purchase amount based on the order data, with the timing of the yen currency confirmation being set as the purchase accounting date, and registering the data in the storage unit;
a transaction-specific balance inquiry step of outputting a transaction-specific balance table at the time of contract, which allows confirmation of foreign currency profits and yen-denominated profits due to the receipt of orders and orders at the time of contract, based on the receipt data and order data registered in the storage unit;
A sales management program to execute the above.

Images