JP7450501B2 - Information processing device and program - Google Patents

Description

Embodiments of the present invention relate to an information processing device and a program.

BACKGROUND ART Tenant management systems have been known that calculate expenses such as rent for each tenant in complex commercial facilities such as shopping centers. For example, a system has been proposed that selects a rental fee from a minimum business fee and a business fee corresponding to product sales (see Patent Document 1).

Incidentally, in a commercial complex, if a tenant is unable to operate due to a disaster or the like, the tenant may be charged rent calculated on a daily basis. However, with the technology that calculates rent according to product sales, it is not possible to calculate a fixed amount of rent on a daily basis.

Generally, when calculating a fixed amount of expenses on a daily basis, store holidays are set for each tenant on a daily basis, and expenses are calculated using the number of days excluding store holidays as business days. It takes a lot of effort to set up. Therefore, there is a strong need for technology that can easily calculate daily expenses.

The problem to be solved by the present invention is to provide an information processing device and a program that can easily calculate daily expenses.

The information processing device of the embodiment includes a receiving unit that receives settlement data including information indicating one day's sales of the store from a terminal device installed in a store, and a receiving unit that receives the settlement data from a terminal device installed in the store. a reception unit that accepts input of the payment data when the data cannot be received; a management unit that manages the payment data of the store received by the reception unit on a daily basis; and a management unit that manages the payment data of the store received by the reception unit on a daily basis; a first calculation unit that calculates the number of days on which the reception unit receives the payment data as a first business day; and the payment data received by the reception unit and the payment received by the reception unit within the calculation period. A second calculation unit that calculates the number of days in which settlement data other than settlement data with sales of zero is received or accepted among the data as a second number of business days, and one of the first number of business days and the second number of business days. , a third calculation unit that calculates billed expenses by multiplying the number of business days by expenses per day, as the number of business days within the calculation period.

FIG. 1 is a diagram schematically showing the overall configuration of a tenant management system according to an embodiment. FIG. 2 is a block diagram showing an example of the configuration of the electrical system of the POS terminal shown in FIG. FIG. 3 is a diagram illustrating an example of the data structure of the aggregated data table according to the embodiment. FIG. 4 is a block diagram showing an example of the functional configuration of the control section of the POS terminal shown in FIG. 1. As shown in FIG. FIG. 5 is a diagram showing an example of the configuration of the electrical system of the tenant management device shown in FIG. 1. FIG. 6 is a diagram illustrating an example of the data structure of the reception management table according to the embodiment. FIG. 7 is a diagram showing an example of the data structure of the sales management table according to the embodiment. FIG. 8 is a diagram showing an example of the data structure of the rent management table according to the embodiment. FIG. 9 is a block diagram showing an example of the functional configuration of the control unit of the tenant management device shown in FIG. 1. FIG. 10 is a flowchart illustrating an example of a rent calculation process executed by the tenant management device according to the embodiment.

DESCRIPTION OF EMBODIMENTS Hereinafter, embodiments of an information processing device and a program according to the present invention will be described in detail with reference to the accompanying drawings. Note that in the following embodiment, an example in which the information processing device and program of the present invention are applied to a complex commercial facility such as a shopping center will be described, but the present invention is not limited to this embodiment.

FIG. 1 is a diagram schematically showing the overall configuration of a tenant management system 1 according to this embodiment. The tenant management system 1 includes a plurality of POS (Point Of Sale) terminals 10 and a tenant management device 20.

Each POS terminal 10 and tenant management device 20 are connected to be able to communicate with each other via a network N such as a LAN (Local Area Network). Note that the POS terminal 10 is an example of a "terminal device," and the tenant management device 20 is an example of an "information processing device."

The POS terminal 10 is a POS terminal installed at each tenant (store) in a commercial complex. Each of the POS terminals 10 generates settlement data including information indicating one day's worth of sales at its own tenant based on the sales data of each product registered for sale, and transmits it to the tenant management device 20.

The tenant management device 20 manages the total sales and rent of each tenant. The tenant management device 20 is installed, for example, at the headquarters (developer) of a commercial complex.

Hereinafter, a configuration example of each device configuring the tenant management system 1 will be described.

First, the configuration of the POS terminal 10 will be explained. FIG. 2 is a block diagram showing an example of the configuration of the electrical system of the POS terminal 10. As shown in FIG. The POS terminal 10 includes a control unit 11 having a computer configuration including a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), and the like.

The control unit 11 is connected to a communication interface (I/F) 13 connectable to a network N and an I/O device control unit 14 via a bus 12. Further, the control section 11 is connected to an input section 15, a display section 16, a storage section 17, etc. via a bus 12 and an I/O device control section 14.

The input unit 15 includes input devices such as a keyboard and a pointing device. The input unit 15 notifies the control unit 11 of a signal corresponding to the operation content received via the input device. The display unit 16 includes a display device such as a liquid crystal display. The display unit 16 displays various information under the control of the control unit 11.

The storage unit 17 includes a storage device such as an HDD (Hard Disk Drive) or an SSD (Solid State Drive). The storage unit 17 stores data including various programs executed by the CPU of the control unit 11 and setting information, as well as a tenant code for identifying the tenant in which the device is installed and information indicating the tenant's daily sales. The totalized data table 171 and the like are stored.

FIG. 3 is a diagram showing an example of the data structure of the total data table 171. The aggregated data table 171 is a table that stores data that is aggregated on a daily basis (each business day), including information indicating the tenant's sales for one day.

Specifically, the aggregated data table 171 is a table that stores aggregated data for each business day, such as total sales, credit, credit, electronic money, consumption tax, net sales, cash balance, number of customers, and the like. In addition to these, aggregated data of debits, gift certificates, coupons, discount tickets, etc. may be added.

Next, the functional configuration of the control section 11 of the POS terminal 10 will be explained. FIG. 4 is a block diagram showing an example of the functional configuration of the control unit 11 of the POS terminal 10. As shown in FIG. The control unit 11 includes a generation unit 111 and a communication control unit 112 as functional units.

The generation unit 111 generates daily settlement data including information indicating one day's worth of sales of its own tenant. Specifically, the generation unit 111 refers to the aggregated data table 171 and attaches the tenant code of the tenant in which the own device is installed to aggregated data that includes information indicating sales on the business day targeted for generation. to generate payment data.

The timing at which the generation unit 111 generates the payment data is arbitrarily determined. For example, the generation unit 111 generates the previous day's settlement data at midnight every day.

The communication control unit 112 controls communication with the tenant management device 20. For example, the communication control unit 112 transmits the payment data generated by the generation unit 111 to the tenant management device 20. It is assumed that the communication control unit 112 transmits the settlement data to the tenant management device 20 once a day, and the timing of transmission is determined arbitrarily. For example, the communication control unit 112 automatically transmits the previous day's settlement data generated by the generation unit 111 at midnight every day to the tenant management device 20.

Note that the timing of generating and transmitting the payment data is not limited to the above. For example, when an operation is performed to update the processing date (business day) on the POS terminal 10, the generation unit 111 generates payment data for the previous business day, and the communication control unit 112 sends the payment data to the tenant management device 20. You may.

By the way, if the power of the POS terminal 10 is not turned on, the payment data is not transmitted. In other words, if the power of the POS terminal 10 is not turned on, it is considered that the tenant is not conducting business. Therefore, on days when payment data is not sent to the tenant management device 20, it can be inferred that the tenant is not open for business.

Next, the configuration of the tenant management device 20 will be explained. FIG. 5 is a block diagram showing an example of the configuration of the electrical system of the tenant management device 20. The tenant management device 20 includes a control unit 21 having a computer configuration including a CPU, ROM, RAM, and the like.

The control unit 21 is connected to a communication interface 23 connectable to the network N and an I/O device control unit 24 via a bus 22. Further, the control section 21 is connected to an input section 25, a display section 26, a storage section 27, etc. via a bus 22 and an I/O device control section 24.

The input unit 25 includes input devices such as a keyboard and a pointing device. The input unit 25 notifies the control unit 21 of a signal corresponding to the operation content received via the input device. The display unit 26 includes a display device such as a liquid crystal display. The display unit 26 displays various information under the control of the control unit 21.

The storage unit 27 includes a storage device such as an HDD or an SSD. The storage unit 27 stores various programs executed by the CPU of the control unit 21, setting information, and the like. The setting information includes, for example, information on setting whether or not to prorate the rent. Note that the setting of whether or not to prorate the rent can be made for each tenant.

The storage unit 27 also stores a reception management table 271, a sales management table 272, and a rent management table 273. Note that the storage unit 27 can be said to be an example of a “management unit” since it has a function of managing payment data on a daily basis.

FIG. 6 is a diagram showing an example of the data structure of the reception management table 271. The reception management table 271 is a data table for storing and managing the number of times payment data has been received from the POS terminal 10 installed in each tenant during the target period.

As shown in FIG. 6, the reception management table 271 associates the target period, the tenant code of each tenant, the tenant name, and the number of receptions.

The number of receptions indicates the number of times payment data has been received from the POS terminal 10 installed in the tenant within a predetermined period. In the example of FIG. 6, for example, the tenant management device 20 was installed in tenant A identified by tenant code 1001 in December 20XX (from December 1st to December 31st if December has ended). This indicates that payment data has been received 10 times from the POS terminal 10.

In this embodiment, the payment data is not sent more than once a day, so the number of times payment data is received within a predetermined period matches the number of days on which payment data is received within the predetermined period. .

The reception management table 271 may store, for each tenant, the number of days (regardless of the number of times) that payment data was received from the POS terminal 10 during the target period. Further, the reception management table 271 may be any table that stores and manages the number of times (number of days) payment data has been received, and the format is not limited to a table.

FIG. 7 is a diagram showing an example of the data structure of the sales management table 272. The sales management table 272 is a data table for storing and managing settlement data for each tenant on a daily basis. Note that the sales management table 272 may be one that stores and manages settlement data for each tenant on a daily basis, and the format is not limited to a table.

Specifically, the sales management table 272 stores the tenant code, tenant name, and settlement data for each business day in association with each other for each tenant in the commercial complex. In the example of FIG. 7, the settlement data includes total sales, credit, credit, electronic money, consumption tax, net sales, cash balance, and number of customers.

The payment data included in the sales management table 272 is, in principle, payment data received from the POS terminal 10 installed in the tenant, but depending on the specifications of the POS terminal 10, the tenant management device 20 may not be able to receive the payment data. There is. In this case, the operator (administrator, etc.) of the tenant management device 20 will input the settlement data in the sales management table 272 via an input device.

Note that in the sales management table 272, 0 is input for all data at the stage of generation. Then, when the tenant management device 20 receives the payment data from the POS terminal 10, each data included in the payment data is overwritten. Therefore, it can be inferred that the tenant is not conducting business on a day that has already passed and 0 is entered in all data in the sales management table 272.

FIG. 8 is a diagram showing an example of the data structure of the rent management table 273. The rent management table 273 is a data table for storing and managing the rent of each tenant. Rent is an example of an "expense." Note that the rent management table 273 may be any table that stores and manages the rent of each tenant, and its format is not limited to a table.

Specifically, the rent management table 273 stores the tenant code, tenant name, daily rent, and fixed rent in association with each other for each tenant in the commercial complex.

Fixed rent is the amount charged to a tenant as rent when the rent is not prorated. In other words, in principle, the fixed rent in the rent management table 273 will be charged to the tenant as rent. In this example, the fixed rent is set as the rent per month according to the general billing period, but if the billing period is set to one week or two weeks, the fixed rent is set as the rent per week. It may be the rent or the rent per two weeks.

The daily rent is the amount used to calculate the rent when the rent is calculated on a daily basis. Rent may be prorated on a daily basis when many tenants are unable to operate due to a major disaster or when tenants move out in the middle of the month. The tenant management device 20 of this embodiment prorates the rent on a daily basis when it is set to prorate the rent on a daily basis.

In the example of FIG. 8, the daily rent is the amount obtained by dividing the fixed rent, which is the monthly rent, by 30, where January is the 30th day, but the daily rent is not limited to this. For example, the daily rent may be determined by dividing the fixed rent by the tenant's average number of business days.

Next, the functional configuration of the control unit 21 of the tenant management device 20 will be explained. FIG. 9 is a block diagram showing an example of the functional configuration of the control unit 21 of the tenant management device 20. The control unit 21 includes a communication control unit 211, a reception unit 212, a first calculation unit 213, a second calculation unit 214, a determination unit 215, and a third calculation unit 216 as functional units.

The communication control unit 211 controls communication with the POS terminal 10. For example, the communication control unit 211 receives payment data from the POS terminal 10 installed in the tenant. When the communication control unit 211 receives the payment data, 1 is added to the number of receptions in the reception management table 271. Further, the settlement data received by the communication control unit 211 is stored in the sales management table 272.

Specifically, for example, consider a case where the communication control unit 211 receives payment data for December 31, 20XX from the POS terminal 10 provided in tenant A identified by tenant code 1001. In this case, 1 is added to the number of receptions in December 20XX for tenant A in the reception management table 271 (for example, if the number of receptions was 9, it becomes 10).

In addition, the settlement data received by the communication control unit 211 is stored as settlement data for December 31, 20XX for tenant A in the sales management table 272 (December 31, 20XX for tenant A where 0 is input). payment data will be overwritten by the value of the received payment data).

The reception unit 212 receives input of payment data. Specifically, the reception unit 212 receives payment data input by the operator of the tenant management device 20 via an input device. The reception unit 212 accepts input of payment data when payment data cannot be received from the POS terminal 10 . The payment data received by the reception unit 212 is stored in the sales management table 272 in the same way as the payment data received by the communication control unit 211.

The first calculation unit 213 calculates the number of days on which the communication control unit 211 receives the payment data as the first business days within a predetermined calculation period related to rent calculation. Specifically, when there is an instruction to calculate the rent, the first calculation unit 213 refers to the reception management table 271 and performs a predetermined calculation for the target tenant if the target tenant is set to calculate the rent on a daily basis. The number of first business days is calculated from the number of receptions within the period.

More specifically, for example, consider a case where the first business days of December 20XX of tenant A identified by tenant code 1001 are calculated. In this case, the first calculation unit 213 refers to the reception management table 271 and calculates the number of receptions by tenant A in December 20XX as the first business days (for example, in the example of FIG. The first business day of December is 10).

The second calculation unit 214 receives or accepts payment data other than the payment data with zero sales from among the payment data received by the communication control unit 211 and the payment data accepted by the reception unit 212 within a predetermined calculation period. The number of days is calculated as the number of second business days.

Specifically, when there is an instruction to calculate the rent, the second calculation unit 214 refers to the sales management table 272 and calculates the amount within a predetermined calculation period if the target tenant is set to calculate the rent on a daily basis. , the number of days in which data other than zero is stored in one or more of the data included in the sales management table 272 is counted, and the counted number of days is calculated as the second number of business days.

More specifically, for example, a case will be considered in which the second number of business days in December 20XX of tenant A identified by tenant code 1001 is calculated.

In this case, the second calculation unit 214 refers to the sales management table 272 and stores data other than zero in one or more of the data such as tenant A's total sales between December 1, 20XX and December 31, 20XX. Counts the number of days that are remembered. For example, if the counted number of days is 9, the second calculation unit 214 calculates 9 as the second number of business days.

The determining unit 215 determines either the first number of business days or the second number of business days as the number of business days. Specifically, the determining unit 215 determines the greater number of business days between the first number of business days calculated by the first calculation unit 213 and the second number of business days calculated by the second calculation unit 214.

More specifically, for example, if the first number of business days calculated by the first calculation unit 213 is 10 and the second number of business days calculated by the second calculation unit 214 is 9, the determination unit 215 The number of days, 10, is determined as the number of business days.

Here, the determining unit 215 determines the larger number of business days between the first number of business days and the second number of business days as the number of business days, even if payment data cannot be transmitted for some reason or even if the tenant is open for business. This is because there may be days when sales are zero.

Specifically, for example, consider a case where the tenant was open for business, but there was a day when the sales were 0, and settlement data with all data of 0 was sent to the tenant management device 20. In this case, the day is counted as the first number of business days, but not as the second number of business days, so the first number of business days may be greater than the second number of business days.

For example, even though there were sales, there was a day when the POS terminal 10 could not send the payment data to the tenant management device 20 due to a problem with the communication I/F 13, and the reception unit 212 received the payment data for that day. Consider the case where input is accepted. In this case, the day is counted as the second number of business days, but not as the first number of business days, so the second number of business days may be greater than the first number of business days.

In this way, regardless of whether the first number of business days or the second number of business days is adopted, there may be cases where the tenant is not counted as the number of business days even though the tenant is open for business. and the second number of business days, whichever has the greater number of days will be determined as the number of business days.

The third calculation unit 216 calculates the rent when there is an instruction to calculate the rent. If the target tenant is not set to prorate the rent on a daily basis, the third calculation unit 216 calculates the fixed rent in the rent management table 273 as the requested rent to be charged to the tenant. Specifically, the third calculation unit 216 refers to the rent management table 273, identifies the fixed rent of the target tenant, and calculates the amount as the billed rent.

More specifically, for example, consider a case where the target tenant is not set to pro-rata the rent and charges rent to tenant A identified by tenant code 1001. In this case, the third calculation unit 216 refers to the rent management table 273, specifies the fixed rent of tenant A, and calculates the amount as the billed rent. For example, in the example of FIG. 8, the rent charged to tenant A is 300,000 yen.

In addition, if the target tenant is set to prorate the rent, the third calculation unit 216 sets either the first number of business days or the second number of business days as the number of business days within the predetermined calculation period, and Calculate the billed rent by multiplying the number of business days by the rent per day. Specifically, the third calculation unit 216 refers to the rent management table 273 and calculates the billed rent by multiplying the number of business days determined by the determination unit 215 by the daily rent set for the target tenant.

More specifically, for example, when the determining unit 215 determines that the number of business days in December 20XX of tenant A identified by tenant code 1001 is 10, and calculates the daily prorated rent of tenant A in December 20XX. think of. In this case, the third calculation unit 216 refers to the rent management table 273 and confirms tenant A's daily rent. For example, in the example of FIG. 8, tenant A's daily rent is 10,000 yen.

The third calculation unit 216 calculates the rent to be charged to tenant A by multiplying 10, which is the number of business days determined by the determination unit 215, by 10,000 yen. In this example, the rent charged to tenant A is 100,000 yen.

Note that the operator of the tenant management device 20 may manually instruct the third calculation unit 216 to calculate the rent at any timing, or the control unit 21 of the tenant management device 20 may instruct the third calculation unit 216 to calculate the rent at a preset date and time (for example, It may also be performed automatically at 0:00 on the first day of the month.

Next, the processing of the tenant management device 20 will be explained. FIG. 10 is a flowchart illustrating an example of the rent calculation process executed by the tenant management device 20.

First, the communication control unit 211 receives settlement data including information indicating the tenant's total sales from the POS terminal 10 (step S101).

Next, the storage unit 27 stores the settlement data in the sales management table 272 (step S102). Note that if the communication control unit 211 is unable to receive the payment data due to the specifications of the POS terminal 10 or the like, the reception unit 212 accepts input of the payment data. In this case, the storage unit 27 stores the payment data received by the reception unit 212 in the sales management table 272.

The third calculation unit 216 checks whether there is an instruction to calculate the rent (step S103). If there is no instruction to calculate the rent (step S103: No), the process returns to step S101.

On the other hand, if there is an instruction to calculate the rent (step S103: Yes), the third calculation unit 216 checks whether the target tenant is set to calculate the rent on a daily basis (step S104). If it is not set to be prorated on a daily basis (step S104: No), the third calculation unit 216 refers to the rent management table 273, calculates the fixed rent of the tenant to be billed as the billed rent, and ends this process. do.

If it is set to be calculated on a daily basis (step S104: Yes), the first calculation unit 213 refers to the reception management table 271 and calculates the number of receptions of payment data within a predetermined calculation period as the first number of business days ( Step S105).

Next, the second calculation unit 214 refers to the sales management table 272, and calculates the number of days in which data other than zero is input to one or more of the data included in the sales management table 272 within a predetermined calculation period. is calculated as the second number of business days (step S106). The determining unit 215 determines the greater number of days between the first number of business days and the second number of business days as the number of business days (step S107).

The third calculation unit 216 refers to the rent management table 273 and specifies the daily rent of the tenant to be billed. The third calculation unit 216 calculates the requested rent by multiplying the specified daily rent by the number of business days determined by the determination unit 215, and ends this process (step S108).

Next, the effects of the tenant management device 20 of this embodiment will be explained. In the tenant management device 20 according to the present embodiment, when the rent is calculated on a daily basis, the first calculation unit 213 calculates the first business days from the number of receptions of settlement data, and the second calculation unit 214 calculates the first business days from the sales management table 272. 2 Calculate the number of business days.

Then, the third calculation unit 216 takes one of the first number of business days and the second number of business days as the number of business days, multiplies the number of business days by a predetermined daily rent, and charges the tenant. Calculate the rent.

Therefore, the tenant management device 20 of this embodiment can automatically calculate the number of business days for calculating the daily rent based on the number of receptions of settlement data or the sales management table 272. In other words, the tenant management device 20 according to the present embodiment does not require manual input operations when determining the number of business days of a tenant necessary for calculating daily rent, and easily calculates daily rent. Is possible.

Further, the third calculation unit 216 calculates the billed rent by using the larger number of days between the first number of business days and the second number of business days as the number of business days. Thereby, the tenant management device 20 according to the present embodiment can reduce the risk that some days will not be counted as business days even though the tenant is open for business.

Further, when the rent is set to be calculated on a daily basis, the third calculation unit 216 sets either the first number of business days or the second number of business days as the number of business days within the predetermined calculation period, and calculates the number of business days as the number of business days. The billed rent is calculated by multiplying the daily rent. If the rent is not set to be prorated on a daily basis, the fixed rent is calculated as the billed rent.

As a result, it is possible to calculate the rent on a daily basis only when the rent is set to be calculated on a daily basis, thereby eliminating the need to calculate the rent on a daily basis in situations where there is no need to calculate the rent on a daily basis.

Furthermore, the tenant management device 20 according to the present embodiment can set whether or not to prorate the rent and the daily rent for each tenant. Thereby, it is possible to determine whether or not to calculate the rent on a daily basis, and how much to pay the rent per day when calculating the rent on a daily basis, depending on the circumstances of each tenant.

Although the embodiments of the present invention have been described above, the above embodiments are presented as examples and are not intended to limit the scope of the invention. The embodiments described above can be implemented in various other forms, and various omissions, substitutions, and changes can be made without departing from the gist of the invention. The above-described embodiments and modifications thereof are included within the scope and gist of the invention, as well as within the scope of the invention described in the claims and its equivalents.

For example, in the above embodiment, the rent is prorated on a daily basis, but the subject of daily proration is not limited to the rent. For example, other expenses such as management fees and facility usage fees may be subject to daily proration.

Furthermore, for example, in the embodiment described above, a mode has been described in which the larger number of days is determined as the number of business days between the first number of business days and the second number of business days. However, the determining unit 215 may determine the number of business days as the number of business days, whichever is arbitrarily selected by the operator of the tenant management device 20 from among the first number of business days or the second number of business days.

Further, in the above embodiment, the tenant management device 20 is configured to hold the reception management table 271, the sales management table 272, and the rent management table 273, but the present invention is not limited to this. For example, another device (such as a database server) that can be accessed by the tenant management device 20 may hold some or all of the reception management table 271, the sales management table 272, and the rent management table 273.

Note that the program executed by the tenant management device 20 of the above embodiment is a file in an installable format or an executable format, such as a CD-ROM, a flexible disk (FD), a CD-R, a DVD (Digital Versatile Disk), etc. It may also be configured to be recorded and provided on a computer-readable recording medium.

Further, the program executed by the tenant management device 20 of the above embodiment may be stored on a computer connected to a network such as the Internet, and may be provided by being downloaded via the network. Further, the program executed by the tenant management device 20 of the above embodiment may be provided or distributed via a network such as the Internet.

Moreover, each function that the tenant management device 20 (control unit) of the above embodiment has can also be realized by one or more processing circuits. Here, the processing circuit is a concept that includes a processor (such as a CPU), and hardware such as an ASIC (Application Specific Integrated Circuit) and a circuit module designed to realize each function.

1 tenant management system 10 POS terminal 11 control unit 12 bus 13 communication interface 14 I/O device control unit 15 input unit 16 display unit 17 storage unit 20 tenant management device 21 control unit 22 bus 23 communication interface 24 I/O device control unit 25 Input section 26 Display section 27 Storage section 111 Generation section 112 Communication control section 171 Total data table 211 Communication control section 212 Reception section 213 First calculation section 214 Second calculation section 215 Determination section 216 Third calculation section 271 Reception management table 272 Sales management table 273 Rent management table N Network

Japanese Patent Application Publication No. 2008-40970

Claims (6)

a receiving unit that receives settlement data containing information indicating one day's sales of the store from a terminal device installed in the store;
a reception unit that accepts input of the payment data when the reception unit cannot receive the payment data;
a management unit that manages on a daily basis the payment data of the store received by the reception unit and the payment data received by the reception unit;
a first calculation unit that calculates the number of days on which the reception unit receives the settlement data as a first business day within a predetermined calculation period related to calculation of expenses;
Within the calculation period, among the payment data received by the reception unit and the payment data accepted by the reception unit, the number of days in which payment data other than payment data with sales of zero is received or accepted is defined as the second business day. a second calculation unit that calculates;
a third calculation unit that calculates billed expenses by setting either the first number of business days or the second number of business days as the number of business days within the calculation period, and multiplying the number of business days by expenses per day;
An information processing device comprising: The third calculation unit calculates billed expenses by using the larger number of days between the first number of business days and the second number of business days as the number of business days.
The information processing device according to claim 1. When the expenses are set to be prorated on a daily basis, the third calculation unit sets either the first number of business days or the second number of business days as the number of business days within the calculation period, and calculates the number of business days as the number of business days. Multiply the daily expenses to calculate the billed expenses,
If the above expenses are not set to be prorated on a daily basis, fixed expenses will be calculated as billed expenses.
The information processing device according to claim 1 or 2. The management unit manages the payment data of the plurality of stores on a daily basis,
The information processing device according to any one of claims 1 to 3. Whether or not the expenses are to be prorated on a daily basis and the daily expenses can be set for each store;
The information processing device according to any one of claims 1 to 3. Computer of information processing equipment,
a receiving unit that receives settlement data containing information indicating one day's sales of the store from a terminal device installed in the store;
a reception unit that accepts input of the payment data when the reception unit cannot receive the payment data;
a management unit that manages the payment data of the store received by the reception unit on a daily basis;
a first calculation unit that calculates the number of days on which the reception unit receives the payment data as a first business day within a predetermined calculation period related to calculation of expenses;
Within the calculation period, among the payment data received by the receiving unit and the payment data accepted by the reception unit, the number of days in which payment data other than payment data with sales of zero is received or accepted is defined as the second business day. a second calculation unit that calculates;
a third calculation unit that calculates billed expenses by setting either the first number of business days or the second number of business days as the number of business days within the calculation period, and multiplying the number of business days by expenses per day;
A program that functions as

Images