JP2018156406A - Sales data creating apparatus, sales data creating method, and program for creating sales data - Google Patents

Abstract

PROBLEM TO BE SOLVED: To reduce a load of data creation.SOLUTION: A sales data creating apparatus according to the present embodiment has a calculation unit for calculating a work unit price indicating an amount per work by using the number of works per month and the fixed charge amount per month set for each of months from a start month to a last month of a contract term, and a data creating unit for creating work program data including a plurality of first records which associates work identification information for identifying work with a work unit price and an allocation month, and sales data including a plurality of second records which associate sales identification information for identifying sales corresponding to work with a charge amount and a charge month. The sales data includes the second record including, as a charge amount, a first adjustment amount calculated so that the sum of a plurality of charge amounts per charge month should not exceed the fixed charge amount and the second record including, as a charge amount, a second adjustment amount obtained by subtracting the first adjustment amount from the work unit price.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a sales data creation device, a sales data creation method, and a sales data creation program.

  Patent Document 1 proposes a work management system that inputs contract data into a computer, divides the contract data into work units, and manages each divided work unit to prevent omission of reports and work omissions. ing. For example, Patent Document 1 describes a work management system that creates work slips to which work amounts are individually assigned and calculates sales in units of work slips.

JP 2001-344332 A

  However, Patent Document 1 does not describe, for example, contract work management in which the monthly billing amount is a fixed amount and the number of operations per month is different. In such a contract, the billing amount calculated from the actual number of operations and the work amount may be less than the fixed amount or may exceed the fixed amount, so that the billing amount needs to be adjusted. Conventionally, in such a case, it has been necessary to manually input data such as a billing amount, and thus there has been a problem that the load becomes high and an input error may occur.

  The present invention has been made in view of the above, and an object thereof is to provide a sales data creation device, a sales data creation method, and a sales data creation program that can reduce the data creation load.

  In order to solve the above-described problems and achieve the object, the sales data creation device according to the present invention includes the number of operations per month set for each month from the start month to the end month of the contract period. The calculation unit for calculating the work unit price indicating the amount of work per work using the fixed charge amount per month, the work identification information for identifying the work, the work unit price, and the recording month Data creation for creating work schedule data including a plurality of first records, and sales data including a plurality of second records in which sales identification information for identifying sales corresponding to the work, a billing amount, and a billing month are associated with each other. And the sales data includes, as the bill amount, a first adjustment amount calculated so that a sum of the plurality of bill amounts for each billing month does not exceed the bill fixed amount. When Including a second record containing second adjustment amount obtained by subtracting the first adjustment amount from the working unit price as the amount billed.

  Further, in the sales data creation device according to the present invention, the data creation unit includes the sales identification information corresponding to the first adjustment amount and the sales identification information corresponding to the second adjustment amount. The work schedule data and the sales data are created so as to correspond to the work identification information.

  In addition, the sales data creation device according to the present invention is configured to perform a billing process for each billing month based on the work schedule data and a billing processing unit that executes billing processing for each billing month based on the sales data. A journal processing unit to be executed.

  In addition, the sales data creation method according to the present invention uses the number of operations per month set for each month from the start month to the end month of the contract period, and a fixed charge amount per month. A calculation step for calculating a work unit price indicating the amount of money per operation, work schedule data including a plurality of first records in which the work identification information for identifying the work, the work unit price and the recording month are associated, and A data creation step of creating sales data including a plurality of second records in which sales identification information for identifying sales corresponding to the work, a billing amount, and a billing month are associated with each other. The second record including the first adjustment amount calculated so that the sum of the plurality of the billing amounts for each billing month does not exceed the billing fixed amount as the billing amount, and the first unit cost based on the work unit price. The second adjustment amount obtained by subtracting the integer amount; and a second record containing as the amount billed.

  In addition, the sales data creation program according to the present invention allows the computer to set the number of operations per month set for each month from the start month to the end month of the contract period, and the fixed amount charged per month. , And a work unit including a plurality of first records in which a work unit price indicating the amount of money per work is calculated, work identification information for identifying the work, and the work unit price and the recording month are associated with each other. Data and a data creation unit that creates sales data including a plurality of second records in which sales identification information for identifying sales corresponding to the work, a billing amount, and a billing month are associated with each other. The data includes the second record including the first adjustment amount calculated so that the sum of the plurality of the billing amounts for each billing month does not exceed the billing fixed amount, and the work The second adjustment amount obtained by subtracting the first adjustment amount from the bid including, a second record containing as the amount billed.

  According to the present invention, it is possible to reduce the load of data creation.

FIG. 1 is a block diagram showing an example of the configuration of the sales data creation device. FIG. 2 is a diagram illustrating an example of the data structure of sales data and work schedule data. FIG. 3 is a diagram illustrating an example of the data structure of sales data and work schedule data. FIG. 4 is a diagram illustrating an example of a contract input screen. FIG. 5 is a diagram illustrating an example of the sales detail screen. FIG. 6 is a diagram illustrating an example of a development assistance screen. FIG. 7 is a diagram illustrating an example of input data. FIG. 8 is a diagram illustrating an example of the cost details screen. FIG. 9 is a diagram illustrating an example of the cost detail screen. FIG. 10 is a flowchart illustrating an example of the flow of processing by the sales data creation device.

  Hereinafter, embodiments of a sales data creation device, a sales data creation method, and a sales data creation program according to the present invention will be described in detail with reference to the drawings. In addition, this invention is not limited by this embodiment.

  For example, in a regular inspection work for real estate, there may be a contract in which the monthly billing amount is a fixed amount (billing fixed amount) and the number of monthly work is different. In such a case, for example, sales are recorded on a work performance basis, while the monthly billing amount is determined by negotiation with the customer independently of the number of operations. Therefore, there is a case where the amount corresponding to the work performance does not become the billed amount as it is. For this reason, the function which divides | segments the money according to a work performance based on the sum total of the amount of money charged in a contract period, and the total of the frequency | count of work is needed. As described above, in the conventional method, since data such as the divided billing amount is manually input, there is a problem that the load increases.

  Therefore, in the present embodiment, the sales amount per operation is calculated from the input number of operations and the amount charged every month, and the work schedule data and the sales data appropriated to the monthly amount charged are generated. Thereby, it is possible to reduce the load of data creation. In addition, when a work result is input based on work schedule data, sales recording processing (journal processing) and billing processing can be executed in conjunction with each other. Hereinafter, a specific configuration and operation will be described.

  The configuration of the sales data creation device 10 according to the present embodiment will be described with reference to FIG. FIG. 1 is a block diagram illustrating an example of the configuration of the sales data creation device 10.

  The sales data creation device 10 is a commercially available desktop personal computer. The sales data creation device 10 is not limited to a stationary information processing device such as a desktop personal computer, but is a portable personal computer such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer. It may be a type information processing apparatus.

  As shown in FIG. 1, the sales data creation device 10 includes a control unit 12, a communication interface unit 13, a storage unit 11, and an input / output interface unit 14. Each unit included in the sales data creation device 10 is communicably connected via an arbitrary communication path.

  The communication interface unit 13 connects the sales data creation device 10 to the network CN via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 13 has a function of communicating data with other devices via a communication line. Here, the network CN has a function of connecting the sales data creation device 10 and the server SV so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network). Note that data stored in the storage unit 11 to be described later may be stored in the server SV.

  An input device ID and an output device OD are connected to the input / output interface unit 14. In addition to a monitor (including a home television), a speaker or a printer can be used as the output device OD. In addition to a keyboard, mouse, and microphone, a monitor that realizes a pointing device function in cooperation with the mouse can be used as the input device ID.

  The storage unit 11 stores various databases, tables, files, and the like. The storage unit 11 stores a computer program for giving various instructions to a CPU (Central Processing Unit) in cooperation with an OS (Operating System). As the storage unit 11, for example, a memory device such as a RAM (Random Access Memory) and a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, and the like can be used.

  For example, as shown in FIG. 1, the storage unit 11 stores sales data 21, work schedule data 22, and journal data 23.

  The sales data 21 is data indicating sales of contracted work. For example, the sales data 21 indicates the sales schedule for each month within the contract period for the contracted work. The work schedule data 22 is data indicating a contracted work schedule. For example, the work schedule data 22 indicates the work schedule of each month within the contract period for the contracted work.

  2 and 3 are diagrams showing examples of data structures of sales data and work schedule data. For convenience of explanation, each piece of data (sales data 201, work schedule data 202) is divided into two diagrams of FIG. 2 and FIG. 3, but the storage unit 11 does not have to store each piece of data separately.

  As shown in FIG. 2 and FIG. 3, the sales data 201 includes a sales serial number, a work month, a billing month, a main body amount, a consumption tax, a tax-included amount, a recording month, a work scheduled serial number, including. The work schedule data 202 includes a work schedule serial number, a work month, a payment month, a main body amount, a consumption tax, a tax-included amount, and a recording month.

  The work schedule sequence number is identification information (work identification information) for identifying a record (first record) indicating each detail of work. The sales serial number is identification information (sales identification information) for identifying a record (second record) indicating each item of sales. Each record of the sales data 201 includes a work schedule serial number of the corresponding work schedule data 202. Thereby, the record of the work schedule data 202 corresponding to each record of the sales data 201 can be specified.

  The sales data 201 is not limited to the data structure shown in FIGS. 2 and 3, and may be any data structure that can specify at least the billing amount and the billing month. The work schedule data 202 is not limited to the data structure shown in FIGS. 2 and 3, and may be any data structure that can specify at least a work unit price and a recording month. The work unit price indicates the amount of money per work.

  Sales data 201 and work schedule data 202 are created by a data creation unit 32 (described later) and stored in the storage unit 11. Details of data creation processing for creating sales data 201 and work schedule data 202 will be described later.

  The journal data 23 is data created as a result of the journal processing. The journal data 23 includes, for example, an account item code, a debit amount, a credit amount, and a description. The journal data 23 is generated by a journal processing unit 34 (described later) and stored in the storage unit 11.

  The control unit 12 is a CPU or the like that comprehensively controls the sales data creation device 10. The control unit 12 includes an internal memory for storing a control program such as an OS and various processing procedures and necessary data, and various information processing based on the stored programs. Execute.

  As shown in FIG. 1, the control unit 12 includes a calculation unit 31, a data creation unit 32, a billing processing unit 33, and a journal processing unit 34.

The calculation unit 31 calculates a work unit price per work. For example, the calculation unit 31 calculates the work unit price using the number of operations per month and the fixed charge amount per month set for each month from the start month to the end month of the contract period. . The work unit price is calculated by the following equation (1), for example.
Unit price for work = fixed amount for billing x number of months / (total number of operations) (1)

  The data creation unit 32 creates work schedule data and sales data using the calculated work unit price and the like. In this embodiment, the data creation unit 32 creates sales data so as to divide and distribute the work unit price so that the sum of a plurality of billing amounts for each billing month does not exceed the billing fixed amount. For example, the data creation unit 32 sets the first from the record including the adjustment amount (first adjustment amount) calculated so that the sum of the plurality of invoice amounts for each invoice month does not exceed the fixed charge amount, and the work unit price. Sales data including an adjustment amount obtained by subtracting the adjustment amount (second adjustment amount) as a billing amount is created.

  In addition, the data creation unit 32 creates sales data and work schedule data so that each work and sales are associated with each other by a work schedule serial number. For example, when the work unit price of one work is divided into a plurality of sales (adjustment amounts) as described above, the data creation unit 32 assigns a plurality of sales sequence numbers corresponding to the plurality of adjustment amounts to one work scheduled sequence number. Work schedule data and sales data are created so as to correspond to.

  Here, a specific example of the adjustment amount calculation method will be described. In principle, the data creation unit 32 sets the unit price calculated by the calculation unit 31 as the billing amount (main body amount) of each sales. When a fraction (remainder) is generated according to equation (1), for example, the data creation unit 32 adds the fraction to the billed amount of a specific record (for example, the first record).

For each month in the contract period, the data creation unit 32 adds the work unit price to the sum of the billed amount for each month. If the sum total is less than or equal to the fixed billing amount for the same billing month, the work unit price is used as the billing amount as described above. When the added sum exceeds the fixed billing amount for the same billing month, the data creation unit 32 uses the adjustment amount A1 calculated by the following equation (2) as the billing amount.
Adjustment amount A1 = work unit price− (total added−invoice fixed amount for the same billing month) (2)

In this case, the data creation unit 32 uses the adjustment amount A2 calculated by the following equation (3) as the charge amount of the first record of the next billing month, which is the amount corresponding to the excess of the billing month. To do.
Adjustment amount A2 = work unit price−adjustment amount A1 (3)

Hereinafter, an example of FIG. 2 will be described. 2 and 3, the contract period is 12 months (April 2013 to March 2014), the monthly fixed charge is 93,000 yen, and the total number of work for each month is 52 times. It is an example in the case of. The calculation part 31 calculates a work unit price as follows according to Formula (1).
Work unit price = 93000 yen x 12/52 = 21461 yen Remaining 28 yen

  The data creation unit 32 receives the sales data corresponding to the first work in April 2013 (scheduled work sequence number = 1) and the billing amount (main body amount) of the work scheduled data, which is an amount obtained by adding a fraction to 21489 yen ( = 21461 yen + 28 yen). The data creation unit 32 adds the work unit price to the billing amount of the sales data and work schedule data corresponding to the subsequent work. Until the fourth time (scheduled work sequence number = 4), the total added does not exceed the fixed charge amount, so the work unit price is set as the charge amount.

In the fifth work (scheduled work sequence number = 5), the sum (107333 yen) by addition exceeds the fixed charge amount. Therefore, the data creation unit 32 calculates the adjustment amount A1 by the above equation (2) and sets it as the billing amount.
Adjustment A1 = 21461-(107333-93000) = 7128 (yen)

The data creation unit 32 sets the adjustment amount A2 calculated by the above equation (3) as the amount charged for the first work in the next billing month (May 2013).
Adjustment amount A2 = 21461-7128 = 14333 (yen)

  In this way, the sales data and work schedule data shown in FIGS. 2 and 3 are calculated. For example, out of the billing amount with the billing month of April 2013, the amount of 7128 yen (adjustment amount A1) corresponds to the work with the work month of May 2013. Therefore, the amount charged for this amount is a down payment. The invoiced amount received as a down payment is transferred as sales when the work is actually performed in May 2013 and the results are registered, for example.

  Returning to FIG. 1, the billing processing unit 33 executes billing processing for each billing month based on the sales data. For example, the billing processing unit 33 creates billing data for the billing month from the sales data, and issues a bill based on the billing data.

  The journal processing unit 34 executes the journal processing for each recording month based on the work schedule data. For example, the journal processing unit 34 counts sales for the work performed in units of the recording month, and creates journal data.

  Next, various processes by the sales data creation device 10 of the present embodiment configured as described above will be described. 4 to 9 are diagrams illustrating examples of screens used in each process. FIG. 4 is a diagram illustrating an example of a contract input screen for inputting a contract.

  The contract input screen 400 in FIG. 4 is an example of a screen for inputting basic contract information and sales details information. The contract input screen 400 includes a sales detail button 401 and a cost details button 402. When the sales details button 401 is pressed, a sales details screen is displayed. When the cost details button 402 is pressed, a cost details screen is displayed. The sales details screen is a screen for inputting and displaying details (details) of sales data. The cost detail screen is a screen for inputting and displaying work schedule data. 4 to 9 show examples of screens in the case where the sales amount of work is managed as the cost, the data management method is not limited to this.

  FIG. 5 is a diagram illustrating an example of the sales detail screen. As shown in FIG. 5, the sales detail screen 500 displays data corresponding to the sales data shown in FIGS. 2 and 3, for example. The expansion assistance button 501 is a button for displaying an expansion assistance screen that is used to input the number of operations for each month and the amount charged.

  FIG. 6 is a diagram illustrating an example of a development assistance screen. As shown in FIG. 6, the expansion assistance screen 600 includes an input field 601, an input field 602, and an update button 611. The input field 601 is an area for inputting the number of operations for each month. The input field 602 is an area for inputting the billing amount for each month. Data on contracts in which the monthly billing amount is a fixed amount (billing fixed amount) and the number of operations per month is different can be entered in the input fields 601 and 602.

  FIG. 7 is a diagram illustrating an example of input data. FIG. 7 is an example of data in which the monthly charge fixed amount is 93000 yen and the number of operations per month is a different value (4 or 5). When the data in FIG. 7 is input, sales data 201 and work schedule data 202 as shown in FIGS. 2 and 3 are created.

  For example, when the update button 611 is pressed, a calculation process by the calculation unit 31 and a data creation process by the data creation unit 32 are executed. Then, the expansion assistance screen 600 is closed, and the sales data created by the data creation process is reflected on the sales details screen. The sales detail screen 500 in FIG. 5 corresponds to a screen in which a part of the sales data 201 shown in FIGS. 2 and 3 created in this way is reflected.

  Conventionally, for example, it has been necessary to manually input each sales data as shown in the sales details information on the sales details screen 500 as shown in FIG. On the other hand, according to the present embodiment, sales data can be created simply by inputting the number of operations and the billing amount for each month on the screen as shown in FIG.

  FIG. 8 is a diagram illustrating an example of the cost details screen. As shown in FIG. 8, the cost details screen 800 includes a cost detail button 801. When the cost detail button 801 is pressed, a cost detail screen for inputting and displaying details (details) of work schedule data is displayed.

  FIG. 9 is a diagram illustrating an example of the cost detail screen. As shown in FIG. 9, the cost detail screen 900 displays data corresponding to the work schedule data shown in FIGS. 2 and 3, for example. A development assistance button 901 is a button for displaying a development assistance screen. When the development assistance button 901 is pressed, for example, a development assistance screen 600 of FIG. 6 is displayed.

  Next, the flow of processing by the sales data creation device 10 of the present embodiment configured as described above will be described. FIG. 10 is a flowchart showing an example of the flow of processing by the sales data creation device 10 of this embodiment.

  First, the control unit 12 accepts input of the number of operations for each month and the billing amount (step S101). For example, the control unit 12 receives the number of operations (input field 601) and the billing amount (input field 602) for each month, which are input using the development assistance screen 600 of FIG.

  Next, the calculation unit 31 calculates the work unit price of the work (step S102). For example, the calculation unit 31 calculates the work unit price by using the input number of operations and the amount charged and the above equation (1).

  Next, the data creating unit 32 creates work schedule data and sales data by the above-described procedure using the calculated work unit price and the like (step S103). The data creation unit 32 stores the created sales data and work schedule data in the storage unit 11 (step S104).

  Thereafter, billing processing and journalizing processing are executed based on the generated sales data and work schedule data.

  For example, the billing processing unit 33 executes billing processing for the sales in the billing month to be billed based on the sales data at the designated billing timing (step S105). Further, for example, the journal processing unit 34 executes the journal processing for the work of the recording month to be recorded based on the work schedule data when the timing of sales recording is reached, such as when the work results are input ( Step S106).

  The billing process (step S105) and the journalizing process (step S106) need not be executed in the order shown in FIG. 10, and can be executed independently when the timing of each process comes.

  As described above, the sales data creation device 10 according to the present embodiment generates the work schedule data and the sales data in which the work unit price is distributed so as not to exceed the fixed charge amount of each month from the number of times of work and the charge amount of each month. To do. Thereby, it is possible to reduce the load of data creation.

  In addition to the above-described embodiments, the present invention may be implemented in various different embodiments within the scope of the technical idea described in the claims.

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

  In addition, the processing procedures, control procedures, specific names, information including parameters such as registration data and search conditions for each processing, screen examples, and database configurations shown in the present specification and drawings, unless otherwise specified. Can be changed arbitrarily.

  Further, regarding the sales data creation device 10, the illustrated components are functionally conceptual and do not necessarily need to be physically configured as illustrated.

  For example, all or some of the processing functions provided in the sales data creation device 10, particularly the processing functions performed by the control unit 12, are realized by the CPU and a program that is interpreted and executed by the CPU. Alternatively, it may be realized as hardware by wired logic. The program is recorded on a non-temporary computer-readable recording medium including programmed instructions for causing the information processing apparatus to execute the processing described in this embodiment, and sales data is created as necessary. It is mechanically read by the device 10. In other words, in a storage unit such as a ROM or a HDD (Hard Disk Drive), a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded. This computer program is executed by being loaded into the RAM, and constitutes a control unit in cooperation with the CPU.

  The computer program may be stored in an application program server connected to the sales data creation device 10 via an arbitrary network, and may be downloaded in whole or in part as necessary. It is.

  In addition, a program for executing the processing described in this embodiment may be stored in a non-temporary computer-readable recording medium, or may be configured as a program product. Here, the “recording medium” refers to a memory card, USB (Universal Serial Bus) memory, SD (Secure Digital) card, flexible disk, magneto-optical disk, ROM, EPROM (Erasable Programmable Read Only Memory), EEPROM (registration). Trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROM (Compact Disk Read Only Memory), MO (Magneto-Optical disk), DVD (Digital Digital, Trademark) Any “portable physical media It is intended to include. Therefore, a recording medium storing a program for executing the processing or processing method described in this specification also constitutes the present invention.

  The “program” is a data processing method described in an arbitrary language or description method, and may be in any form such as source code or binary code. Note that the “program” is not necessarily limited to a single configuration, and functions are achieved in cooperation with a separate configuration such as a plurality of modules and libraries or a separate program represented by the OS. Including things. In addition, a well-known structure and procedure can be used about the specific structure and reading procedure for reading a recording medium in each apparatus shown to embodiment, the installation procedure after reading, etc.

  Various databases and the like stored in the storage unit 11 are storage means such as a memory device such as RAM and ROM, a fixed disk device such as a hard disk, a flexible disk, and an optical disk. Programs, tables, databases, web page files, and the like.

  The sales data creation device 10 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 sales data creation device 10 may be realized by installing software (including a program or data) that realizes the processing described in the present embodiment in the device.

  Furthermore, the specific form of distribution / integration of the devices is not limited to that shown in the figure, and all or a part of them may be functionally or physically in arbitrary units according to various additions or according to functional loads. It can be configured to be distributed and integrated. That is, the above-described embodiments may be arbitrarily combined and may be selectively implemented.

  The present invention is useful in various industries, for example, in industries where billing cycles and sales cycles are different.

DESCRIPTION OF SYMBOLS 10 Sales data creation apparatus 11 Storage part 12 Control part 13 Communication interface part 14 Input / output interface part 21 Sales data 22 Scheduled work data 23 Journal data 31 Calculation part 32 Data creation part 33 Billing process part 34 Journal processing part CN Network ID input device OD output device SV server

Claims (5)

Unit price of work per operation using the number of operations per month and the fixed amount charged per month, set for each month from the start month to the end month of the contract period A calculation unit for calculating
Work schedule data including a plurality of first records in which work identification information for identifying work, the work unit price and recording month are associated with each other, and sales identification information for identifying sales corresponding to the work, billing amount and billing month And a data creation unit for creating sales data including a plurality of second records in association with
The sales data includes the second record including, as the billing amount, a first adjustment amount calculated so that the sum of the plurality of billing amounts for each billing month does not exceed the billing fixed amount, and the work unit price. A sales data creation device including: the second record including a second adjustment amount obtained by subtracting the first adjustment amount as the billing amount. The data creation unit is configured to associate the sales identification information corresponding to the first adjustment amount and the sales identification information corresponding to the second adjustment amount with a single piece of the operation identification information. Create data and sales data,
The sales data creation device according to claim 1. A billing processing unit that executes billing processing for each billing month based on the sales data;
A journal processing unit that executes journal processing for each recording month based on the work schedule data; and
The sales data creation device according to claim 1. Unit price of work per operation using the number of operations per month and the fixed amount charged per month, set for each month from the start month to the end month of the contract period A calculating step for calculating
Work schedule data including a plurality of first records in which work identification information for identifying work, the work unit price and recording month are associated with each other, and sales identification information for identifying sales corresponding to the work, billing amount and billing month And a data creation step for creating sales data including a plurality of second records in association with
The sales data includes the second record including, as the billing amount, a first adjustment amount calculated so that the sum of the plurality of billing amounts for each billing month does not exceed the billing fixed amount, and the work unit price. A sales data creation method including: the second record including a second adjustment amount obtained by subtracting the first adjustment amount as the billing amount. Computer
Unit price of work per operation using the number of operations per month and the fixed amount charged per month, set for each month from the start month to the end month of the contract period A calculation unit for calculating
Work schedule data including a plurality of first records in which work identification information for identifying work, the work unit price and recording month are associated with each other, and sales identification information for identifying sales corresponding to the work, billing amount and billing month And function as a data creation unit that creates sales data including a plurality of second records in association with
The sales data includes the second record including, as the billing amount, a first adjustment amount calculated so that the sum of the plurality of billing amounts for each billing month does not exceed the billing fixed amount, and the work unit price. A sales data creation program including: the second record including a second adjustment amount obtained by subtracting the first adjustment amount as the billing amount.