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

Abstract

To provide an excess reflecting device, an excess reflecting method, and an excess reflecting program capable of reflecting the excess amount in scheduled billing data including the contract amount that is contracted in advance.SOLUTION: The present embodiment is configured to: if a billing category in contract data is "lump sum payment", update generated scheduled billing data by adding a scheduled billing record, which includes a scheduled billing date and an excess amount corresponding to a next contract period in the case where a contract period is updated, to scheduled billing data; and on the other hand, if the billing category in the contract data is "monthly", update the generated scheduled billing data by adding the excess amount to the scheduled billing amount in the scheduled billing record, which has the scheduled billing date corresponding to a month following a month to which the scheduled sales date belongs, wherein the scheduled sales date is included in a sales order detail record that is identified using receipt data.SELECTED DRAWING: Figure 5

Description

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

Patent Document 1 describes that when a user is provided with a resource that exceeds the expected usage amount of the user, a billing fee with the excess amount added can be calculated (see paragraph 0039 of Patent Document 1). ).

Japanese Unexamined Patent Publication No. 2015-225436

In the field of billing costs in consideration of such excess, there have been the following problems in the past. That is, in recent years, there has been an increasing number of business formats in which after purchasing points for a certain period of time with an advance payment, the advance payment is consumed by the number of clicks and the number of advertisements displayed, and sales are recorded.

However, when the contract amount contracted in advance is exceeded, it is necessary to issue a separate invoice for the excess amount, which is a very complicated operation. That is, in the past, it has been difficult to reflect the excess amount in the billing schedule data including the contract amount contracted in advance.

The present invention has been made in view of the above problems, and is an excess amount reflecting device capable of reflecting an excess amount in billing schedule data including a contract amount contracted in advance, an excess amount reflecting method, and an excess amount reflecting. The purpose is to provide a program.

In order to solve the above-mentioned problems and achieve the object, the excess amount reflecting device according to the present invention is provided with a control unit, and reflects the excess amount, which is the amount exceeding the contract amount contracted in advance, in the billing schedule data. It is a possible excess amount reflecting device, and the control unit means that the billing schedule generation category in the contract data including the contract amount, the billing schedule generation category, and the contract period bills the contract amount in a lump sum. In the case of a batch classification, 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 is generated, and the billing in the contract data is performed. When the schedule generation category is a split category that means that the contract amount is divided into each month and billed, the billing amount when the contract amount is divided into each month and the billing date corresponding to each month A billing schedule data generation means for generating billing schedule data including the number of months in which the billing schedule record having the above is divided, and an order amount when the contract amount is divided into monthly orders based on the contract data and the corresponding order amount. From the order detail data generation means for generating the order detail data including the divided number of the order detail records having the planned sales date corresponding to the monthly order, and the order detail data generated by the order detail data generation means. Order detail record specifying means for specifying an order detail record having a planned sales date in which sales of the certain month are recorded in the confirmed order data including the confirmed order amount, which is the confirmed order amount of the month, and the order detail record identification. The excess amount calculation means for calculating the difference between the order amount held by the order detail record specified by the means and the confirmed order amount as the excess amount, and the billing schedule generation category in the contract data are the batch categories. In some cases, the billing schedule record including the billing date corresponding to the next contract period when the contract period is renewed and the excess amount calculated by the excess amount calculation means is added to the billing schedule data. When the billing schedule data is updated and the billing schedule generation category in the contract data is the split category, the month following the month to which the scheduled sales date of the order detail record specified by the order detail record specifying means belongs. The billing schedule data update means for updating the billing schedule data by adding the excess amount calculated by the excess amount calculation means to the billing schedule amount in the billing schedule record having a corresponding billing schedule date. It is characterized by that.

Further, the excess amount reflecting method according to the present invention reflects the excess amount that can be reflected in the billing schedule data, which is the amount exceeding the contract amount contracted in advance, which is executed by the information processing apparatus provided with the control unit. It is a method, which means that the billing schedule generation category in the contract data including the contract amount, the billing schedule generation category, and the contract period, which is executed by the control unit, bills the contract amount in a lump sum. In the case of classification, 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 is generated, and the billing schedule generation in the contract data is generated. When the classification is a split classification that means that the contract amount is divided into each month and billed, the billing amount when the contract amount is divided into each month and the billing date corresponding to each month are set. Billing schedule data generation step to generate billing schedule data including the number of months when the billing schedule record to be held, and the order amount when the contract amount is divided into monthly orders based on the contract data and the monthly order amount From the order detail data generation step that generates the order detail data including the divided number of the order detail records having the planned sales date corresponding to the order, and the order detail data generated in the order detail data generation step, one month In the order detail record specifying step for specifying the order detail record having the planned sales date in which the sales of the relevant month are recorded in the confirmed order data including the confirmed order amount, which is the confirmed order amount, and the order detail record specifying step. When the excess amount calculation step for calculating the difference between the order amount held by the specified order detail record and the confirmed order amount as the excess amount and the billing schedule generation category in the contract data are the batch categories. , The billing schedule by adding a billing schedule record including the billing schedule date corresponding to the next contract period when the contract period is renewed and the excess amount calculated in the excess amount calculation step to the billing schedule data. When the data is updated and the billing schedule generation category in the contract data is the split category, it corresponds 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. Includes a billing schedule data update step that updates 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. Features ..

In addition, the excess amount reflecting program according to the present invention can reflect the excess amount, which is the amount exceeding the contract amount contracted in advance, in the billing schedule data for the information processing apparatus provided with the control unit to execute. It means that the billing schedule generation category in the contract data including the contract amount, the billing schedule generation category, and the contract period for the control unit to execute the reflection program bills the contract amount in a lump sum. In the case of a batch classification, 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 is generated, and the billing in the contract data is performed. When the schedule generation category is a split category that means that the contract amount is divided into each month and billed, the billing amount when the contract amount is divided into each month and the billing date corresponding to each month The billing schedule data generation step for generating billing schedule data including the number of months when the billing schedule record having and is divided, and the order amount when the contract amount is divided into monthly orders based on the contract data and the corresponding From the order detail data generation step that generates the order detail data including the divided number of the order detail records having the planned sales date corresponding to the monthly order, and the order detail data generated in the order detail data generation step. The order detail record identification step for specifying the order detail record having the planned sales date in which the sales of the certain month are recorded in the confirmed order data including the confirmed order amount which is the confirmed order amount of the month, and the order detail record identification The excess amount calculation step that calculates the difference between the order amount of the order details record specified in the step and the confirmed order amount as the excess amount, and the billing schedule generation category in the contract data are the batch categories. In some cases, the billing schedule record including the billing date corresponding to the next contract period when the contract period is renewed and the excess amount calculated in the excess amount calculation step is added to the billing schedule data. When the billing schedule data is updated and the billing schedule generation category in the contract data is the split category, in the month following the month to which the scheduled sales date of the order detail record specified in the order detail record specifying step belongs. A billing schedule data update step for 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 corresponding billing date. It is characterized by including.

According to the present invention, there is an effect that the excess amount can be reflected in the billing schedule data including the contract amount contracted in advance.

FIG. 1 is a block diagram showing an example of the configuration of the excess amount reflecting device. FIG. 2 is a diagram showing an example of correlation of each data. FIG. 3 is a diagram showing an example of a case registration process in the case of a consolidated pre-billing. FIG. 4 is a diagram showing an example of advance payment request processing in the case of a consolidated advance request. FIG. 5 is a diagram showing an example of processing for determining sales for the current month in the case of a consolidated advance billing. FIG. 6 is a diagram showing an example of processing for recording sales for the current month in the case of a consolidated advance billing. 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 advance payment request processing in the case of monthly advance request. FIG. 9 is a diagram showing an example of processing for determining sales for the current month in the case of monthly advance billing. FIG. 10 is a diagram showing an example of processing for recording sales for the current month in the case of monthly advance billing.

Hereinafter, the excess amount reflecting device, the excess amount reflecting method, and the embodiment of the excess amount reflecting program according to the present invention will be described in detail with reference to the drawings. The present invention is not limited to the present embodiment.

[1. composition]
An example of the configuration of the excess amount reflecting device 100 according to the present embodiment will be described with reference to FIG. FIG. 1 is a block diagram showing an example of the configuration of the excess amount reflecting device 100.

The excess amount reflecting device 100 is a commercially available desktop personal computer. The excess amount reflecting device 100 is not limited to a stationary information processing device such as a desktop personal computer, but is a portable personal computer, a PDA (Personal Digital Assistants), a smartphone, a tablet personal computer, or the like on the market. It may be a type information processing device.

The excess amount reflecting device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each part of the excess amount reflecting device 100 is communicably connected via an arbitrary communication path.

The communication interface unit 104 connects the excess amount reflecting device 100 to the network 300 so as to be communicable 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 another device via a communication line. Here, the network 300 has a function of connecting the excess amount reflecting device 100 and the server 200 so as to be able to communicate with each other, and is, for example, the Internet or a LAN (Local Area Network). Data of various masters and the like, which will be described later, 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. As the output device 114, a speaker or a printer can be used in addition to a monitor (including a home television). As the input device 112, in addition to a keyboard, a mouse, and a microphone, a monitor that cooperates with the mouse to realize a pointing device function can be used. In the following, the output device 114 may be referred to as a monitor 114, and the input device 112 may be referred to as a keyboard 112 or a mouse 112.

Various databases, tables, files, and the like are stored in the storage unit 106. In the storage unit 106, a computer program for giving an instruction to a CPU (Central Processing Unit) in cooperation with an OS (Operating System) to perform various processes is recorded. As the storage unit 106, for example, a memory device such as a RAM (Random Access Memory) or a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, or the like can be used.

The storage unit 106 includes, for example, contract data 106a, order detail data 106b, billing schedule data 106c, billing data 106d, acceptance data 106e (corresponding to "fixed order data" of the present invention), and sales data 106f. , Is equipped. Note that FIG. 2 shows an example of the correlation of each data.

As shown in FIGS. 3 and 7, for example, the contract data 106a includes an order number, a contract name, a billing destination, a customer, a slip amount (corresponding to the “contract amount” of the present invention), and a contract. Item number, product name, sales development category, billing development category (corresponding to the "billing schedule generation category" of the present invention), contract unit price, contract quantity, unit, contract amount, contract period start and Includes the end of the contract period (corresponding to the "contract period" of the present invention), and the like. The billing development classification (corresponding to the "billing schedule generation classification" of the present invention) is a "lump sum" classification (corresponding to the "collective classification meaning that the contract amount is billed in a lump sum" of the present invention) or " It is a "monthly" category (corresponding to the "divided category meaning that the contract amount is divided and billed in each month" of the present invention).

As shown in FIGS. 3 and 7, for example, the order detail data 106b includes an order number, a contract detail number, an order line number, a confirmed state, an order unit price, an order quantity, an order amount, and sales. Includes order detail records with expected dates, sales completion categories, and so on.

As shown in FIGS. 3 and 7, for example, the billing schedule data 106c includes an order number, a contract detail number, a billing schedule number, a billing schedule unit price, a billing schedule quantity, a billing schedule amount, and a billing schedule. Includes billing schedule records with date, billing completion category, and so on.

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

As shown in FIGS. 5 and 9, the receipt data 106e (corresponding to the “fixed order data” of the present invention) is, for example, an order number, a contract detail number, an order line number, an order quantity, and an order amount (corresponding to the “fixed order data” of the present invention). (Corresponding to the "fixed order amount, which is the fixed order amount for a certain month") of the present invention), and the like are included.

As shown in FIGS. 6 and 10, the sales data 106f includes, for example, a sales number, a customer, a sales date, a sales unit price, a sales quantity, a sales amount, a sales line number, and a product name. Etc. are included.

The control unit 102 is a CPU or the like that collectively controls the excess amount reflecting device 100. The control unit 102 has an internal memory for storing a control program such as an OS, a program that defines various processing procedures, required data, and the like, and performs various information processing based on these stored programs. Run.

Functionally, the control unit 102 means that, for example, (1) the billing schedule generation category in the contract data including the contract amount, the billing schedule generation category, and the contract period bills the contract amount in a lump sum. In the case of a batch classification, 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 is generated, and the billing in the contract data is performed. When the schedule generation category is a split category that means that the contract amount is divided into each month and billed, the billing amount when the contract amount is divided into each month and the billing date corresponding to each month The billing schedule data generation unit 102a as a billing schedule data generation means for generating billing schedule data including the number of months in which the billing schedule record having the above is divided, and (2) the contract amount is monthly based on the contract data. Order detail data generation as an order detail data generation means for generating order detail data including the number of order detail records having the order amount when the order is divided into orders and the planned sales date corresponding to the monthly order. From the order details data generated by the order detail data generation means and (3) the order details data generation means, the sales of the certain month in the fixed order data including the fixed order amount which is the fixed order amount of a certain month are recorded. The order detail record specifying unit 102c as the order detail record specifying means for specifying the order detail record having the scheduled date, (4) the order amount held by the order detail record specified by the order detail record specifying means, and the confirmed order. The excess amount calculation unit 102d as the excess amount calculation means for calculating the difference between the amount and the amount as the excess amount, and (5) when the billing schedule generation category in the contract data is the batch category, the contract period is set. The billing schedule data is updated by adding a billing schedule record including the billing schedule date corresponding to the next contract period in the case of renewal and the excess amount calculated by the excess amount calculation means to the billing schedule data. When the billing schedule generation category in the contract data is the split category, it has a billing date corresponding to the month following the month to which the sales schedule date of the order detail record specified by the order detail record specifying means belongs. The billing schedule data update unit 102e as a billing schedule data update means for updating the billing schedule data by adding the excess amount calculated by the excess amount calculation means to the billing schedule amount in the billing schedule record. I have.

When the billing schedule generation category in the contract data 106a including the contract amount, the billing schedule generation category, and the contract period is the batch category, the billing schedule data generation unit 102a has the same amount as the contract amount and the billing schedule amount. Generate billing schedule data 106c including one billing schedule record having a billing schedule date corresponding to the contract period.

On the other hand, when the billing schedule generation category in the contract data 106a is the split category, the billing schedule data generation unit 102a corresponds to the billing schedule amount when the contract amount is divided into each month and each month. Generate billing schedule data 106c including the number of months in which the billing schedule record having the billing schedule date is divided.

Based on the contract data 106a, the order detail data generation unit 102b divides the order detail record having the order amount when the contract amount is divided into monthly orders and the planned sales date corresponding to the monthly order. Generate order detail data 106b including only the number.

The order detail record specifying unit 102c records the sales of the month in the received data 106e including the fixed order amount, which is the fixed order amount of the month, from the order detail data 106b generated by the order detail data generation unit 102b. Identify the sales order item record that has the expected sales date.

The excess amount calculation unit 102d calculates the difference between the order amount held by the order detail record specified by the order detail record specifying unit 102c and the determined order amount as the excess amount.

When the billing schedule generation category in the contract data 106a is the batch category, the billing schedule data update unit 102e has a billing schedule date and an excess amount calculation unit 102d corresponding to the next contract period when the contract period is renewed. By adding the billing schedule record including the excess amount calculated in the above to the billing schedule data 106c, the billing schedule data 106c generated by the billing schedule data generation unit 102a is updated.

On the other hand, when the billing schedule generation category in the contract data 106a is the split category, the billing schedule data update unit 102e belongs to the sales schedule date of the order detail record specified by the order detail record specifying unit 102c. Generated by the billing schedule data generation unit 102a by adding the excess amount calculated by the excess amount calculation unit 102d to the billing schedule amount in the billing schedule record having the billing schedule date corresponding to the month following the month. The billing schedule data 106c is updated.

[2. Specific example of processing]
In this item, a specific example of the process in this embodiment will be described. The processing in the case of consolidated pre-billing will be described in the following [2-1], and the processing in the case of monthly pre-billing will be described in the following [2-2].

[2-1. For consolidated pre-billing]
In this item, the processing in the case of the consolidated pre-billing (that is, the case where the billing development category in the maintenance contract detail data 106a is “collective”) will be described in detail with reference to FIGS. 3 to 6.

(1) Item registration First, the item information is registered by inputting the maintenance contract information. The date of implementation of the registration shall be December 15, 2018. Specifically, the maintenance contract information data 106a and the maintenance contract detail data 106a of FIG. 3 are registered.

As shown in FIG. 3, the billing development category in the registered maintenance contract detail data 106a is “collective”. In this case, the billing schedule data generation unit 102a has the billing schedule amount of 180,000 yen, which is the same as the slip amount of 180,000 yen in the registered maintenance contract information data 106a, and the contract period "2019 /" in the registered maintenance contract detail data 106a. The maintenance billing schedule data 106c of FIG. 3 including the billing schedule record having the billing schedule date “2018/12/20” corresponding to “1 / 1/1 to 2019/6/30” and the like is generated.

Further, as shown in FIG. 3, the sales development category in the registered maintenance contract detail data 106a is “monthly”. In this case, the order detail data generation unit 102b divides the slip 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 6 months, it will be divided into 6 parts. Therefore, the order detail data generation unit 102b sets the order amount of 30,000 yen when the slip amount of 180,000 yen in the registered maintenance contract information data 106a is divided into six, the planned sales date corresponding to the monthly order, and the like. The order detail data 106b of FIG. 3 including six order detail records having is generated.

(2) Advance payment request processing Next, from the advance payment request processing, the bill for the current month is recorded. The implementation date of the advance payment request processing is assumed to be 2018/12/20. When the advance payment request processing is executed, as shown in FIG. 4, the classification of the request completion in the generated maintenance request schedule data 106c is updated from "incomplete" to "completed", and the request in FIG. 4 is performed. Header data 106d and billing detail data 106d are generated.

(3) Confirmation of sales for the current month Next, the order details for the confirmation for the current month are updated by receiving the pay-as-you-go data (acceptance data 106e in FIG. 5). The date of acceptance is assumed to be February 5, 2019.

Since the acceptance date of the acceptance data 106e in FIG. 5 is February 5, 2019, it can be said that the order amount of 33,750 yen in the acceptance data 106e in FIG. 5 is the confirmed order amount for January 2019. Here, since the planned sales date for recording sales for January 2019 is January 31, 2019, the order detail record specifying unit 102c is based on the maintenance order detail data 106b of FIG. 3 generated in (1). , Specify the order detail record (order amount 30,000 yen) of order line number 1 having the expected sales date 2019/1/31. The order detail record specifying unit 102c may specify the order detail record by using the order number, the contract detail number, and the order line number as keys. Specifically, the order number and the contract in the receipt data 106e. An order detail record having the same combination as the detail number and the order line number may be specified from the maintenance order detail data 106b.

Subsequently, the excess amount calculation unit 102d calculates the difference between the order amount of 30,000 yen held by the order detail record specified by the order detail record specifying unit 102c and the order amount of 33,750 yen in the received data 106e. That is, the excess amount calculation unit 102d calculates 3,750 yen as the difference.

Here, the billing development category in the maintenance contract detail data 106a registered in (1) is "collective". In this case, the billing schedule data update unit 102e updates the contract period "2019/1/1 to 2019/6/30" in the maintenance contract detail data 106a registered in (1), and the next contract period " Add a billing record with the scheduled billing date "2019/6/20" corresponding to "2019/7/1 to 2019/12/31" and the difference of 3,750 yen calculated by the excess calculation unit 102d, etc. As a result, as shown in FIG. 5, the maintenance request schedule data 106c is updated. The details indicated by hatching in the maintenance billing schedule data 106c of FIG. 5 are the added billing schedule records.

(4) Recording of sales for the current month Finally, the order details for the fixed amount for the current month are updated by the maintenance sales batch processing. The implementation date of the maintenance sales batch processing is assumed to be 2019/2/5. When the maintenance sales batch processing is executed, as shown in FIG. 6, the sales completion classification of the order detail record of the order line number 1 is updated from "incomplete" to "completed", and in FIG. Sales header data 106f and sales detail data 106f are generated.

[2-2. In case of monthly advance billing]
In this item, the processing in the case of monthly advance billing (that is, when the billing development category in the maintenance contract detail data 106a is "monthly") will be described in detail with reference to FIGS. 7 to 10.

(1) Item registration First, the item information is registered by inputting the maintenance contract information. The date of implementation of the registration shall be December 15, 2018. Specifically, the maintenance contract information data 106a and the maintenance contract detail data 106a of FIG. 7 are registered.

As shown in FIG. 3, the billing development category in the registered maintenance contract detail data 106a is “monthly”. In this case, the billing schedule data generation unit 102a divides the slip 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 detail data 106a is 6 months, it will be divided into 6 parts. Therefore, the billing schedule data generation unit 102a sets the billing schedule amount of 30,000 yen when the slip amount of 180,000 yen in the registered maintenance contract information data 106a is divided into six, the billing schedule date for monthly billing, and the like. The maintenance billing schedule data 106c of FIG. 7 including six billing schedule records having is generated.

Further, as shown in FIG. 7, the sales development category in the registered maintenance contract detail data 106a is “monthly”. In this case, the order detail data generation unit 102b divides the slip 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 6 months, it will be divided into 6 parts. Therefore, the order detail data generation unit 102b sets the order amount of 30,000 yen when the slip amount of 180,000 yen in the recorded maintenance contract information data 106a is divided into six, the planned sales date corresponding to the monthly order, and the like. The order detail data 106b of FIG. 7 including six order detail records having is generated.

(2) Advance payment request processing Next, from the advance payment request processing, the bill for the current month is recorded. The implementation date of the advance payment request processing is assumed to be 2018/12/20. When the advance payment request process is executed, as shown in FIG. 8, the billing completion classification of the billing schedule record of billing schedule number 1 in the generated maintenance billing schedule data 106c changes from "incomplete" to "completed". It is updated and the billing header data 106d and the billing detail data 106d of FIG. 8 are generated.

(3) Confirmation of sales for the current month Next, the order details for the confirmation for the current month are updated by receiving the pay-as-you-go data (acceptance data 106e in FIG. 9). The date of acceptance is assumed to be February 5, 2019.

Since the acceptance date of the acceptance data 106e in FIG. 9 is February 5, 2019, it can be said that the order amount of 33,750 yen in the acceptance data 106e of FIG. 9 is the confirmed order amount for January 2019. Here, since the planned sales date for recording sales for January 2019 is January 31, 2019, the order detail record specifying unit 102c is based on the maintenance order detail data 106b of FIG. 7 generated in (1). , Specify the order detail record (order amount 30,000 yen) of order line number 1 having the expected sales date 2019/1/31. The order detail record specifying unit 102c may specify the order detail record by using the order number, the contract detail number, and the order line number as keys. Specifically, the order number and the contract in the receipt data 106e. An order detail record having the same combination as the detail number and the order line number may be specified from the maintenance order detail data 106b.

Subsequently, the excess amount calculation unit 102d calculates the difference between the order amount of 30,000 yen held by the order detail record specified by the order detail record specifying unit 102c and the order amount of 33,750 yen in the received data 106e. That is, the excess amount calculation unit 102d calculates 3,750 yen as the difference.

Here, the billing development category in the maintenance contract detail data 106a registered in (1) is "monthly". In this case, the billing schedule data update unit 102e is in the month to which the scheduled sales date "2019/1/31" of the order detail record of the order line number 1 specified by the order detail record identification unit 102c belongs (= January 2019). Identify the billing record that has the billing date (2019/1/20) corresponding to the next month (= February 2019). With reference to the maintenance billing schedule data 106c of FIG. 7 generated in (1), since the billing schedule record of the billing schedule number 2 has the billing schedule date “2019/1/20”, the billing schedule data update unit 102e charges. Identify the billing schedule record for schedule number 2. Then, the billing schedule data update unit 102e adds the difference of 3,750 yen calculated by the excess amount calculation unit 102d to the billing schedule amount of 30,000 yen in the billing schedule record of the specified billing schedule number 2, and the billing schedule number 2 By updating the billing schedule amount in the billing schedule record to 33,750 yen, the maintenance billing schedule data 106c is updated as shown in FIG. The numerical value indicated by hatching in the maintenance request schedule data 106c of FIG. 9 is an updated numerical value.

(4) Recording of sales for the current month Finally, the order details for the fixed amount for the current month are updated by the maintenance sales batch processing. The implementation date of the maintenance sales batch processing is assumed to be 2019/2/5. When the maintenance sales batch processing is executed, as shown in FIG. 10, the sales completion classification of the order detail record of the order line number 1 is updated from "incomplete" to "completed", and in FIG. Sales header data 106f and sales detail data 106f are generated.

[3. Summary of this embodiment]
Here, in the past, in the pay-as-you-go contract, the billing act was performed after the sales amount was fixed, so there was no assumption that the pre-billing would be performed. For this reason, when advance payment occurs in a pay-as-you-go contract on the system, until now, the advance payment was separately billed outside the system, and after confirmation, sales, billing, and payment application processing were performed on the system. .. When an excess amount occurred, the excess amount was divided into separate items and an invoice was issued again. As a result, despite the processing within the same contract, there is a problem that the processing is divided inside and outside the system, which is a complicated operation.

In the face of these problems, the inventors focused on pay-per-click and impression-based sales accounting and billing methods in the online advertising industry. Originally, most of the pay-as-you-go contracts were sales and billing operations, but in recent years, after purchasing points with advance payment, the advance payment is consumed by the number of clicks and the number of advertisements displayed, and sales are recorded. Business forms are emerging.

Therefore, in the present embodiment, for example, in a long-term pay-as-you-go fixed-term contract, it is possible to receive the charge in advance and withdraw it to record sales, and the portion exceeding the advance receipt is set as the next billing amount. You can also request it.

That is, in this embodiment, for example, the following two functions have been realized.
(1) Even in the case of a pay-as-you-go contract, a certain amount of money is received in advance and applied at the time of sales.
(2) Check the advance payment balance when the monthly pay-as-you-go amount is fixed, and if a shortage occurs, generate a billing schedule for the shortage amount.

[4. Other embodiments]
In addition to the above-described embodiments, the present invention may be implemented in various different embodiments within the scope of the technical ideas described in the claims.

For example, of each of the processes described in the embodiments, all or part of the processes described as being automatically performed may be manually performed, or all of the processes described as being performed manually. Alternatively, a part thereof can be automatically performed by a known method.

In addition, the processing procedure, control procedure, specific name, information including parameters such as registration data and search conditions of each processing, screen examples, and database configuration shown in the present specification and drawings are not specified unless otherwise specified. Can be changed arbitrarily.

Further, with respect to the excess amount reflecting 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, with respect to the processing functions included in the excess reflection device 100, particularly each processing function performed by the control unit, all or any part thereof is realized by the CPU and a program that is interpreted and executed by the CPU. It may be realized as hardware by wired logic. The program is recorded on a non-temporary computer-readable recording medium including a programmed instruction for causing the information processing apparatus to execute the process described in the present embodiment, and the excess amount is reflected as necessary. It is read mechanically by the device 100. That is, a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or an HDD (Hard Disk Drive). This computer program is executed by being loaded into RAM, and cooperates with a CPU to form a control unit.

Further, this computer program may be stored in the application program server connected to the excess reflection device 100 via an arbitrary network, and all or a part thereof can be downloaded as needed. Is.

Further, the program for executing the process described in the present embodiment may be stored in a non-temporary computer-readable recording medium, or may be configured as a program product. Here, the "recording medium" includes a memory card, a USB (Universal Serial Bus) memory, an SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), and an EEPROM (registration). Trademarks) (Electrically Erasable and Programmable Read Only Memory), CD-ROM (Compact Disk Read Only Memory), MO (Magnet-Optical Disk), MO (Magnet-Optical Disk), MO (Magnet-Optical Disc), DVD (Digital), DVD (Digital) It shall include any "portable physical medium".

The "program" is a data processing method described in any language or description method, regardless of the format such as source code or binary code. The "program" is not necessarily limited to a single program, but is distributed as a plurality of modules or libraries, or cooperates with a separate program represented by the OS to achieve its function. Including things. A well-known configuration or procedure can be used for a specific configuration and reading procedure for reading the recording medium in each device shown in the embodiment, an installation procedure after reading, and the like.

Various databases and the like stored in the storage unit are memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and storage means such as optical disks, and are used for various processes and website provision. Stores programs, tables, databases, files for web pages, etc.

Further, the excess amount reflecting 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 an arbitrary peripheral device is connected. Further, the excess amount reflecting device 100 may be realized by mounting software (including a program or data) that realizes the processing described in the present embodiment on the device.

Further, the specific form of distribution / integration of the device is not limited to the one shown in the drawing, and all or a part thereof may be functionally or physically in an arbitrary unit according to various additions or functional loads. It can be distributed and integrated. That is, the above-described embodiments may be arbitrarily combined and implemented, or the embodiments may be selectively implemented.

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

100 Excess reflection device 102 Control unit
102a Billing schedule data generator
102b Order details data generation unit
102c Order detail record identification part
102d excess calculation unit
102e Billing schedule data update unit 104 Communication interface unit 106 Storage unit
106a Contract data
106b Order details 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)

It is an excess amount reflecting device that has a control unit and can reflect the excess amount, which is the amount exceeding the contract amount contracted in advance, in the billing schedule data.
The control unit
If the billing schedule generation category in the contract data including the contract amount, the billing schedule generation category, and the contract period is a batch category that means that the contract amount is billed in a lump sum, the billing schedule is the same as the contract amount. Billing schedule data including one billing schedule record having an amount and a billing schedule date corresponding to the contract period is generated, and the billing schedule generation category in the contract data divides the contract amount into each month. In the case of a split category that means billing, billing including the number of billing months in which the billing schedule record having the billing amount when the contract amount is split into each month and the billing date corresponding to each month is divided. Billing schedule data generation means to generate schedule data,
Based on the contract data, order detail data including the number of order detail records having the order amount when the contract amount is divided into monthly orders and the planned sales date corresponding to the monthly order is generated. Order detail data generation means and
From the order detail data generated by the order detail data generation means, an order detail record having a planned sales date in which the sales of the month in the fixed order data including the fixed order amount, which is the fixed order amount of the month, is recorded. Order detail record identification means to identify
An excess amount calculation means for calculating the difference between the order amount held by the order detail record specified by the order detail record specifying means and the confirmed order amount as the excess amount.
When the billing schedule generation category in the contract data is the batch category, the billing date corresponding to the next contract period when the contract period is renewed and the excess amount calculated by the excess amount calculation means are combined. When the billing schedule data is updated by adding the billing schedule record including the billing schedule data to the billing schedule data and the billing schedule generation category in the contract data is the division category, the order specified by the order detail record specifying means By adding the excess amount calculated by the excess amount calculation means to the billing amount in the billing record having the billing date corresponding to the month to which the planned sales date of the detail record belongs. Billing schedule data update means and billing schedule data update means
To prepare
An excess reflection device characterized by. It is an excess amount reflection method that can be executed by an information processing device equipped with a control unit and can reflect the excess amount, which is the amount exceeding the contract amount contracted in advance, in the billing schedule data.
Executed by the control unit,
If the billing schedule generation category in the contract data including the contract amount, the billing schedule generation category, and the contract period is a batch category that means that the contract amount is billed in a lump sum, the billing schedule is the same as the contract amount. Billing schedule data including one billing schedule record having an amount and a billing schedule date corresponding to the contract period is generated, and the billing schedule generation category in the contract data divides the contract amount into each month. In the case of a split category that means billing, billing including the number of billing months in which the billing schedule record having the billing amount when the contract amount is split into each month and the billing date corresponding to each month is divided. Billing schedule data generation step to generate schedule data, and
Based on the contract data, order detail data including the number of order detail records having the order amount when the contract amount is divided into monthly orders and the planned sales date corresponding to the monthly order is generated. Order details data generation step and
From the order detail data generated in the order detail data generation step, an order detail record having a planned sales date in which sales of the month in the confirmed order data including the confirmed order amount, which is the confirmed order amount of the month, is recorded. Order detail record identification step to identify
An excess amount calculation step for calculating the difference between the order amount held by the order detail record specified in the order detail record specifying step and the confirmed order amount as the excess amount.
When the billing schedule generation category in the contract data is the batch category, the billing date corresponding to the next contract period when the contract period is renewed and the excess amount calculated in the excess amount calculation step are combined. When the billing schedule data is updated by adding the billing schedule record including the billing schedule data to the billing schedule data and the billing schedule generation category in the contract data is the division category, the order specified in the order detail record specifying step By adding the excess amount calculated in the excess amount calculation step to the billing amount in the billing record having the billing date corresponding to the month to which the planned sales date of the detail record belongs. The billing schedule data update step to update the billing schedule data, and
Including,
A method of reflecting excess amount, which is characterized by. It is an excess amount reflection program that can reflect the excess amount, which is the amount exceeding the contract amount contracted in advance, in the billing schedule data for the information processing device equipped with the control unit to execute.
To make the control unit execute
If the billing schedule generation category in the contract data including the contract amount, the billing schedule generation category, and the contract period is a batch category that means that the contract amount is billed in a lump sum, the billing schedule is the same as the contract amount. Billing schedule data including one billing schedule record having an amount and a billing schedule date corresponding to the contract period is generated, and the billing schedule generation category in the contract data divides the contract amount into each month. In the case of a split category that means billing, billing including the number of billing months in which the billing schedule record having the billing amount when the contract amount is split into each month and the billing date corresponding to each month is divided. Billing schedule data generation step to generate schedule data, and
Based on the contract data, order detail data including the number of order detail records having the order amount when the contract amount is divided into monthly orders and the planned sales date corresponding to the monthly order is generated. Order details data generation step and
From the order detail data generated in the order detail data generation step, an order detail record having a planned sales date in which sales of the month in the confirmed order data including the confirmed order amount, which is the confirmed order amount of the month, is recorded. Order detail record identification step to identify
An excess amount calculation step for calculating the difference between the order amount held by the order detail record specified in the order detail record specifying step and the confirmed order amount as the excess amount.
When the billing schedule generation category in the contract data is the batch category, the billing date corresponding to the next contract period when the contract period is renewed and the excess amount calculated in the excess amount calculation step are combined. When the billing schedule data is updated by adding the billing schedule record including the billing schedule data to the billing schedule data and the billing schedule generation category in the contract data is the division category, the order specified in the order detail record specifying step By adding the excess amount calculated in the excess amount calculation step to the billing amount in the billing record having the billing date corresponding to the month to which the planned sales date of the detail record belongs. The billing schedule data update step to update the billing schedule data, and
Including,
Excess reflection program featuring.

Images