JP7569438B2 - Excess reflection device, excess reflection method, and excess reflection program - Google Patents

Description

The present invention relates to an excess amount reflection device, an excess amount reflection method, and an excess amount reflection program.

Patent document 1 states that if resources are provided to a user that exceed the user's planned usage amount, an additional fee can be calculated to cover the excess amount (see paragraph 0039 of patent document 1).

JP 2015-225436 A

In the field of taking such excess amounts into consideration when invoicing expenses, there have traditionally been the following issues. In recent years, there has been an increase in businesses that purchase points for a certain period of time in advance, and then use up the advance payment based on the number of clicks or ad impressions, and record sales.

However, if the amount exceeded the pre-agreed contract amount, a separate invoice had to be issued for the excess amount, resulting in a very cumbersome operation. In other words, in the past, it was difficult to reflect the excess amount in the billing schedule data, which included the pre-agreed contract amount.

The present invention has been made in consideration of the above problems, and aims to provide an excess amount reflection device, an excess amount reflection method, and an excess amount reflection program that can reflect an excess amount in billing schedule data that includes a pre-agreed contract amount.

In order to solve the above-mentioned problems and achieve the object, an excess amount reflection device according to the present invention is an excess amount reflection device having a control unit, and is capable of accessing billing schedule data including one billing schedule record having a billing schedule amount equal to the contract amount and a billing schedule date corresponding to the contract period, which is generated when the billing schedule generation class in contract data including a contract amount, a billing schedule generation class, and a contract period is a lump-sum class meaning that the contract amount is billed in a lump sum, or including billing schedule records having billing schedule amounts when the contract amount is divided into each month and billing dates corresponding to each month, for the number of divided months, which are generated when the billing schedule generation class in the contract data is a split class meaning that the contract amount is divided into each month and billed, and order detail data including order detail records having order amounts when the contract amount is divided into monthly orders and planned sales dates corresponding to the monthly orders, for the number of divided months, which are generated based on the contract data, and an order detail record specifying means for specifying an order detail record having a planned sales date on which sales for a certain month will be recorded in confirmed order data including a certain confirmed order amount; an excess calculation means for calculating the difference between the order amount included in the order detail record specified by the order detail record specifying means and the confirmed order amount as an excess amount which is an amount by which the contract amount exceeds the contract amount ; and a billing schedule data updating means for updating the billing schedule data by adding a billing schedule record including a planned billing date corresponding to the next contract period when the contract period is updated and the excess amount calculated by the excess calculation means to the billing schedule data when the billing schedule generation classification in the contract data is the lump-sum classification, and updating the billing schedule data by adding the excess amount calculated by the excess calculation means to the billing schedule amount in the billing schedule record having a planned billing date corresponding to the month following the month to which the planned sales date included in the order detail record specified by the order detail record specifying means belongs when the billing schedule generation classification in the contract data is the division classification;
The present invention is characterized by comprising:

Further, an excess amount reflection method according to the present invention is an excess amount reflection method executed by an information processing device having a control unit, wherein the information processing device has access to billing schedule data including one billing schedule record having a billing schedule amount equal to the contract amount and a billing date corresponding to the contract period, generated when the billing schedule generation classification in contract data including a contract amount, a billing schedule generation classification, and a contract period is a lump-sum classification meaning that the contract amount is billed in a lump sum, or including billing schedule records having billing schedule amounts when the contract amount is divided into each month and billing dates corresponding to each month, for the number of months into which the contract amount is divided, generated when the billing schedule generation classification in the contract data is a division classification meaning that the contract amount is divided into each month and billed, and order detail data including order detail records having order amounts when the contract amount is divided into monthly orders and planned sales dates corresponding to the monthly orders, for the number of divisions , generated based on the contract data, and an excess calculation step of calculating a difference between the order amount of the order detail record specified in the order detail record specifying step and the confirmed order amount as an excess amount that is an amount that exceeds the contract amount; and, when the billing schedule generation classification in the contract data is the lump-sum classification, updating the billing schedule data by adding to the billing schedule data a billing schedule record including a billing schedule date corresponding to the next contract period when the contract period is updated and the excess amount calculated in the excess calculation step, and, when the billing schedule generation classification in the contract data is the split classification, updating the billing schedule data by adding the excess amount calculated in the excess calculation step to the billing schedule amount in the billing schedule record having a billing schedule date corresponding to the month following the month to which the planned sales date of the order detail record specified in the order detail record specifying step belongs.

Furthermore, the excess reflection program of the present invention is an information processing device having a control unit that can access: billing schedule data including one billing schedule record having a billing amount equal to the contract amount and a billing date corresponding to the contract period, generated when the billing schedule generation class in contract data including a contract amount, a billing schedule generation class, and a contract period is a lump-sum class meaning that the contract amount is billed in a lump sum, or billing schedule data including billing schedule records having billing amounts when the contract amount is divided into each month and billing dates corresponding to each month, for the number of months into which the contract amount is divided, generated when the billing schedule generation class in the contract data is a split class meaning that the contract amount is divided into each month and billed, and order detail data including order detail records having order amounts when the contract amount is divided into monthly orders and planned sales dates corresponding to the monthly orders, for the number of divided months, generated based on the contract data, the billing schedule data update step of updating the billing schedule data by adding, to the billing schedule data, a billing schedule record including a billing schedule date corresponding to the next contract period when the contract period is updated and the excess amount calculated in the excess amount calculation step, when the billing schedule generation classification in the contract data is the lump-sum classification, and updating the billing schedule data by adding, to the billing schedule data, the billing schedule record including the billing schedule date corresponding to the month following the month to which the planned sales date belongs, which is included in the order detail record identified in the order detail record identification step.

The present invention has the effect of allowing the excess amount to be reflected in billing schedule data, which includes the pre-agreed contract amount.

FIG. 1 is a block diagram showing an example of the configuration of an excess reflection device. FIG. 2 is a diagram showing an example of correlation between each piece of data. FIG. 3 is a diagram showing an example of a case registration process in the case of lump-sum advance billing. FIG. 4 is a diagram showing an example of a process for claiming an advance payment in the case of a lump-sum advance claim. FIG. 5 is a diagram showing an example of a process for determining the amount of sales for the current month in the case of a lump-sum advance billing. FIG. 6 is a diagram showing an example of a process for recording the current month's sales in the case of a lump-sum advance invoice. FIG. 7 is a diagram showing an example of a case registration process in the case of monthly advance billing. FIG. 8 is a diagram showing an example of a process for claiming an advance payment in advance every month. FIG. 9 is a diagram showing an example of a process for determining the amount of sales for the current month in the case of monthly advance billing. FIG. 10 is a diagram showing an example of a process for recording the current month's sales in the case of monthly advance billing.

Below, an embodiment of an excess amount reflection device, an excess amount reflection method, and an excess amount reflection program according to the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to the present embodiment.

[1. Configuration]
An example of the configuration of an excess amount reflection 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 excess amount reflection device 100.

The excess reflection device 100 is a commercially available desktop personal computer. The excess reflection 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 excess reflection device 100 comprises a control unit 102, a communication interface unit 104, a storage unit 106, and an input/output interface unit 108. Each unit of the excess reflection 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 excess reflection 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 excess reflection device 100 and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network). Note that data such as various masters described below may be stored in the server 200, for example.

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 instructions 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 storage unit 106 includes, for example, contract data 106a, order detail data 106b, billing schedule data 106c, billing data 106d, receipt data 106e (corresponding to the "confirmed order data" of the present invention), and sales data 106f. An example of the correlation between each data is shown in FIG. 2.

As shown in FIG. 3 and FIG. 7, the contract data 106a includes, for example, the order number, the contract name, the billing destination, the customer, the invoice amount (corresponding to the "contract amount" of the present invention), the contract detail number, the product name, the sales distribution category, the billing distribution category (corresponding to the "billing schedule generation category" of the present invention), the contract unit price, the contract quantity, the unit, the contract amount, the start and end of the contract period (corresponding to the "contract period" of the present invention), and the like. The billing distribution category (corresponding to the "billing schedule generation category" of the present invention) is a "lump sum" category (corresponding to the "lump sum category" meaning that the contract amount is billed in one lump sum) or a "monthly" category (corresponding to the "split category" meaning that the contract amount is billed in installments for each month) of the present invention.

As shown in Figures 3 and 7, the order detail data 106b includes an order detail record having, for example, an order number, a contract detail number, an order line number, a confirmation status, an order price, an order quantity, an order amount, a planned sales date, a sales completion category, and the like.

As shown in Figures 3 and 7, the billing schedule data 106c includes a billing schedule record having, for example, an order number, a contract detail number, a billing schedule number, a billing schedule unit price, a billing schedule quantity, a billing schedule amount, a billing schedule date, a billing completion category, and the like.

As shown in Figures 4 and 8, billing data 106d includes, for example, a billing number, a billing destination, a billing date, a billing amount, a billing line number, billing details, a billing unit price, a billing quantity, a billing amount, etc.

As shown in Figures 5 and 9, the received data 106e (corresponding to the "confirmed order data" of the present invention) includes, for example, the order number, contract detail number, order line number, order quantity, and order amount (corresponding to the "confirmed order amount, which is the confirmed order amount for a certain month" of the present invention).

As shown in Figures 6 and 10, sales data 106f includes, for example, sales number, customer, sales date, sales price, sales quantity, sales amount, sales line number, product name, etc.

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

The control unit 102, functionally and conceptually, generates billing schedule data including one billing schedule record having a billing schedule amount equal to the contract amount and a billing schedule date corresponding to the contract period when the billing schedule generation classification in the contract data including the contract amount, the billing schedule generation classification, and the contract period is a lump-sum classification meaning that the contract amount is billed in a lump sum, and generates billing schedule data including one billing schedule record having a billing schedule amount equal to the contract amount and a billing schedule date corresponding to the contract period when the billing schedule generation classification in the contract data is a split classification meaning that the contract amount is divided into months and billed. (2) an order detail data generating unit 102b as an order detail data generating means for generating order detail data including order detail records having order amounts when the contract amount is divided into monthly orders and scheduled sales dates corresponding to the monthly orders, the number of which corresponds to the number of months into which the contract amount is divided; and (3) an order detail data generating unit 102c as an order detail data generating means for generating order detail data including order detail records having order amounts when the contract amount is divided into monthly orders and scheduled sales dates corresponding to the monthly orders, the number of which corresponds to the number of months into which the contract amount is divided. (4) an order detail record specification unit 102c as an order detail record specification means for specifying an order detail record having a planned sales date for recording sales for the certain month in the confirmed order data including the order detail record specified by the order detail record specification means; (5) an excess calculation unit 102d as an excess calculation means for calculating the difference between the order amount of the order detail record specified by the order detail record specification means and the confirmed order amount as the excess amount; and (6) a billing schedule calculation unit 102e as an excess calculation means for calculating the difference between the order amount of the order detail record specified by the order detail record specification means and the confirmed order amount as the excess amount when the billing schedule generation category in the contract data is the lump-sum category, and a billing schedule date corresponding to the next contract period when the contract period is updated. and a billing schedule data update unit 102e as a billing schedule data update means that updates the billing schedule data by adding a billing schedule record including the estimated excess amount to the billing schedule data, and when the billing schedule generation category in the contract data is the division category, updates the billing schedule data by adding the excess amount calculated by the excess calculation means to the billing schedule amount in the billing schedule record having a billing schedule date corresponding to the month following the month to which the estimated sales date of the order detail record identified by the order detail record identification means belongs.

When the billing schedule generation category in the contract data 106a, which includes the contract amount, the billing schedule generation category, and the contract period, is the lump-sum category, the billing schedule data generation unit 102a generates billing schedule data 106c that includes one billing schedule record having a billing schedule amount equal to the contract amount and a billing schedule date corresponding to the contract period.

In response to this, when the billing schedule generation category in the contract data 106a is the split category, the billing schedule data generation unit 102a generates billing schedule data 106c that includes billing schedule records having the billing schedule amounts when the contract amount is split into each month and the billing schedule dates corresponding to each month, for the number of months into which the contract amount is split.

The order detail data generating unit 102b generates order detail data 106b based on the contract data 106a, which includes order detail records each having the order amount when the contract amount is divided into monthly orders and the expected sales date corresponding to the monthly orders, the number of such divisions.

The order detail record identification unit 102c identifies, from the order detail data 106b generated by the order detail data generation unit 102b, an order detail record having a planned sales date for recording sales for a certain month in the acceptance data 106e that includes a confirmed order amount, which is the confirmed order amount for that certain month.

The excess amount calculation unit 102d calculates the difference between the order amount contained in the order detail record identified by the order detail record identification unit 102c and the confirmed order amount as the excess amount.

When the billing schedule generation category in the contract data 106a is the lump-sum category, the billing schedule data update section 102e updates the billing schedule data 106c generated by the billing schedule data generation section 102a by adding to the billing schedule data 106c a billing schedule record including the billing schedule date corresponding to the next contract period when the contract period is updated and the excess amount calculated by the excess amount calculation section 102d.

In response to this, when the billing schedule generation category in the contract data 106a is the split category, the billing schedule data update section 102e updates the billing schedule data 106c generated by the billing schedule data generation section 102a by adding the excess amount calculated by the excess calculation section 102d to the billing schedule amount in the billing schedule record having a billing schedule date corresponding to the month following the month to which the planned sales date of the order detail record identified by the order detail record identification section 102c belongs.

2. Specific examples of processing
In this section, a specific example of the process in this embodiment will be described. The process in the case of lump-sum advance billing will be described in [2-1] below, and the process in the case of monthly advance billing will be described in [2-2] below.

[2-1. In the case of a lump sum advance payment]
In this section, the process for the lump-sum advance billing (that is, when the billing deployment category in the maintenance contract detailed data 106a is "lump-sum") will be described in detail with reference to FIGS.

(1) Case Registration First, case information is registered by inputting maintenance contract information. The registration date is assumed to be December 15, 2018. Specifically, the maintenance contract information data 106a and the maintenance contract details data 106a in FIG. 3 are registered.

The billing distribution category in the registered maintenance contract details data 106a is "lump sum" as shown in FIG. 3. In this case, the billing schedule data generation unit 102a generates the maintenance billing schedule data 106c in FIG. 3, which includes a billing schedule record having a billing schedule amount of 180,000 yen, which is the same as the invoice amount of 180,000 yen in the registered maintenance contract information data 106a, and a billing schedule date of "2018/12/20" corresponding to the contract period of "2019/1/1 to 2019/6/30" in the registered maintenance contract details data 106a.

The sales distribution category in the registered maintenance contract detail data 106a is "monthly" as shown in FIG. 3. In this case, the order detail data generation unit 102b divides the invoice amount of 180,000 yen in the registered maintenance contract information data 106a into monthly orders. Since the contract period in the registered maintenance contract detail data 106a is six months, it is divided into six. Therefore, the order detail data generation unit 102b generates the order detail data 106b in FIG. 3, which includes six order detail records having the order amount of 30,000 yen obtained by dividing the invoice amount of 180,000 yen in the registered maintenance contract information data 106a by six, the expected sales date corresponding to the monthly orders, etc.

(2) Advance payment billing process Next, the billing for the current month is recorded through the advance payment billing process. The date of the advance payment billing process is assumed to be December 20, 2018. When the advance payment billing process is performed, as shown in FIG. 4, the billing completion category in the generated maintenance billing schedule data 106c is updated from "incomplete" to "completed," and the billing header data 106d and billing detail data 106d in FIG. 4 are generated.

(3) Confirmation of Sales for the Current Month Next, the order details for the current month are updated by accepting the pay-per-use data (acceptance data 106e in FIG. 5). The date of this acceptance is assumed to be 2019/2/5.

Since the date of receipt of the receipt data 106e in FIG. 5 is 2019/2/5, the order amount of 33,750 yen in the receipt data 106e in FIG. 5 can be said to be the confirmed order amount for January 2019. Here, since the planned sales date on which sales for January 2019 are recorded is 2019/1/31, the order detail record identification unit 102c identifies the order detail record (order amount 30,000 yen) of order line number 1 having the planned sales date 2019/1/31 from the maintenance order detail data 106b in FIG. 3 generated in (1). Note that the order detail record identification unit 102c may identify the order detail record using the three items of the order number, contract detail number, and order line number as keys. Specifically, the order detail record having the same combination of the order number, contract detail number, and order line number as the combination in the receipt data 106e may be identified from the maintenance order detail data 106b.

Then, the excess calculation unit 102d calculates the difference between the order amount of 30,000 yen in the order detail record identified by the order detail record identification unit 102c and the order amount of 33,750 yen in the receipt data 106e. In other words, the excess calculation unit 102d calculates the difference to be 3,750 yen.

Here, the billing distribution category in the maintenance contract detail data 106a registered in (1) is "lump sum." In this case, the billing schedule data update unit 102e updates the maintenance billing schedule data 106c as shown in FIG. 5 by adding a billing schedule record having the billing schedule date "2019/6/20" corresponding to the next contract period "2019/7/1-2019/12/31" when the contract period "2019/1/1-2019/6/30" in the maintenance contract detail data 106a registered in (1) is updated, and the difference of 3,750 yen calculated by the excess calculation unit 102d. The details shown in hatching in the maintenance billing schedule data 106c in FIG. 5 are the added billing schedule records.

(4) Recording of sales for the current month Finally, the order details for the current month are updated by the maintenance sales lump-sum processing. The date of the maintenance sales lump-sum processing is assumed to be February 5, 2019. When the maintenance sales lump-sum processing is performed, as shown in Figure 6, the sales completion category of the order detail record for order line number 1 is updated from "incomplete" to "completed," and the sales header data 106f and sales detail data 106f in Figure 6 are generated.

[2-2. In the case of monthly advance billing]
In this section, the process for monthly advance billing (that is, when the billing expansion category in the maintenance contract detailed data 106a is "monthly") will be described in detail with reference to FIGS.

(1) Case Registration First, case information is registered by inputting maintenance contract information. The implementation date of the registration is assumed to be December 15, 2018. Specifically, the maintenance contract information data 106a and the maintenance contract details data 106a in FIG. 7 are registered.

The billing expansion category in the registered maintenance contract details data 106a is "monthly" as shown in FIG. 3. In this case, the billing schedule data generation unit 102a divides the invoice amount of 180,000 yen in the registered maintenance contract information data 106a into monthly bills. Since the contract period in the registered maintenance contract details data 106a is six months, it will be divided into six. Therefore, the billing schedule data generation unit 102a generates the maintenance billing schedule data 106c in FIG. 7, which includes six billing schedule records having the planned billing amount of 30,000 yen obtained by dividing the invoice amount of 180,000 yen in the registered maintenance contract information data 106a by six, the planned billing date for monthly billing, etc.

The sales distribution category in the registered maintenance contract details data 106a is "monthly" as shown in FIG. 7. In this case, the order details data generation unit 102b divides the invoice amount of 180,000 yen in the registered maintenance contract information data 106a into monthly orders. Since the contract period in the registered maintenance contract details data 106a is six months, it is divided into six. Therefore, the order details data generation unit 102b generates the order details data 106b in FIG. 7, which includes six order detail records having the order amount of 30,000 yen obtained by dividing the invoice amount of 180,000 yen in the registered maintenance contract information data 106a by six, the expected sales date corresponding to the monthly orders, etc.

(2) Advance payment billing process Next, the billing for the current month is recorded through the advance payment billing process. The date of this advance payment billing process is assumed to be December 20, 2018. When this advance payment billing process is performed, as shown in FIG. 8, the billing completion category of the billing schedule record for billing schedule number 1 in the generated maintenance billing schedule data 106c is updated from "incomplete" to "completed," and the billing header data 106d and billing detail data 106d in FIG. 8 are generated.

(3) Confirmation of Sales for the Current Month Next, the order details for the current month are updated by accepting the pay-per-use data (acceptance data 106e in FIG. 9). The date of this acceptance is assumed to be 2019/2/5.

Since the date of receipt of the receipt data 106e in FIG. 9 is 2/5/2019, the order amount of 33,750 yen in the receipt data 106e in FIG. 9 can be said to be the confirmed order amount for January 2019. Here, since the planned sales date on which sales for January 2019 are recorded is 1/31/2019, the order detail record identification unit 102c identifies the order detail record (order amount 30,000 yen) of order line number 1 having the planned sales date 1/31/2019 from the maintenance order detail data 106b in FIG. 7 generated in (1). Note that the order detail record identification unit 102c may identify the order detail record using the three items of the order number, contract detail number, and order line number as keys. Specifically, the order detail record having the same combination of the order number, contract detail number, and order line number as the combination in the receipt data 106e may be identified from the maintenance order detail data 106b.

Then, the excess calculation unit 102d calculates the difference between the order amount of 30,000 yen in the order detail record identified by the order detail record identification unit 102c and the order amount of 33,750 yen in the receipt data 106e. In other words, the excess calculation unit 102d calculates the difference to be 3,750 yen.

Here, the billing distribution category in the maintenance contract detail data 106a registered in (1) is "monthly." In this case, the billing schedule data update unit 102e identifies a billing schedule record having a billing schedule date (2019/1/20) corresponding to the month (=2019) following the month (=2019/1/31) to which the sales schedule date (=2019/1/31) of the order detail record of order line number 1 identified by the order detail record identification unit 102c belongs. Referring to the maintenance billing schedule data 106c in FIG. 7 generated in (1), the billing schedule record of billing schedule number 2 has a billing schedule date of "2019/1/20," so the billing schedule data update unit 102e identifies the billing schedule record of billing schedule number 2. The billing schedule data update unit 102e then adds the difference of 3,750 yen calculated by the excess calculation unit 102d to the billing schedule amount of 30,000 yen in the billing schedule record for the identified billing schedule number 2, updating the billing schedule amount in the billing schedule record for billing schedule number 2 to 33,750 yen, thereby updating the maintenance billing schedule data 106c as shown in Figure 9. The values shown in hatching in the maintenance billing schedule data 106c in Figure 9 are the updated values.

(4) Recording of sales for the current month Finally, the order details for the current month are updated by the maintenance sales lump-sum processing. The date of the maintenance sales lump-sum processing is assumed to be February 5, 2019. When the maintenance sales lump-sum processing is performed, as shown in FIG. 10, the sales completion category of the order detail record for order line number 1 is updated from "incomplete" to "completed," and the sales header data 106f and sales detail data 106f in FIG. 10 are generated.

[3. Summary of the present embodiment]
Here, in the past, in pay-as-you-go contracts, billing was done after the sales amount was finalized, so advance billing was not anticipated. For this reason, when an advance payment was generated in the system under a pay-as-you-go contract, the advance was previously billed separately outside the system, and sales, billing, and payment settlement were done in the system after the amount was finalized. If an overage occurred, the overage was divided into separate details and a new invoice was issued. As a result, even though the processing was done within the same contract, the processing was split between inside and outside the system, which caused the problem of cumbersome operation.

In the face of these problems, the inventors focused on the methods of recording sales and billing for pay-per-click and pay-per-impression models in the online advertising industry. Originally, most pay-per-use contracts were operated on a sales and billing basis, but in recent years, a new business model has emerged in which points are purchased in advance, and then the advance payment is consumed according to the number of clicks or ad impressions, and sales are recorded.

Therefore, in this embodiment, for example, in a long-term fixed-term pay-as-you-go contract, the fee can be received in advance and then withdrawn to record sales, and any amount in excess of the amount received in advance can be invoiced together with the next scheduled invoice.

That is, in this embodiment, for example, the following two functions are realized.
(1) Even in the case of a pay-as-you-go contract, a certain amount is received in advance and used at the time of sale.
(2) When the monthly pay-as-you-go amount is finalized, the advance payment balance is checked, and if a shortfall occurs, a billing schedule for the shortfall is generated.

4. 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.

In addition, with regard to the excess reflection 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 excess reflection 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 excess reflection 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 excess reflection 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 Blu-ray (registered trademark) Disc, and a Blu-ray (registered trademark) Disc.

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

The present invention is useful, for example, in the IT (Information Technology) industry and the media industry.

100 Excess reflection device 102 Control unit
102a Billing schedule data generating unit
102b Order detail data generation unit
102c Order detail record identification unit
102d Excess calculation section
102e billing schedule data update unit 104 communication interface unit 106 storage unit
106a Contract Data
106b Order detail data
106c Billing schedule data
106d Billing Data
106e Acceptance Data
106f Sales data 108 Input/output interface unit 112 Input device 114 Output device 200 Server 300 Network

Claims (3)

An excess reflection device including a control unit,
billing schedule data including one billing schedule record having a billing schedule amount equal to the contract amount and a billing schedule date corresponding to the contract period, generated when the billing schedule generation class in the contract data including a contract amount, a billing schedule generation class, and a contract period is a lump-sum class meaning that the contract amount is billed in a lump sum, or billing schedule data including billing schedule records having the billing schedule amount when the contract amount is divided into each month and the billing schedule date corresponding to each month, generated when the billing schedule generation class in the contract data is a split class meaning that the contract amount is divided into each month and billed, for the number of divided months;
order detail data, which is generated based on the contract data, including order detail records each having an order amount when the contract amount is divided into monthly orders and a planned sales date corresponding to the monthly orders, the number of which corresponds to the number of divisions;
is accessible to
The control unit is
an order detail record specifying means for specifying, from the order detail data, an order detail record having a planned sales date on which sales for a certain month will be recorded in the confirmed order data including a confirmed order amount, which is a confirmed order amount for the certain month;
an excess amount calculation means for calculating the difference between the order amount included in the order detail record identified by the order detail record identification means and the confirmed order amount as an excess amount that is an amount that exceeds the contract amount ;
a billing schedule data updating means for updating the billing schedule data by adding to the billing schedule data a billing schedule record including a billing schedule date corresponding to the next contract period when the contract period is updated and the excess amount calculated by the excess amount calculation means when the billing schedule generation category in the contract data is the lump-sum category, and for updating the billing schedule data by adding to the billing schedule amount in the billing schedule record having a billing schedule date corresponding to the month following the month to which the planned sales date of the order detail record identified by the order detail record identifying means belongs when the billing schedule generation category in the contract data is the split category;
To have
An excess reflection device characterized by the above. An excess amount reflecting method executed by an information processing device having a control unit,
The information processing device includes:
billing schedule data including one billing schedule record having a billing schedule amount equal to the contract amount and a billing schedule date corresponding to the contract period, generated when the billing schedule generation class in the contract data including a contract amount, a billing schedule generation class, and a contract period is a lump-sum class meaning that the contract amount is billed in a lump sum, or billing schedule data including billing schedule records having the billing schedule amount when the contract amount is divided into each month and the billing schedule date corresponding to each month, generated when the billing schedule generation class in the contract data is a split class meaning that the contract amount is divided into each month and billed, for the number of divided months;
order detail data, which is generated based on the contract data, including order detail records each having an order amount when the contract amount is divided into monthly orders and a planned sales date corresponding to the monthly orders, the number of which corresponds to the number of divisions;
is accessible to
Executed by the control unit,
an order detail record identifying step of identifying an order detail record having a planned sales date on which sales for a certain month will be recorded in the confirmed order data including a confirmed order amount, which is a confirmed order amount for the certain month, from the order detail data;
an excess amount calculation step of calculating a difference between the order amount included in the order detail record identified in the order detail record identification step and the confirmed order amount as an excess amount that is an amount that exceeds the contract amount;
a billing schedule data updating step of updating the billing schedule data by adding to the billing schedule data a billing schedule record including a billing schedule date corresponding to the next contract period when the contract period is updated and the excess amount calculated in the excess amount calculation step when the billing schedule generation classification in the contract data is the lump-sum classification, and updating the billing schedule data by adding the excess amount calculated in the excess amount calculation step to the billing schedule amount in the billing schedule record having a billing schedule date corresponding to the month following the month to which the planned sales date of the order detail record identified in the order detail record identification step belongs when the billing schedule generation classification in the contract data is the split classification;
containing,
A method of reflecting excess amounts, characterized by the above. billing schedule data including one billing schedule record having a billing schedule amount equal to the contract amount and a billing schedule date corresponding to the contract period, generated when the billing schedule generation class in the contract data including a contract amount, a billing schedule generation class, and a contract period is a lump-sum class meaning that the contract amount is billed in a lump sum, or billing schedule data including billing schedule records having the billing schedule amount when the contract amount is divided into each month and the billing schedule date corresponding to each month, generated when the billing schedule generation class in the contract data is a split class meaning that the contract amount is divided into each month and billed, for the number of divided months;
order detail data, which is generated based on the contract data, including order detail records each having an order amount when the contract amount is divided into monthly orders and a planned sales date corresponding to the monthly orders, the number of which corresponds to the number of divisions;
A control unit of an information processing device having a control unit that can access
an order detail record identifying step of identifying an order detail record having a planned sales date on which sales for a certain month will be recorded in the confirmed order data including a confirmed order amount, which is a confirmed order amount for the certain month, from the order detail data;
an excess amount calculation step of calculating a difference between the order amount included in the order detail record identified in the order detail record identification step and the confirmed order amount as an excess amount that is an amount that exceeds the contract amount;
a billing schedule data updating step of updating the billing schedule data by adding to the billing schedule data a billing schedule record including a billing schedule date corresponding to the next contract period when the contract period is updated and the excess amount calculated in the excess amount calculation step when the billing schedule generation classification in the contract data is the lump-sum classification, and updating the billing schedule data by adding the excess amount calculated in the excess amount calculation step to the billing schedule amount in the billing schedule record having a billing schedule date corresponding to the month following the month to which the planned sales date of the order detail record identified in the order detail record identification step belongs when the billing schedule generation classification in the contract data is the split classification;
An excess reflection program for executing the above.

Images