JP2007179383A - Method and program for calculating bill - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a method and a program for calculating a bill in such a manner that when a price plan is changed or when services are added, a system can easily be made to reflect them without being greatly modified. <P>SOLUTION: A bill creating apparatus 10 manages use logs along with several elements for determining unit prices, and manages unit prices for calculating the charge of each use log, together with the several elements for determining the unit prices. After the unit price for which the combination of the elements matches each use log is specified (step S101-S114), the charge of each use log is calculated on the basis of the unit price specified and the amount of unit use related to the use log (step S115, S116). <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a billing amount calculation method for calculating a billing amount based on a usage log and a unit price, and a billing amount calculation program for operating a computer as a device for realizing such a billing amount calculation method. Related.

  As is well known, the service provider stores each user's usage log and charges each user for a usage fee. A process of calculating a charge amount from a predetermined unit price and totaling the total charge amount for a certain period of use is periodically performed. Many service providers construct and operate a system for automatically performing the process of calculating the billing amount as described above.

Japanese Patent No. 3570233

  The above-described system calculates a charge amount according to an algorithm determined based on a charge plan provided to the user by the service provider. Therefore, the service provider has to modify the system or construct a new system separately when changing the rate plan or adding a new service.

  However, every time a price plan is changed or a service is added, if the system is modified or newly constructed, there is a problem that it takes time and costs.

  The present invention has been made in view of the problems of the prior art as described above, and the problem is that even when changing a price plan or adding a service, the system is not significantly modified. It is to make it easy to reflect them.

  The billing amount calculation method devised to solve the above problem is that each of all combinations in which the contents of elements necessary for a computer to determine a unit price for one use of a predetermined service are different from each other. Unit price definition procedure for storing correspondence information in which the combination and the unit price per unit quantity corresponding thereto are stored in the storage device, the usage amount of each time, and the usage for each use of a predetermined service A log accumulation procedure for storing in the storage device as usage log information in association with the contents of some elements necessary to determine the unit price to be multiplied by the amount, and a usage log recorded in the storage device in the log accumulation procedure For each piece of information, a unit price reading unit that reads correspondence information whose usage log information matches the combination of element contents from the storage device. When the correspondence information is read in the unit price reading procedure, the quotient obtained by dividing the usage amount included in the usage log information by the unit amount is multiplied by the unit price in the correspondence information, and indicated by the usage log information. A charge amount calculation procedure for calculating a charge amount for one use, and a section for storing the charge amount in the storage device in association with the use log information when the charge amount is calculated in the charge amount calculation procedure. It is characterized by executing the money saving procedure.

  When configured in this way, when changing a rate plan by separately adding or deleting elements necessary for determining the unit price, the corresponding information stored in the storage device is added or deleted. It is easy to update the corresponding information that is adapted to the change except for the elements to be added, and to add or remove the elements from the usage log information without making any major modifications to the system. The charge amount can be calculated with the changed price plan.

  In addition, the billing amount calculation program devised to solve the above-mentioned problem is a combination of all the combinations of different elements necessary for determining the unit price for one use of a predetermined service. For each of the above, unit price definition means for storing correspondence information in which the combination and the unit price per unit amount corresponding thereto are stored in the storage device, for each use of a predetermined service, Log storage means for storing in the storage device as usage log information in association with the contents of some elements necessary for determining the unit price to be multiplied by the usage amount, which is recorded in the storage device For each piece of usage log information, the unit price reading that reads from the storage device correspondence information that matches the combination of the usage log information and the element contents. When the unit price reading unit reads the correspondence information, the quotient obtained by dividing the usage amount included in the usage log information by the unit amount is multiplied by the unit price in the correspondence information and indicated by the usage log information. A charge amount calculating means for calculating a charge amount for a single use, and a charge amount stored in the storage device in association with the usage log information when the charge amount calculating means calculates the charge amount. It is characterized by functioning as a storage means.

  Therefore, according to this billing amount calculation program, a computer can be operated as an apparatus for realizing the above-described billing amount calculation method according to the present invention.

  As described above, according to the present invention, even when a charge plan is changed or a service is added, they can be easily reflected without making a major correction to the system.

  Hereinafter, five best modes for carrying out the present invention will be described in detail with reference to the accompanying drawings.

Embodiment 1

  FIG. 1 is a configuration diagram of a bill creation apparatus 10 according to the first embodiment.

  The bill creation apparatus 10 according to the first embodiment is a personal computer in which bill creation software 15 described later is installed in order to realize a bill creation function sent to a user for use of a predetermined service. It is.

  A personal computer constituting the bill creation apparatus 10 includes a display device 10a such as a liquid crystal display, an input device 10b such as a keyboard and a mouse, a printing device 10c such as a local printer and a network printer, and a main body. The main body includes known hardware such as a CPU [Central Processing Unit] 10d, a DRAM [Dynamic Random Access Memory] 10e, an MDD [Multi Disk Drive] 10f, and an HDD [Hard Disk Drive] 10g.

  The HDD 10g stores basic software 11. The basic software 11 controls input / output in the display device 10a and the input device 10b, controls output in the printing device 10c, and storage areas (storage elements, CD [Compact Disk], DVD) of the DRAM 10e, MDD 10f, and HDD 10g. This is software that provides basic functions such as read / write control to the [Digital Versatile Disk] and HD [Hard Disk] storage areas) to many application software.

  Further, a usage log table 12, a charge definition table 13, a charge definition table 14, and an invoice creation software 15 are installed in the HDD 10g. The charge definition table 13 and the charge definition table 14 are prepared for each of various charge plans prepared by the service provider for each user, and one charge plan is assigned to one charge definition table. 13 and one fee definition table 14.

  The usage log table 12 is a table for recording the usage history of the service. The usage log table 12 corresponds to the log accumulation procedure and log accumulation means described above.

  FIG. 2 is a diagram showing an example of the data structure of the usage log table 12.

  The usage log table 12 in FIG. 2 has the same number of records as the number of times the service is used. Each record has fields of “date”, “user information”, “code”, “element 1”, “element 2”,..., “Element 10”, “unit usage”, and “billing amount”. ing.

  The “date” field is a field in which the date on which the service is used is recorded. The “user information” field is a field in which user information for individually identifying each user from among a large number of users is recorded. In the “Code” field, code information indicating a rate plan with which the user indicated by the user identification information contracts with the provider of the service among various price plans provided by the service provider. The field to be recorded.

  The “element n” field is a field in which an element necessary for determining a unit price to be multiplied by the usage amount is recorded. Here, the factors create a unit price difference in the charge system. For example, in the printing service, there are paper size, color, paper quality, etc. In the calling service, the calling distance, calling time zone, day of the week, etc. There is. In the first embodiment, ten “element n” fields are prepared in the usage log table 12, and “element n” has a larger value of n than the number of elements necessary for determining the unit price. The field is blank.

  The “unit usage amount” field is a field in which the usage amount related to one use of the user is recorded. The “billing amount” field is a field in which an amount charged for one use of the user is recorded. This “billing amount” field is blank until the billing amount is calculated by the bill creation software described later.

  The charge definition table 13 is a table used for calculating a charge amount generated for one use of the service. The billing definition table 13 corresponds to the unit price definition procedure and the unit price definition means described above.

  FIG. 3 is a diagram showing an example of the data structure of the charge definition table 13.

  The charge definition table 13 of FIG. 3 has the same number of records as the combination pattern of each element in one charge plan. Each record includes “element 1”, “element 2”,..., “Element 10”, “unit quantity”, “unit price”, “free portion”, “basic charge amount”, “maximum charge amount”, and “minimum charge amount”. “Charging amount” field.

  The “element n” field is a field in which an element necessary for determining the unit price is recorded. Similar to the usage log table 12, the charge definition table 13 also includes 10 “element n” fields, and “element n” having a value of n larger than the number of elements necessary for determining the unit price. "Field is blank.

  The “unit quantity” field is a field in which a quantity serving as a unit to which a unit price is imposed is recorded. The “unit price” field is a field in which a unit price per unit quantity is recorded. If this rate plan is a rate plan that does not perform metered billing, the “unit price” field is blank or “0 yen”.

  The “free equivalent” field is a field in which the maximum usage amount that can be reduced as a privilege equivalent to discounting from the usage amount used for one use is recorded as a free equivalent amount. If this rate plan is a rate plan that does not provide a free equivalent reduction service, the “free equivalent” field is blank.

  The “basic charge amount” field is a field in which the basic charge amount imposed on the user regardless of the use amount is recorded for one use. Note that if this charge plan is a charge plan that does not impose a basic charge on a user for a single use, the “basic charge” field is blank.

  The “maximum billing amount” field is a field in which the maximum billing amount is recorded when so-called cap-based billing is employed for one use. Here, the cap-based billing is the maximum that the sum of the basic billing amount and the pay-as-you-go billing amount ({(unit usage) / (unit quantity): rounded up after the decimal point} × (unit price)) is the set upper limit. If the charge amount does not exceed the charge amount, the total amount is charged to the user as the charge amount for one use, and if the sum exceeds the set maximum charge amount, the set maximum charge amount is charged. Is billed to the user as a billing amount for one use. If this rate plan is a rate plan that does not employ cap-based charging for a single use, the “maximum charge amount” field is blank.

  The “minimum charge amount” field is a field in which the minimum charge amount when a so-called minimum charge system charge is adopted for one use is recorded. Here, the minimum charge system charge is a charge that is applied to one use as it is when the sum of the basic charge amount and the pay-as-you-go charge amount exceeds the minimum charge amount that is the preset lower limit. A billing method in which the user is charged as an amount of money, and when the sum does not exceed the set minimum charge amount, the set minimum charge amount is charged to the user as a charge amount for one use. To tell. Note that if this rate plan is a rate plan that does not employ a minimum charge system charge for a single use, the “minimum charge amount” field is blank.

  The charge definition table 14 is a table used to calculate a billing charge amount for the use of the service for a certain period of time of the user. Although this charge definition table 14 is not shown because it is not related to the present invention, if it is simply explained, if the total charge amount for the use of the service for a certain period is a pay-per-use charge, the charge-rate table 14 Free equivalent charge to be deducted, basic charge to be added to the pay-as-you-go charge, maximum usage charge of the sum of pay-to-use charge and basic charge when adopting cap charge, pay-as-you-go charge and basic charge when adopting minimum charge charge Defines the minimum usage charge for the sum of

  The bill creation software 15 is software for creating a bill sent to each user of the service. The bill creation software 15 includes a billing amount calculation module (program) 15a, a billing total amount calculation module (program) 15b, and a bill printing module (program) 15c.

  The charge amount calculation module 15a is a so-called rating module that calculates the amount to be charged to the user for one use of the service. The contents of the processing performed by the CPU 10d according to the billing amount calculation module 15a will be described later in detail with reference to FIGS. 4 and 5. However, if briefly described, the contents are accumulated in the usage log table 12. For each usage log, the charge amount is calculated based on the contents of the charge definition table 13. The billing amount calculation module 15a may be set to operate periodically such as monthly or weekly, or may be operated at any time by the service provider. Also good.

  The billing total amount calculation module 15b aggregates the total amount charged for using the service for a certain period of time for each user as a pay-per-use charge, and reduces the free charge or adds the basic charge from the pay-per-use charge. This is a pricing module for determining the total amount charged. The processing performed by the CPU 10d in accordance with the billed total amount calculation module 15b is general and irrelevant to the present invention, and therefore the description of the processing content is omitted.

  The bill printing module 15c is a module that prints the bill total determined by the bill total calculation module 15b for each user on a predetermined bill through the printing apparatus 10c. The processing performed by the CPU 10d according to the invoice printing module 15c is also general and irrelevant to the present invention, and therefore the description of the processing content is omitted.

  4 and 5 are diagrams showing the flow of processing by the billing amount calculation module 15a.

  After the start of the process, the CPU 10d executes a first process loop (L1). Specifically, the CPU 10d specifies one record in the usage log table 12 as a processing target, and performs steps S101 to S117 for the record specified as the processing target. The CPU 10d performs such processing one by one for all the records in the usage log table 12, and ends the processing according to FIGS. 4 and 5 when the processing is completed for all the records.

  In step S101, the CPU 10d performs a process of substituting “1” for the variable n, and advances the process to step S102.

  In step S102, the CPU 10d reads the value of the “element n” field in the processing target record.

  In the next step S103, the CPU 10d determines whether or not the read value is a valid value (whether or not the field is not blank). If the read value is a valid value, the CPU 10d branches the process from step S103 to step S104.

  In step S104, the CPU 10d determines whether or not the substitution value of the variable n is “1”. Then, when the substitution value of the variable n is “1”, the CPU 10d branches the process from step S104 to step S105.

  In step S105, the CPU 10d searches the accounting definition table 13 specified by the code information stored in the “code” field of the processing target record for a record including the value read in step S102 in the element n. .

  In the next step S106, the CPU 10d determines whether or not a record including the value read in step S102 in the element n can be detected from the accounting definition table 13. When the record including the value read in step S102 in element n can be detected from the accounting definition table 13, the CPU 10d branches the process from step S106 to step S107.

  In step S107, the CPU 10d performs a process of storing a record detected from the charge definition table 13 in a work table (not shown), and the process proceeds to step S111.

  In step S111, the CPU 10d performs a process of incrementing the substitution value of the variable n by “1”.

  In step S112, the CPU 10d determines whether or not the substitution value of the variable n is “11”. If the substitution value of the variable n is not “11”, the CPU 10d returns the process from step S112 to step S102.

  On the other hand, when the substituted value of the variable n is not “1” in step S104, the CPU 10d advances the process to step S108.

  In step S108, the CPU 10d searches the charge definition table 13 indicated by the code information stored in the “code” field of the processing target record for a record including the value read in step S102 in the element n.

  In the next step S109, the CPU 10d determines whether or not a record including the value read in step S102 in the element n can be detected from the charging definition table 13. When the record including the value read in step S102 in element n can be detected from the accounting definition table 13, the CPU 10d branches the process from step S109 to step S110.

  In step S110, the CPU 10d performs a process of deleting all records other than the record detected from the accounting definition table 13 from a work table (not shown), and advances the process to step S111.

  The processing loop of steps S102 to S112 described above corresponds to the unit price reading procedure described above, and the CPU 10d that executes this processing loop corresponds to the unit price reading unit described above.

  During the execution of the processing loop of steps S102 to S112, when the value of the “element n” field of the processing target record is no longer valid (step S103; NO), or the value of the variable n reaches “11”. If so (step S112; YES), the CPU 10d advances the process to step S113.

  In step S113, the CPU 10d searches this work table in order to check whether or not a record is included in a work table (not shown).

  In the next step S114, the CPU 10d determines whether or not only one record has been detected from a work table (not shown) as a result of the search. Then, when only one record can be detected from the work table (not shown), the CPU 10d advances the process from step S114 to step S115.

In step S115, the CPU 10d performs a process of calculating a charge amount for the processing target record. Specifically, the CPU 10d determines the value of the “unit usage” field of the processing target record and the “unit quantity”, “unit price”, “free equivalent” of one record remaining in the work table (not shown), and Based on the value of the “basic billing amount” field, the billing amount is calculated according to the following calculation formula.
Formula: (billing amount) = (basic billing amount) + [{(unit usage amount)-(free equivalent amount)} ÷ (unit quantity)] x (unit price)
In addition, when the (unit usage amount) − (free portion) in the above calculation formula has a negative value, the CPU 10d changes the value of the portion to zero. In addition, when the {(unit usage) − (free equivalent)} ÷ (unit quantity) portion in the above calculation formula is a value having a fractional part, the value of that part is rounded up to the next decimal point. Change the value to

  Further, the CPU 10d calculates the charge amount in the above formula, and then refers to the values of the “maximum charge amount” and “minimum charge amount” fields of one record remaining in the work table (not shown), If the charge amount calculated using the above formula exceeds the maximum charge amount when the amount is set, the charge amount is changed to the same amount as the maximum charge amount, and the minimum charge amount is set. In this case, if the charge amount calculated using the above calculation formula does not exceed the minimum charge amount, the charge amount is changed to the same amount as the minimum charge amount.

  This step S115 corresponds to the above-described charging amount calculation procedure, and the CPU 10d that executes this step S115 corresponds to the above-described charging amount calculation means.

  In the next step S116, the CPU 10d performs a process of storing the charge amount calculated in step S115 in the “charge amount” field of the processing target record in the usage log table 12 of FIG.

  Note that this step S116 corresponds to the above-described charging amount storage procedure, and the CPU 10d that executes this step S116 corresponds to the above-described charging amount storage means.

  Further, when the processing loop of steps S102 to S112 is being executed, the CPU 10d cannot detect a record including the value read in step S102 in the element n from the charging definition table 13 (step S106; NO, or step (S109; NO), or when no record is detected from a work table (not shown), or when two or more records are detected (step S114; NO), the process proceeds to step S117.

  In step S117, the CPU 10d performs processing for storing information indicating an error in the “billing amount” field of the processing target record in the usage log table 12 of FIG.

  In the first embodiment described above, the usage log is managed together with some elements for determining the unit price (FIG. 2), and the unit price is also managed together with some elements for determining the unit price. (Figure 3). The charge amount for each usage log is determined based on the specified unit price and the unit usage amount related to the usage log after the unit price at which the combination of elements matches the usage log is specified (steps S101 to S114). Are calculated (steps S115 and S116).

  Here, the charge amount is calculated according to the charge plan defined in the contract that the user exchanges with the service provider. When a service provider wants to change the contents of one rate plan, the calculation formula for calculating the usage fee was created as the most appropriate for the rate plan at that time in the conventional system. A major change was needed. On the other hand, in the first embodiment, it is only necessary to add or delete a record that conforms to the new price plan from the charge definition table 13.

  FIG. 6 is a diagram showing an example in which the contents of the charging definition table 13 of FIG. 3 are partially changed.

  FIG. 3 shows an example of a charge plan for a printing service. In FIG. 3, the element 1 that defines the type of ink used for printing and the size of the printing paper are defined as elements for determining the unit price. Element 2 to be determined is determined, and elements equal to or higher than element 3 are not determined.

  On the other hand, FIG. 6 shows an example in which the paper quality of the printing paper is newly added as an element that causes a difference in unit price in the charge plan according to FIG. 3, and the element 1 that defines the type of ink and the printing paper In addition to the element 2 that defines the size of the printing paper, an element 3 that defines the paper quality of the printing paper is further defined. For example, in FIG. 2, there is only one record in which element 1 is “black and white” and element 2 is “A4 or less”, but in FIG. 6, element 1 is “black and white” and element 2 is “A4”. There are a number of records that can be included in the element 3 (in FIG. 6, two types of “quality paper” and “plain paper”).

  In this way, when changing a rate plan by adding an element for determining a unit price, a record that matches the change is added to or deleted from the charge definition table 13, and a new charge definition table 13 ′ is added. This makes it possible to easily calculate the charge amount with the changed price plan without significantly changing the system.

  Further, in the first embodiment, the basic charge amount, the free equivalent amount, the maximum charge amount, and the minimum charge amount set in the charge definition table 13 are appropriately changed so that the charge amount required for one use is changed. The amount of change according to the unit usage can be changed. Specifically, it is as follows.

  FIG. 7A is an exemplary diagram of the charging definition table 13 ″ when the flat rate charging is adopted, and FIG. 7B is a graph showing the relationship between the charging amount and the unit usage amount in the flat rate charging. As shown in Fig. 7, if only the basic charge amount is set and none of the unit price, free equivalent, maximum charge amount, or minimum charge amount is set, the charge amount is independent of the change in unit usage. Is constant (flat-rate billing).

  FIG. 8A is an exemplary diagram of a charging definition table 13 ″ when simple usage-based charging is employed, and FIG. 8B shows the relationship between the charging amount and unit usage in simple usage-based charging. As shown in Fig. 8, when only unit quantity and unit price are set and no free equivalent, basic charge amount, maximum charge amount, and minimum charge amount are set, the unit usage amount The billing amount also simply increases with a simple increase (simple metered billing).

  FIG. 9 (a) is an illustration of a billing definition table 13 ″ when pay-as-you-go with basic billing is adopted, and FIG. 9 (b) shows billing in metered billing with basic billing. It is a graph showing the relationship with the unit usage amount, as shown in Fig. 9. The unit quantity, unit price and basic charge amount were set, and no free equivalent, maximum charge amount, and minimum charge amount were not set. In this case, the basic charge amount is added to the charge amount that simply increases as the unit usage amount increases (a metered charge with a basic charge amount).

  FIG. 10 (a) is an illustration of a billing definition table 13 ″ when pay-as-you-go billing with discount benefits is employed, and FIG. 10 (b) shows billing amounts and unit usage in pay-as-you-go billing with discount benefits. 11 is a graph showing the relationship with the amount, when only the unit quantity, unit price and free equivalent are set, and none of the basic charge amount, maximum charge amount, and minimum charge amount is set, as shown in FIG. There is no billing amount until the predetermined usage amount is reached, and after the predetermined usage amount is reached, the billing amount increases with a simple increase in the unit usage amount (pay-as-you-go with discount benefits).

  FIG. 11A is an exemplary diagram of a charging definition table 13 ″ when step type metered charging is adopted, and FIG. 11B shows the billing amount and unit usage in step type metered charging. As shown in Fig. 11, the unit quantity is set to a value larger than the minimum number (in the printing service, the minimum number is one, so two or more values are set to the unit quantity). If the basic charge amount, maximum charge amount, and minimum charge amount are not set, the charge amount increases step by step each time the unit usage reaches a multiple of the unit quantity (step type) Note that in the step billing system, the free equivalent may be set or may not be set.

  FIG. 12A is an exemplary diagram of a charging definition table 13 ″ when cap-based charging is adopted, and FIG. 12B is a graph showing the relationship between the charging amount and unit usage in cap-based charging. As shown in Fig. 12, if the unit quantity, unit price, and maximum charge amount are set, and the free charge, basic charge amount, and minimum charge amount are not set, the unit usage amount is simply increased. Along with this, the billing amount simply increased, and when the billing amount reached the maximum billing amount, the billing amount reached its peak, and the same amount as the maximum billing amount was maintained regardless of the increase in unit usage (cap system). Billing).

  FIG. 13A is an exemplary diagram of the charging definition table 13 ″ when the minimum charge system charging is adopted, and FIG. 13B shows the relationship between the charging amount and the unit usage amount in the minimum charge system charging. 13, the unit quantity, unit price and minimum charge amount (or free equivalent amount and basic charge amount) are set, the free equivalent amount and basic charge amount (or minimum charge amount), and If no maximum charge amount is set, the charge amount remains the same as the minimum charge amount until reaching the minimum charge amount regardless of the increase in unit usage, and reaches the minimum charge amount. Then, it simply increases with a simple increase in unit usage (minimum charge system charging).

  FIG. 14A is an exemplary diagram of a charging definition table 13 ″ when double flat-rate billing is adopted, and FIG. 14B shows the relationship between the billing amount and unit usage in double flat-rate billing. 14, the unit quantity, unit price, maximum charge amount and minimum charge amount (or free equivalent amount and basic charge amount) are set, and the free equivalent amount and basic charge amount (or minimum charge) are set. If the amount is not set, the billing amount will remain the same as the minimum billing amount until the minimum billing amount is reached, regardless of the increase in unit usage. When the billing amount reaches the maximum billing amount, the billing amount reaches a peak when the amount simply increases, and remains constant at the same amount as the maximum billing amount regardless of the increase in unit usage ( Double flat rate billing).

  As described above, when changing the charge plan by changing the relationship between the charge amount calculated for one use and the unit use amount, a record suitable for the change is added to or deleted from the charge definition table 13. Then, by creating a new billing definition table 13 ″, it is possible to easily calculate the billing amount with the billing plan after the change without significantly changing the system.

  By the way, the usage log table 12 of the first embodiment stores the usage log of the printing service as shown in FIG. This usage log may be stored in the usage log table 12 each time usage of the service occurs by a usage log storage function (not shown), but is stored in a print log table in another system. Alternatively, it may be copied to the usage log table 12 of FIG. 2 by a copy function (not shown).

  In the latter case, at the same time as copying the usage log to the usage log table 12 of FIG. 10 must be generated.

  FIG. 15 is a diagram illustrating an example of the print log table 21 in another system.

  Each record of the print log table 21 of another system shown in FIG. 15 has fields of “date”, “user information”, “size”, “color”, and “number of sheets”. When the log record of the print log table 21 is copied to the usage log table 12 of FIG. 2, the value of the “size” field becomes the value of the “element 1” field, and the value of the “color” field becomes “element” It is necessary to perform processing so that the value of the “2” field becomes the value of the “number of sheets” field and the value of the “unit usage” field.

  FIG. 16 is a diagram illustrating an example of the contract management table 22 in another system.

  Each record of the contract management table 22 in another system shown in FIG. 16 has fields of “user information”, “code”, and “service name”. In a separate system, a plurality of fee schedules are prepared, and in this contract management table 22, it is defined by which charge plan the user is contracted by associating user information and code information. Has been.

  FIG. 17 is a diagram showing an example of the fee table 23 in another system.

  In the charge table 23 in another system shown in FIG. 17, the unit price per unit quantity and the printing condition calculated by the unit price are defined in a state of being associated with each other. When generating the charge definition table 13 of FIG. 3 based on the information of the charge table 23, each element included in the print conditions in the charge table 23 is stored in the “element n” field of the charge definition table 13. The unit quantity and the unit price in the fee table 23 must be processed so as to be stored in the “unit quantity” and “unit price” fields of the charge definition table 13.

Embodiment 2

  FIG. 18 is a diagram illustrating an example of a data structure of the usage log table 16 according to the second embodiment. 19 and 20 are diagrams showing an example of the data structure of the charge definition table 17.

  18 and FIG. 2 and FIG. 19 and FIG. 20 and FIG. 3 are compared, each record of the usage log table 16 of the second embodiment is the same as that of the first embodiment. The accounting definition table 17 of the second embodiment has exactly the same fields as those of the first embodiment. The difference from the first embodiment is that the usage log stored in the usage log table 16 and the unit price defined in the accounting definition table 17 relate to the call service.

  As described above, the data structure of the usage log table and the data structure of the charge definition table are unified in the first embodiment and the second embodiment regardless of the difference in the service contents and the charge plan. 4 and the accounting algorithm shown in FIG. 5 can be used as a standardized algorithm.

  Incidentally, even in the second embodiment, the usage log may be stored in the usage log table 16 every time the service is used by a usage log storage function (not shown). It may be stored in the call log table in the system and copied to the usage log table 16 of FIG. 18 by a copy function (not shown).

  In the latter case, at the same time as copying the usage log to the usage log table 16 of FIG. 10 must be generated.

  FIG. 21 is a diagram showing an example of a call log table 31 in another system.

  Each record of the call log table 31 of another system shown in FIG. 21 has fields of “date”, “calling number”, “incoming number”, “call start time”, and “call end time”. . When the log record of the print log table 31 is copied to the usage log table 12 of FIG. 2, the value of the “calling number” field becomes the value of the “user information” field, and the value of the “calling number” field The destination type (city / city type) and distance determined from the value in the “Destination Number” field are the values in the “Element 1” and “Element 2” fields, and are determined from the values in the “Date” field. The type of day of the week (weekday, holiday type) and time zone type (daytime, nighttime, or midnight type) are the values of the “element 3” and “element 4” fields, and the value of the “call start time” field It is necessary to perform processing so that the unit usage determined from the value of the “call end time” field becomes the value of the “unit usage” field.

  FIG. 22 is a diagram showing an example of the contract management table 32 in another system.

  Each record of the contract management table 32 in another system shown in FIG. 22 has fields of “contract number”, “code”, and “service name”. In the separate system, a plurality of fee schedules are prepared, and in this contract management table 32, it is defined by which contract plan the user is contracted by associating the contract number with the code information. ing.

  FIG. 23 is a diagram showing an example of the fee table 33 in another system.

  In the charge table 33 in another system shown in FIG. 23, the unit price per unit quantity and the call condition (call destination type, distance, day type, time zone type) to which the unit price is applied are associated with each other. Defined in When generating the charge definition table 17 of FIGS. 19 and 20 based on the information of the charge table 33, each element included in the call condition in the charge table 33 is an “element n” field of the charge definition table 17. And the unit quantity and unit price in the fee table 33 must be processed so as to be stored in the “unit quantity” and “unit price” fields of the charge definition table 13.

Embodiment 3

  FIG. 24 is a diagram illustrating an example of a data structure of the charge definition table 41 according to the third embodiment.

  As is clear from comparison between FIG. 24 and FIG. 3, each record of the charge definition table 41 of the third embodiment has exactly the same fields as that of the first embodiment. Although not shown, each record of the usage log table of the third embodiment has exactly the same field as that of the first embodiment. The difference from the first embodiment is that the unit price defined in the charging definition table 41 and the usage log stored in the usage log table (not shown) relate to the packet communication service. .

  In this way, the data structure of the usage log table and the data structure of the charge definition table are unified regardless of the content of the service and the charge plan, so that both the first embodiment and the third embodiment 4 and the accounting algorithm shown in FIG. 5 can be used as a standardized algorithm.

Embodiment 4

  FIG. 25 is a diagram illustrating an example of a data structure of the charge definition table 42 according to the fourth embodiment.

  As is obvious from comparison between FIG. 25 and FIG. 3, each record of the charge definition table 42 of the fourth embodiment has exactly the same fields as that of the first embodiment. Although not shown, each record of the usage log table of the fourth embodiment has exactly the same field as that of the first embodiment. The difference from the first embodiment is that the unit price defined in the charging definition table 42 and the usage log stored in the usage log table (not shown) relate to the parcel delivery service. .

  As described above, the data structure of the usage log table and the data structure of the charge definition table are unified regardless of the content of the service or the charge plan, so that both the first embodiment and the fourth embodiment 4 and the accounting algorithm shown in FIG. 5 can be used as a standardized algorithm.

Embodiment 5

  FIG. 26 is a diagram illustrating an example of a data structure of the charge definition table 43 according to the fifth embodiment.

  As is clear by comparing FIG. 26 and FIG. 3, each record of the accounting definition table 43 of the fifth embodiment has exactly the same fields as that of the first embodiment. Although not shown, each record in the usage log table of the fifth embodiment has exactly the same field as that of the first embodiment. The difference from the first embodiment is that the unit price defined in the charging definition table 43 and the usage log stored in the usage log table (not shown) relate to the taxi service.

  As described above, the data structure of the usage log table and the data structure of the charge definition table are unified in the first embodiment and the fifth embodiment regardless of the content of the service and the charge plan. 4 and the accounting algorithm shown in FIG. 5 can be used as a standardized algorithm.

Configuration diagram of bill creation device of first embodiment The figure which shows an example of the data structure of a use log table The figure which shows an example of the data structure of a charge definition table The figure which shows the flow of processing by the billing amount calculation module The figure which shows the flow of processing by the billing amount calculation module The figure which shows the example which changed the content of the charge definition table of FIG. 3 partially (A) Illustration of charge definition table and (b) Graph showing relationship between charge amount and unit usage when flat-rate charge is adopted (A) Illustrative diagram of billing definition table and (b) Graph showing relationship between billing amount and unit usage when simple metered billing is adopted (A) Illustrative diagram of billing definition table when adopting pay-as-you-go billing with basic billing amount, and (b) graph showing the relationship between billing amount and unit usage (A) Illustrative diagram of billing definition table when pay-as-you-go billing with discount benefits is adopted, and (b) Graph showing the relationship between billing amount and unit usage (A) Illustrative diagram of billing definition table and (b) Graph showing relationship between billing amount and unit usage when step type pay-as-you-go billing is adopted (A) Illustration of charge definition table and (b) graph showing the relationship between charge amount and unit usage when cap-based charge is adopted (A) Illustrative diagram of billing definition table and (b) Graph showing relationship between billing amount and unit usage amount when minimum charge system billing is adopted (A) Illustrative diagram of billing definition table and (b) Graph showing relationship between billing amount and unit usage when double flat rate billing is adopted The figure which shows an example of the print log table in another system The figure which shows an example of the contract management table in another system A diagram showing an example of a price list in another system The figure which shows an example of the data structure of the utilization log table of 2nd Embodiment The figure which shows an example of the data structure of a charge definition table The figure which shows an example of the data structure of a charge definition table The figure which shows an example of the call log table in another system The figure which shows an example of the contract management table in another system A diagram showing an example of a price list in another system The figure which shows an example of the data structure of the charge definition table of 3rd Embodiment The figure which shows an example of the data structure of the charge definition table of 4th Embodiment The figure which shows an example of the data structure of the charge definition table of 5th Embodiment

Explanation of symbols

10 Invoice creation device 10d CPU
10g HDD
12 Usage Log Table 13 Charge Definition Table 14 Charge Definition Table 15 Billing Software 15a Charge Calculation Module

Claims (6)

Computer
Correspondence information that associates the combination with the unit price per unit amount for each combination of elements that are different from each other in the content of elements required to determine the unit price for a single use of a given service Unit price definition procedure stored in the storage device,
For each use of a predetermined service, the usage amount and the contents of some elements necessary for determining the unit price to be multiplied by the usage amount are associated with the usage log information in the storage device. Log accumulation procedure to be stored,
A unit price reading procedure for reading from the storage device correspondence information that matches the combination of the usage log information and the element content for each of the usage log information recorded in the storage device in the log accumulation procedure;
When the correspondence information is read in the unit price reading procedure, the quotient obtained by dividing the usage amount included in the usage log information by the unit amount is multiplied by the unit price in the correspondence information, and is indicated by the usage log information. A charge amount calculation procedure for calculating a charge amount for each use, and
When the charge amount is calculated in the charge amount calculation procedure, a charge amount storing procedure is executed in which the charge amount is stored in the storage device in association with the usage log information. The computer
In the unit price definition procedure, for each of all combinations in which the contents of elements necessary for determining a unit price for one use of a predetermined service are different from each other, the combination, the unit price per unit amount, and the unit price Correspondence information that associates the basic charge added to the charge calculated from the unit price is stored in the storage device,
In the accounting amount calculation procedure, the usage log information is obtained by multiplying the quotient obtained by dividing the usage amount included in the usage log information by the unit amount by the unit price in the correspondence information read in the unit price reading procedure. 2. The billing amount calculation method according to claim 1, further comprising: calculating a billing amount for one use indicated by the step, and further adding a basic billing amount in the corresponding information to the billing amount. The computer
In the unit price definition procedure, for each of all combinations in which the contents of elements necessary for determining a unit price for one use of a predetermined service are different from each other, the combination, the unit price per unit amount, and the unit price Storing correspondence information in association with the reduction amount subtracted from the usage amount divided by the unit amount before the unit price is multiplied;
In the accounting amount calculation procedure, the reduction amount in the correspondence information read in the unit price reading procedure is subtracted from the usage amount included in the usage log information, and the value obtained by the subtraction is divided by the unit amount. 2. The charge amount calculation method according to claim 1, wherein the charge amount for one use indicated by the use log information is calculated by multiplying the obtained quotient by the unit price in the correspondence information. The computer
In the unit price definition procedure, for each of all combinations in which the contents of elements necessary for determining a unit price for one use of a predetermined service are different from each other, the combination, the unit price per unit amount, and the unit price Storing correspondence information in association with the upper limit value of the charge amount calculated from the unit price in the storage device;
In the accounting amount calculation procedure, the usage log information is obtained by multiplying the quotient obtained by dividing the usage amount included in the usage log information by the unit amount by the unit price in the correspondence information read in the unit price reading procedure. A charge amount for one use indicated by is calculated, and if the charge amount exceeds an upper limit value in the corresponding information, the upper limit value is set as the charge amount. Item 2. A billing amount calculation method according to item 1. The computer
In the unit price definition procedure, for each of all combinations in which the contents of elements necessary for determining a unit price for one use of a predetermined service are different from each other, the combination, the unit price per unit amount, and the unit price Storing correspondence information in association with the lower limit value of the billing amount calculated from the unit price in the storage device;
In the accounting amount calculation procedure, the usage log information is obtained by multiplying the quotient obtained by dividing the usage amount included in the usage log information by the unit amount by the unit price in the correspondence information read in the unit price reading procedure. A charge amount for one use indicated by is calculated, and if the charge amount does not exceed a lower limit value in the corresponding information, the lower limit value is set as the charge amount. Item 2. A billing amount calculation method according to item 1. Computer
Correspondence information that associates the combination with the unit price per unit amount for each combination of elements that are different from each other in the content of elements required to determine the unit price for a single use of a given service Unit price definition means for storing in a storage device;
For each use of a predetermined service, the usage amount and the contents of some elements necessary for determining the unit price to be multiplied by the usage amount are associated with the usage log information in the storage device. Log storage means to store,
Unit price reading means for reading, from the storage device, correspondence information in which the combination of the usage log information and the content of the elements matches for each of the usage log information recorded in the storage device by the log storage means,
When the unit price reading means reads the correspondence information, the quotient obtained by dividing the usage amount included in the usage log information by the unit amount is multiplied by the unit price in the correspondence information, and is indicated by the usage log information. A billing amount calculating means for calculating a billing amount for each use, and
A billing amount calculation program that, when the billing amount calculation means calculates a billing amount, causes the billing amount to function as billing amount storage means that stores the billing amount in association with usage log information.