Billing management device, billing management method, and billing management program

Abstract

We provide billing management systems and other devices that can reduce fees, contribute to profits, and improve operational efficiency. [Solution] A billing management device equipped with a control unit, the control unit registers sales data that associates information about the billing customer, the date of sale, the sales amount, the scheduled collection date, and the collection method, and creates billing data that adjusts the timing of billing the aggregated sales amount of the billing customer to the billing customer based on the sales data and a billing customer master that associates information about the billing customer, the billing base amount, a billing grouping category indicating whether or not the billing customer is subject to collective billing, and information regarding the collection of the billing amount.

Description

Technical Field

[0001] The present invention relates to a billing management device, a billing management method, and a billing management program.

Background Art

[0002] In the distribution and retail industry, there is a business model in the BtoC business that regularly provides small-value services. Here, BtoC is an abbreviation for "Business to Consumer" and "Business to Customer", and is a business model in which a company provides goods or services to individuals. Note that in BtoB, it is an abbreviation for "Business to Business", and is a business model in which a company provides goods or services to another company as a commercial transaction between companies.

[0003] When a small-value transaction continues in a regular purchase / regular contract service, the amount billed to a single customer at one time becomes small. Here, when billing under the settlement condition of bank transfer, if the company bears the transfer fee, the burden of the fee becomes large, and there is a problem that it has a great impact on the profit of a business that conducts low-margin and high-volume sales. Conventionally, it has been common practice to temporarily set the sales amount or the billing amount to zero manually, invalidate the billing, and then adjust the billing amount by adding the previous month's amount to the next month's billing to suppress the fee.

[0004] Regarding billing management, for example, in Patent Document 1, in order to solve the problem that in some cases, it may be necessary to suddenly change the billing destination after performing billing processing in work units, request units, etc., various conditions such as the billing destination, sales period, request unit, contract classification, etc. are specified to perform closing processing, and a configuration is disclosed that enables the issuance of a bill, thereby contributing to an early grasp of the actual amount with respect to the project budget of the billing destination and an early start of the payment procedure.

Prior Art Documents

Patent Documents

[0005] [Patent Document 1] Japanese Patent Publication No. 2022-041148 [Overview of the project] [Problems that the invention aims to solve]

[0006] The present invention has been made in view of the above problems, and aims to provide a billing management device, a billing management method, and a billing management program that can reduce fees, contribute to profits, and improve the efficiency of operations. [Means for solving the problem]

[0007] To solve the above-mentioned problems and achieve the objective, the billing management device according to the present invention is a billing management device comprising a control unit, the control unit comprising: a reception unit that registers sales data associating information about the billing customer, the date of sale, the sales amount, the scheduled date of collection, and the collection method; a billing customer master that associates information about the billing customer, the billing base amount, a billing summary classification indicating whether or not the billing customer is subject to collective billing, and information regarding the collection of the billing amount; and a creation unit that creates billing data that adjusts the timing of billing the billing customer for the aggregated sales amount of the billing customer based on the sales data.

[0008] Furthermore, in the billing management device according to the present invention, the creation unit is characterized in that it creates the billing data based on the billing customer master, the sales data, and the comparison result between the aggregated sales amount of the billing customer and the billing base amount.

[0009] Furthermore, in the billing management device according to the present invention, the creation unit creates a billing data work that associates information about the billing customer, the aggregated sales amount of the billing customer, the billing basis amount, and a current billing flag indicating whether or not to bill the billing customer, based on the billing customer master, the sales data, and the comparison result of the aggregated sales amount of the billing customer and the billing basis amount, and creates the billing data based on the billing data work.

[0010] Furthermore, in the billing management device according to the present invention, the creation unit creates a billing data work that associates information about the billing destination, the aggregated sales amount of the billing destination, the billing standard amount, and the current billing flag indicating that the billing destination will be billed this time, when the billing destination master indicates that the billing aggregation category of the billing destination is the target of billing for a group billing, and the aggregated sales amount of the billing destination is equal to or greater than the billing standard amount, and based on the billing data work, creates billing data to bill the billing destination for the aggregated sales amount of the billing destination on the scheduled collection date.

[0011] Furthermore, in the billing management device according to the present invention, the creation unit creates a billing data work that associates information about the billing destination, the aggregated sales amount of the billing destination, the billing standard amount, and the current billing flag indicating that the billing destination will not be billed this time, when the billing destination master indicates that the billing aggregation category of the billing destination is the target of billing for a group billing, and the aggregated sales amount of the billing destination is less than the billing standard amount, and based on the billing destination master and the billing data work, changes the scheduled collection date to the next scheduled collection date and updates the sales data.

[0012] Furthermore, in the billing management device according to the present invention, if the billing aggregation classification of the billing destination master indicates that the billing destination is not subject to collective billing, the creation unit creates a billing data work that associates information about the billing destination, the aggregated sales amount of the billing destination, the billing base amount, and the current billing flag indicating that the billing destination will be billed this time, and based on the billing data work, creates billing data to bill the billing destination for the aggregated sales amount of the billing destination on the scheduled collection date.

[0013] Furthermore, the billing management method according to the present invention is a billing management method to be executed by a billing management device equipped with a control unit, and is characterized in that the control unit includes: a reception step of registering sales data that associates information about the customer, the date of sale, the sales amount, the scheduled date of collection, and the collection method; a creation step of creating billing data that adjusts the timing of billing the customer for the aggregated sales amount of the customer, based on the customer information, the billing base amount, a billing summary classification indicating whether or not the customer is subject to collective billing, and information regarding the collection of the billing amount, and the sales data.

[0014] Furthermore, the billing management program according to the present invention is a billing management program to be executed by a billing management device equipped with a control unit, characterized in that the control unit executes: a reception step of registering sales data that associates information about the customer, the date of sale, the sales amount, the scheduled date of collection, and the collection method; a creation step of creating billing data that adjusts the timing of billing the customer based on the customer information, the billing base amount, a billing summary classification indicating whether or not the customer is subject to collective billing, and information regarding the collection of the billing amount, and the sales data. [Effects of the Invention]

[0015] This invention has the effect of reducing fees, contributing to profits, and improving operational efficiency. [Brief explanation of the drawing]

[0016] [Figure 1] Figure 1 is a block diagram showing an example of the configuration of the billing management device in this embodiment. [Figure 2] Figure 2 is a flowchart showing an example of the processing performed by the billing management device in this embodiment. [Figure 3] Figure 3 shows an example of the processing performed by the billing management device in this embodiment. [Figure 4]FIG. 4 is a diagram showing an example of the processing of the claim management apparatus in the present embodiment. [Figure 5] FIG. 5 is a diagram showing an example of the processing of the claim management apparatus in the present embodiment. [Figure 6] FIG. 6 is a diagram showing an example of the processing of the claim management apparatus in the present embodiment. [Figure 7] FIG. 7 is a diagram showing an example of the processing of the claim management apparatus in the present embodiment. [Figure 8] FIG. 8 is a diagram showing an example of the processing of the claim management apparatus in the present embodiment. [Figure 9] FIG. 9 is a diagram showing an example of the processing of the claim management apparatus in the present embodiment. [Figure 10] FIG. 10 is a diagram showing an example of the processing of the claim management apparatus in the present embodiment. [Figure 11] FIG. 11 is a diagram showing an example of the processing of the claim management apparatus in the present embodiment. BEST MODE FOR CARRYING OUT THE INVENTION

[0017] Hereinafter, embodiments of a claim management apparatus, a claim management method, and a claim management program according to the present invention will be described in detail based on the drawings. Note that the present invention is not limited by the present embodiment.

[0018] [1. Overview] [[ID=z35]]First, the overview of the present invention will be described.

[0019] In the retail industry, there are business models that provide small-value services on a regular basis in B2C (business-to-consumer) operations. When small transactions continue through recurring purchase or contract services, the amount billed to each customer at one time is small. However, when billing with bank transfer as the payment method, if the company bears the transfer fees, the burden of fees becomes significant, which can greatly impact the profitability of businesses that rely on high volume sales with low profit margins. Until now, it has been common practice to reduce fees by manually resetting the sales or billing amount to zero, invalidating the invoice, and then adjusting the billing amount the following month by adding the previous month's amount.

[0020] For example, when providing services through recurring purchases or contracts, in most cases, the company bears the bank transfer fees if it bills monthly for small transactions. Therefore, in this embodiment, by creating a system that pools invoices up to a certain amount, it is possible to reduce bank transfer fees.

[0021] Furthermore, in B2C transactions involving rentals or subscriptions, the number of customers and contracts can reach tens of thousands, making manual control of billing impossible. In the case of low-margin, high-volume sales, bank transfer fees also become substantial. Therefore, in this embodiment, consolidated billing contributes to profits and improves operational efficiency by consolidating the number of bills.

[0022] While a larger amount collected at once increases the risk of non-payment, it is expected that such risks can be avoided by conducting credit checks at the time of contracting with customers and only performing transactions with low-risk customers.

[0023] [2. Structure] An example of the configuration of the billing management device 100 according to this embodiment will be described with reference to Figure 1, etc. Figure 1 is a block diagram showing an example of the configuration of the billing management device 100.

[0024] The billing management device 100 is built on a commercially available desktop personal computer. However, the billing management device 100 is not limited to being built on a stationary information processing device such as a desktop personal computer; it may also be built on a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

[0025] The billing management device 100 comprises a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each part of the billing management device 100 is connected to communicate via any communication path.

[0026] The communication interface unit 104 connects the billing management device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has the function of communicating data with other devices via a communication line. Here, the network 300 has the function of connecting the billing management device 100 and the server 200 so that they can communicate with each other, and is, for example, the internet or a LAN (Local Area Network). The data stored in the storage unit 106 may be stored in, for example, the server 200.

[0027] The input / output interface unit 108 is connected to an input device 112 and an output device 114. The output device 114 can be a monitor (including a home television), a speaker, or a printer. The input device 112 can be a keyboard, a mouse, a microphone, or a monitor that works in conjunction with a mouse to provide pointing device functionality. In the following, the output device 114 may be referred to as the monitor 114, and the input device 112 may be referred to as the keyboard 112 or mouse 112.

[0028] The memory unit 106 stores various databases, tables, and files. The memory unit 106 also stores computer programs that work in cooperation with the OS (Operating System) to give instructions to the CPU (Central Processing Unit) to perform various processes. As the memory unit 106, for example, memory devices such as RAM (Random Access Memory) and ROM (Read Only Memory), fixed disk devices such as hard disks, flexible disks, and optical disks can be used.

[0029] Furthermore, the storage unit 106 includes a billing master 106a. For example, the billing master 106a is a master that sets records that associate information about the billing recipient, the billing base amount, the billing consolidation category, and information about the collection of the billed amount. For example, information about the billing recipient may include the billing recipient code and the billing recipient name. The billing consolidation category indicates whether or not the billing recipient is subject to consolidated billing. For example, information about the collection of the billed amount may include the closing date, collection method, planned collection month, and planned collection date. A collection method may be bank transfer.

[0030] Furthermore, sales data 106b is registered in the storage unit 106. For example, the storage unit 106 registers sales data 106b, which includes information about the billing party, the date of sale, the sales amount, the scheduled collection date, and the collection method. For example, the sales amount is the amount excluding consumption tax, and is what is known as the net sales amount.

[0031] The control unit 102 is a CPU or the like that comprehensively controls the billing management device 100. The control unit 102 has internal memory for storing control programs such as the OS, programs that define various processing procedures, and required data, and executes various information processing based on these stored programs. Functionally, the control unit 102 comprises a receiving unit 102a and a creation unit 102b.

[0032] The reception unit 102a registers the sales data 106b in the storage unit 106. For example, the reception unit 102a displays the sales input screen and receives the sales input information, thereby registering the sales data 106b in the storage unit 106, associating it with information about the billing party (billing party code, billing party name), the sales date, the sales amount (actual sales amount), the scheduled collection date, and the collection method.

[0033] The creation unit 102b creates billing data 106d based on the customer master 106a and sales data 106b, adjusting the timing of billing the customer for the aggregated sales amount. Specifically, the creation unit 102b extracts the sales data to be billed based on the customer master 106a and sales data 106b. Next, the creation unit 102b creates billing data work 106c based on the customer master 106a, sales data 106b, and the comparison result between the aggregated sales amount of the customer and the billing base amount of the extracted sales data. This work 102b associates customer information (customer code, customer name), the aggregated sales amount of the customer, the billing base amount, and a current billing flag indicating whether or not to bill the customer this time. Finally, the creation unit 102b registers the created billing data work 106c in the storage unit 106. Next, the creation unit 102b creates the billing data 106d based on the billing data work 106c and registers the created billing data 106d in the storage unit 106.

[0034] [3. Specific examples of processing] A specific example of the processing (billing management processing) of the billing management device of this embodiment will be described with reference to Figures 2 to 11.

[0035] [3.1 Billing Management Process] Now, with reference to Figure 2, an example of the processing of the billing management device in this embodiment will be described. Figure 2 is a flowchart showing an example of the processing of the billing management device 100 in this embodiment.

[0036] First, in the sales data reception process, the reception unit 102a receives the sales input information and registers sales data 106b in the storage unit 106, which associates information about the billing party (billing party code, billing party name), the sales date, the sales amount (actual sales amount), the scheduled collection date, and the collection method (step S101).

[0037] Next, in the billing data extraction process, the creation unit 102b extracts the sales data to be billed based on the customer master 106a and the sales data 106b (step S102). Next, in the billing data work creation process, the creation unit 102b creates a billing data work 106c that associates customer information (customer code, customer name), the aggregated sales amount of the customer, and the billing basis amount based on the customer master 106a, the sales data 106b, and the comparison result between the aggregated sales amount of the customer and the billing basis amount of the extracted sales data (step S103).

[0038] Next, in the sales data temporary invoice number update process, the creation unit 102b registers a temporary invoice number in the extracted sales data and updates the sales data 106b (step S104). Next, in the billing data work current billing flag update process, the creation unit 102b registers a current billing flag in the billing data work 106c, indicating whether or not to bill the recipient this time, and updates the billing data work 106c (step S105).

[0039] Next, in the billing data creation process, the creation unit 102b creates billing data 106d based on the updated billing data work 106c (step S106). Next, in the sales data billing number update process, the creation unit 102b registers a billing number for the extracted sales data in place of the temporary billing number and updates the sales data 106b. The creation unit 102b also registers the scheduled collection date for the extracted sales data and updates the sales data 106b (step S107).

[0040] [3.2 Specific Examples of Billing Management Processes] Here, with reference to Figures 3 to 11, specific examples of the sales data reception process (step S101), billing target data extraction process (step S102), billing data work creation process (step S103), sales data temporary billing number update process (step S104), billing data work current billing flag update process (step S105), billing data creation process (step S106), and sales data billing number update process (step S107) will be explained. Figures 3 to 11 show an example of the processing of the billing management device in this embodiment.

[0041] First, as shown in Figures 3 and 4, in this embodiment, the billing master 106a is registered. For example, as shown in Figure 3, the reception unit 102a displays the billing master input screen and receives the information from the billing master. Suppose the user uses the input device 112 to input the billing code "0001", billing name "Sakaguchi-sama", billing summary category "1: Target", billing base amount "2,000", closing date "31", collection method "1001: Bank transfer", collection scheduled month "1: Next month", collection scheduled date "31", etc., into the screen. In this case, as shown in Figure 4, the reception unit 102a registers information about the billing recipient (billing recipient code "0001", billing recipient name "Sakaguchi-sama"), billing base amount "2,000", billing aggregation category "1: Target", and information about the collection of the billed amount (closing date "31", collection method "1001: Bank transfer", collection scheduled month "1: Next month", collection scheduled date "31") in the storage unit 106 as the billing recipient master 106a.

[0042] Here, the billing consolidation category represents, for example, "1: Targeted" if the billing party is subject to consolidated billing, and "0: Not Targeted" if the billing party is not subject to consolidated billing. When the billing consolidation category represents "1: Targeted," that billing party is a customer that, when the billing threshold is referenced during the creation of billing data, will be billed in a consolidated manner when the amount of a single bill exceeds the billing threshold. When the billing consolidation category represents "0: Not Targeted," that billing party is a customer that will be billed according to the billing category. For example, a credit check is performed when a contract is made with a customer, and customers (customers) with low risk are designated as targets for consolidated billing. In other words, customers with a billing consolidation category of "1: Targeted" are low-risk customers.

[0043] Furthermore, the billing threshold is set for business partners whose billing aggregation category is "1: Target". In this embodiment, if the amount of a single invoice is less than the billing threshold, the customer will not be billed. In this embodiment, when comparing the invoice amount and the billing threshold, the consumption tax amount is not included, and the total sales amount is compared with the billing threshold as the invoice amount.

[0044] For example, suppose a user uses the input device 112 to input the following information into the screen: billing code "0002", billing name "Mr. / Ms. Miyazaki", billing aggregation category "1: Target", billing base amount "2,000", closing date "31", collection method "1001: Bank transfer", collection month "1: Next month", and collection date "31". In this case, as shown in Figure 4, the reception unit 102a registers the billing information (billing code "0002", billing name "Mr. / Ms. Miyazaki"), billing base amount "2,000", billing aggregation category "1: Target", and information regarding the collection of the billed amount (closing date "31", collection method "1001: Bank transfer", collection month "1: Next month", collection date "31") in association with the information in the storage unit 106 as the billing master 106a.

[0045] For example, suppose a user uses the input device 112 to input the following information into the screen: billing code "0003", billing name "Mr. Tahara", billing aggregation category "0: Not applicable", billing base amount "0", closing date "31", collection method "1001: Bank transfer", collection month "1: Next month", and collection date "31". In this case, as shown in Figure 4, the reception unit 102a registers the billing information (billing code "0003", billing name "Mr. Tahara"), billing base amount "0", billing aggregation category "0: Not applicable", and information regarding the collection of the billed amount (closing date "31", collection method "1001: Bank transfer", collection month "1: Next month", collection date "31") in association with the information in the storage unit 106 as the billing master 106a.

[0046] Similarly, for inputting the billing master data related to billing code "0004", the user uses the input device 112 to input the billing code "0004", billing name "Mr. Mori", billing summary category "0: Not applicable", billing base amount "0", closing date "20", collection method "1001: Bank transfer", collection scheduled month "1: Next month", collection scheduled date "31", etc. into the billing master input screen, and the reception unit 102a registers these as billing master data 106a in the storage unit 106.

[0047] Next, as shown in Figure 5, sales data 106b is registered in the sales data reception process (step S101). For example, the reception unit 102a displays the sales input screen and receives the sales input information, and the user enters the following on the screen using the input device 112: invoice number "UR0001", sales date "2024 / 7 / 3", billing code "0001", billing name "Sakaguchi-sama", sales amount "1,000", consumption tax amount "100", initial collection date "2024 / 8 / 31", collection date "2024 / 8 / 31", collection method "bank transfer", etc. In this case, the reception unit 102a registers the following information as sales data 106b in the storage unit 106: invoice number "UR0001", billing information (billing code "0001", billing name "Sakaguchi-sama"), sales date "2024 / 7 / 3", sales amount (base sales amount "1,000"), consumption tax amount "100", initial collection date "2024 / 8 / 31", scheduled collection date "2024 / 8 / 31", and collection method "bank transfer".

[0048] For example, suppose a user uses the input device 112 to enter the following information into the screen: invoice number "UR0002", sales date "2024 / 7 / 3", billing code "0001", billing name "Mr. Sakaguchi", sales amount "500", consumption tax amount "50", initial collection date "2024 / 8 / 31", scheduled collection date "2024 / 8 / 31", and collection method "bank transfer". In this case, the reception unit 102a registers the following information as sales data 106b in the storage unit 106: invoice number "UR0002", information about the billing recipient (billing recipient code "0001", billing recipient name "Sakaguchi-sama"), sales date "2024 / 7 / 3", sales amount (base sales amount "500"), consumption tax amount "50", initial collection date "2024 / 8 / 31", scheduled collection date "2024 / 8 / 31", and collection method "bank transfer".

[0049] For example, suppose a user uses the input device 112 to enter the following information into the screen: invoice number "UR0003", sales date "2024 / 7 / 10", billing code "0002", billing name "Mr. / Ms. Miyazaki", sales amount "1,000", consumption tax amount "100", initial collection date "2024 / 8 / 31", scheduled collection date "2024 / 8 / 31", and collection method "bank transfer". In this case, the reception unit 102a registers the following information as sales data 106b in the storage unit 106: invoice number "UR0003", information about the billing recipient (billing recipient code "0002", billing recipient name "Mr. / Ms. Miyazaki"), sales date "2024 / 7 / 10", sales amount (base sales amount "1,000"), consumption tax amount "100", initial collection date "2024 / 8 / 31", scheduled collection date "2024 / 8 / 31", and collection method "bank transfer".

[0050] For example, suppose a user uses the input device 112 to enter the following information into the screen: invoice number "UR0004", sales date "2024 / 7 / 10", billing code "0002", billing name "Mr. / Ms. Miyazaki", sales amount "1,000", consumption tax amount "100", initial collection date "2024 / 8 / 31", scheduled collection date "2024 / 8 / 31", and collection method "bank transfer". In this case, the reception unit 102a registers the following information as sales data 106b in the storage unit 106: invoice number "UR0004", information about the billing recipient (billing recipient code "0002", billing recipient name "Mr. / Ms. Miyazaki"), sales date "2024 / 7 / 10", sales amount (base sales amount "1,000"), consumption tax amount "100", initial collection date "2024 / 8 / 31", scheduled collection date "2024 / 8 / 31", and collection method "bank transfer".

[0051] For example, suppose a user uses the input device 112 to enter the following information into the screen: invoice number "UR0005", sales date "2024 / 7 / 10", billing code "0003", billing name "Mr. / Ms. Tahara", sales amount "300", consumption tax amount "30", initial collection date "2024 / 8 / 31", scheduled collection date "2024 / 8 / 31", and collection method "bank transfer". In this case, the reception unit 102a registers the following information as sales data 106b in the storage unit 106: invoice number "UR0005", information about the billing recipient (billing recipient code "0003", billing recipient name "Mr. Tahara"), sales date "2024 / 7 / 10", sales amount (base sales amount "300"), consumption tax amount "30", initial collection date "2024 / 8 / 31", scheduled collection date "2024 / 8 / 31", and collection method "bank transfer".

[0052] For example, suppose a user uses the input device 112 to enter the following information into the screen: invoice number "UR0006", sales date "2024 / 7 / 10", billing code "0003", billing name "Mr. / Ms. Tahara", sales amount "200", consumption tax amount "20", initial collection date "2024 / 8 / 31", scheduled collection date "2024 / 8 / 31", and collection method "bank transfer". In this case, the reception unit 102a registers the following information as sales data 106b in the storage unit 106: invoice number "UR0006", information about the billing recipient (billing recipient code "0003", billing recipient name "Mr. Tahara"), sales date "2024 / 7 / 10", sales amount (base sales amount "200"), consumption tax amount "20", initial collection date "2024 / 8 / 31", scheduled collection date "2024 / 8 / 31", and collection method "bank transfer".

[0053] Similarly, for sales entries related to the billing code "0004" and billing name "Mr. Mori," the user uses the input device 112 to enter the slip number "UR9999," sales date "2024 / 7 / 10," billing code "0004," billing name "Mr. Mori," sales amount "500," consumption tax amount "50," initial collection date "2024 / 8 / 31," scheduled collection date "2024 / 8 / 31," and collection method "bank transfer" into the sales entry screen. The reception unit 102a then registers these as sales data 106b in the storage unit 106, associating them with each other.

[0054] Next, the reception unit 102a displays a billing closing processing screen as shown in Figure 5, for example, if the closing date of the billing master 106a is "31" and the date is "2024 / 7 / 31". For example, on the billing closing processing screen, the reception unit 102a displays the billing closing date "2024 / 7 / 31", the closing date "31", and the display button "Register". For example, suppose a user presses the display button "Register Set" on the billing closing processing screen using the input device 112. At this time, the billing target data extraction process (step S102) is performed.

[0055] As shown in Figures 5 and 6, in the billing data extraction process (step S102), the creation unit 102b extracts the sales data to be billed based on the billing master 106a and the sales data 106b. Specifically, the creation unit 102b retrieves from the storage unit 106 the sales data 106b whose sales date is within the billing closing date "2024 / 7 / 31" based on the billing master 106a and the sales data 106b. For example, the creation unit 102b retrieves from the storage unit 106 the sales data 106b containing invoice numbers "UR0001" to "UR0006" as sales data 106b whose sales date is within the billing closing date "2024 / 7 / 31" based on the billing master 106a and the sales data 106b. At this time, the billing data work creation process (step S103) is performed.

[0056] As shown in Figure 6, in the billing data work creation process (step S103), the creation unit 102b creates a billing data work 106c that associates information about the customer (customer code, customer name), the aggregated sales amount of the customer, and the billing basis amount, based on the customer master 106a, sales data 106b, and the comparison result between the aggregated sales amount of the customer from the extracted sales data and the billing basis amount.

[0057] For example, the creation unit 102b adds up the sales amounts of "1,000" and "500" for the customer code "0001" and customer name "Sakaguchi-sama," and uses the sum "1,500" as the aggregated sales amount for the customer. The creation unit 102b then assigns "KEQ0001" as a temporary invoice number and creates an invoice data worksheet 106c that associates the temporary invoice number "KEQ0001," customer information (customer code "0001," customer name "Sakaguchi-sama"), the aggregated sales amount for the customer (this purchase amount "1,500"), the consumption tax amount "150," the invoiced amount "1,650," and the invoice base amount "2,000."

[0058] For example, the creation unit 102b adds up the sales amounts of "1,000" and "1,000" for the customer code "0002" and customer name "Mr. / Ms. Miyazaki," and uses the sum "2,000" as the aggregated sales amount for the customer. The creation unit 102b then assigns "KEQ0002" as a temporary invoice number and creates an invoice data worksheet 106c that associates the temporary invoice number "KEQ0002," customer information (customer code "0002," customer name "Mr. / Ms. Miyazaki"), the aggregated sales amount for the customer (this purchase amount "2,000"), the consumption tax amount "200," the invoiced amount "2,200," and the invoice base amount "2,000."

[0059] For example, the creation unit 102b adds up the sales amounts of "300" and "200" for the customer with the customer code "0003" and customer name "Mr. Tahara," and uses the sum "500" as the aggregated sales amount for the customer. The creation unit 102b then assigns "KEQ0003" as a temporary invoice number and creates an invoice data worksheet 106c that associates the temporary invoice number "KEQ0003," customer information (customer code "0003," customer name "Mr. Tahara"), the aggregated sales amount for the customer, the purchase amount "500," the consumption tax amount "50," the invoice amount "550," and the invoice base amount "0."

[0060] Next, as shown in Figure 6, in the sales data temporary invoice number update process (step S104), the creation unit 102b registers the temporary invoice number in the extracted sales data and updates the sales data 106b.

[0061] For example, the creation unit 102b, based on sales data 106b which includes invoice numbers "UR0001" and "UR0002", billing code "0001", and billing name "Sakaguchi", and billing data work 106c which includes billing code "0001" and billing name "Sakaguchi", registers the temporary invoice number "KEQ0001" in the billing data work 106c and updates the sales data 106b, associating it with the invoice numbers "UR0001" and "UR0002" in the sales data 106b.

[0062] For example, the creation unit 102b, based on sales data 106b which includes invoice numbers "UR0003" and "UR0004", billing code "0002", and billing name "Mr. Miyazaki", and billing data work 106c which includes billing code "0002" and billing name "Mr. Miyazaki", registers the temporary invoice number "KEQ0002" in the billing data work 106c, associating it with the invoice numbers "UR0003" and "UR0004" in the sales data 106b, and updates the sales data 106b.

[0063] For example, the creation unit 102b, based on sales data 106b which includes invoice numbers "UR0005" and "UR0006", billing code "0003", and billing name "Mr. Tahara", and billing data work 106c which includes billing code "0003" and billing name "Mr. Tahara", registers the temporary invoice number "KEQ0003" in the billing data work 106c, associating it with the invoice numbers "UR0005" and "UR0006" in the sales data 106b, and updates the sales data 106b.

[0064] Next, as shown in Figure 7, in the billing data work current billing flag update process (step S105), the creation unit 102b registers a current billing flag for the billing data work 106c, indicating whether or not to bill the recipient this time, and updates the billing data work 106c.

[0065] For example, in billing data work 106c, the billing code "0001" and billing name "Sakaguchi-sama" indicate that the billing aggregation category "1: Target" in billing master 106a is a target for consolidated billing, and the aggregated sales amount of the billing recipient (current purchase amount "1,500") is below the billing threshold amount "2,000". In this case, the creation unit 102b associates billing code "0001" and billing name "Sakaguchi-sama" in billing data work 106c with a current billing flag "0: No billing", indicating that the billing recipient will not be billed this time, and updates the billing data work 106c. In other words, the creation unit 102b created a billing data work 106c that associates information about the billing recipient (billing recipient code "0001", billing recipient name "Mr. Sakaguchi"), the total sales amount for the billing recipient (this time's purchase amount "1,500"), the consumption tax amount "150", the billing amount "1,650", the billing base amount "2,000", and a billing flag "0: No billing" indicating that the billing recipient will not be billed this time.

[0066] For example, for the billing address code "0002" and billing address name "Miyazaki-sama" in billing data work 106c, the billing aggregation category "1: Target" in billing address master 106a indicates that the billing address is subject to a combined billing, and the aggregated sales amount of the billing address (current purchase amount "2,000") is equal to or greater than the billing base amount "2,000". In this case, the creation unit 102b associates the billing address code "0002" and billing address name "Miyazaki-sama" in billing data work 106c with the current billing flag "1: Billing Included", indicating that the billing address will be billed this time, and updates the billing data work 106c. In other words, the creation unit 102b created a billing data work 106c that associates information about the billing recipient (billing recipient code "0002", billing recipient name "Mr. / Ms. Miyazaki"), the total sales amount of the billing recipient (this time purchase amount "2,000"), the consumption tax amount "200", the billing amount "2,200", the billing base amount "2,000", and the current billing flag "1: billing issued" which indicates that the billing recipient will be billed this time.

[0067] For example, regarding the customer code "0003" and customer name "Mr. Tahara" in the billing data work 106c, the billing aggregation classification "0: Not applicable" in the customer master 106a indicates that the customer is not subject to consolidated billing. In this case, the creation unit 102b associates the customer code "0003" and customer name "Mr. Tahara" in the billing data work 106c with the current billing flag "1: Billing Included", indicating that the customer will be billed this time, and updates the billing data work 106c. In other words, the creation unit 102b has created a billing data work 106c that associates customer information (customer code "0003", customer name "Mr. Tahara"), the total sales amount of the customer (current purchase amount "500"), the consumption tax amount "50", the billing amount "550", the billing base amount "0", and the current billing flag "1: Billing Included", indicating that the customer will be billed this time.

[0068] Next, as shown in Figure 7, in the billing data creation process (step S106), the creation unit 102b creates billing data 106d based on the updated billing data work 106c.

[0069] For example, as described above, in the billing data work current billing flag update process (step S105), the creation unit 102b creates billing data work 106c that associates information about the billing recipient (billing recipient code "0002", billing recipient name "Miyazaki-sama"), the aggregated sales amount of the billing recipient (current purchase amount "2,000"), the consumption tax amount "200", the billing amount "2,200", the billing base amount "2,000", and the current billing flag "1: billing available" which indicates that the billing recipient will be billed this time. In this case, in the billing data creation process (step S106), the creation unit 102b creates billing data 106d based on the billing data work 106c, to bill the billing recipient with the aggregated sales amount of the billing recipient (current purchase amount "2,000") on the scheduled collection date "2024 / 8 / 31". Specifically, the creation unit 102b assigns "SEQ0001" as the invoice number and creates invoice data 106d that associates the following information: information about the customer (customer code "0002", customer name "Mr. / Ms. Miyazaki"), invoice number "SEQ0001", total sales amount for the customer (total purchase amount "2,000"), consumption tax amount "200", and total invoice amount "2,200".

[0070] For example, as described above, in the billing data work current billing flag update process (step S105), the creation unit 102b creates billing data work 106c that associates information about the billing recipient (billing recipient code "0003", billing recipient name "Mr. Tahara"), the aggregated sales amount of the billing recipient (current purchase amount "500"), the consumption tax amount "50", the billing amount "550", the billing base amount "0", and the current billing flag "1: billing available" which indicates that the billing recipient will be billed this time. In this case, in the billing data creation process (step S106), the creation unit 102b creates billing data 106d based on the billing data work 106c, to bill the billing recipient with the aggregated sales amount of the billing recipient (current purchase amount "500") on the scheduled collection date "2024 / 8 / 31". Specifically, the creation unit 102b assigns "SEQ0002" as the invoice number and creates invoice data 106d that associates the following information: customer information (customer code "0003", customer name "Mr. Tahara"), invoice number "SEQ0002", total sales amount for the customer (total purchase amount "500"), consumption tax amount "50", and total invoice amount "550".

[0071] Next, as shown in Figure 7, in the sales data invoice number update process (step S107), the creation unit 102b updates the sales data 106b based on the created invoice data 106d.

[0072] For example, based on sales data 106b which includes invoice numbers "UR0003" and "UR0004", billing code "0002", and billing name "Mr. Miyazaki", and billing data 106d which includes billing code "0002" and billing name "Mr. Miyazaki", the creation unit 102b registers the billing number "SEQ0001" from billing data 106d in place of the temporary billing number "KEQ0002" which was registered in association with invoice numbers "UR0003" and "UR0004" in sales data 106b, and updates sales data 106b.

[0073] For example, based on sales data 106b which includes invoice numbers "UR0005" and "UR0006", billing code "0003", and billing name "Mr. Tahara", and billing data 106d which includes billing code "0003" and billing name "Mr. Tahara", the creation unit 102b registers the billing number "SEQ0002" from billing data 106d in place of the temporary billing number "KEQ0003" which was registered in association with the invoice numbers "UR0005" and "UR0006" in sales data 106b, and updates sales data 106b.

[0074] Here, the creation unit 102b updates the sales data 106b associated with the record in the billing data work 106c with the current billing flag "0: No billing" by leaving the billing number blank. Also, as described above, the creation unit 102b sets the billing number from billing data 106d for the sales data 106b associated with the record in the billing data work 106c with the current billing flag "1: Billing issued".

[0075] Furthermore, as shown in Figure 7, in the sales data invoice number update process (step S107), the creation unit 102b registers the scheduled collection date for the extracted sales data and updates the sales data 106b.

[0076] As described above, in the billing data work current billing flag update process (step S105), the creation unit 102b creates billing data work 106c that associates information about the billing recipient (billing recipient code "0001", billing recipient name "Sakaguchi-sama"), the total sales amount for the billing recipient (current purchase amount "1,500"), the consumption tax amount "150", the billing amount "1,650", the billing base amount "2,000", and the current billing flag "0: No billing" which indicates that the billing recipient will not be billed this time. In this case, in the billing data creation process (step S106), the creation unit 102b does not create billing data 106d, and in the sales data billing number update process (step S107), based on the billing recipient master 106a and the billing data work 106c, it changes the scheduled collection date "2024 / 8 / 31" to the next scheduled collection date "2024 / 9 / 30", and updates the sales data 106b.

[0077] In this embodiment, for slips from the extracted data for which no billing data was created, the data is carried over to the next billing cycle. Therefore, the creation unit 102b updates the scheduled collection date assuming it will be billed next time. The date to be updated is one month added to the original scheduled collection date. This change is necessary because the timing of billing will be shifted.

[0078] Next, I will explain the operations for the following month. For example, as shown in Figure 8, in the sales data reception process (step S101), a sales entry for invoice number "UR0008" was made in the previous month, and in the following month, new sales entries for invoice numbers "UR0009" to "UR0013" were made.

[0079] For example, with respect to invoice number "UR0008", the reception unit 102a registers the following information as sales data 106b in the storage unit 106: invoice number "UR0008", information about the billing recipient (billing recipient code "0001", billing recipient name "Sakaguchi-sama"), sales date "2024 / 8 / 3", sales amount (base sales amount "300"), consumption tax amount "30", initial collection date "2024 / 9 / 30", scheduled collection date "2024 / 9 / 30", and collection method "bank transfer".

[0080] For example, with respect to invoice number "UR0009", the reception unit 102a registers the following information as sales data 106b in the storage unit 106: invoice number "UR0009", information about the billing recipient (billing recipient code "0001", billing recipient name "Mr. Sakaguchi"), sales date "2024 / 8 / 3", sales amount (base sales amount "200"), consumption tax amount "20", initial collection date "2024 / 9 / 30", scheduled collection date "2024 / 9 / 30", and collection method "bank transfer".

[0081] Here, the reception unit 102a displays an unbilled list inquiry screen, as shown in Figure 8, for sales data 106b for which no billing number has been registered. For example, on the unbilled list inquiry screen, the reception unit 102a displays the billing code, the closing date "31", the billing summary category "1: Target", and the number of days elapsed since collection.

[0082] For example, the reception unit 102a calculates the sales amounts for the initial collection date "2024 / 8 / 31" and "200" for the customer with billing code "0001" and billing name "Sakaguchi-sama," summing them up. The sales amounts for the initial collection date "2024 / 9 / 30" are "300" and "200," and this sum of "2,000" is used as the aggregate sales amount for the customer. The unbilled list inquiry screen then displays the customer with billing code "0001," billing name "Sakaguchi-sama," the aggregate sales amount for the customer (expected billing amount "2,000"), and the billing base amount "2,000." For example, suppose a user uses the input device 112 to click on the row for customer with billing code "0001" and billing name "Sakaguchi-sama" on the unbilled list inquiry screen. At this time, the reception unit 102a displays the sales amounts of "1,000" and "500" for the initial collection date "2024 / 8 / 31", the sales amounts of "300" and "200" for the initial collection date "2024 / 9 / 30", the latest collection date "2024 / 9 / 30", and the number of days elapsed on the unbilled list inquiry screen.

[0083] Next, the reception unit 102a displays a billing closing processing screen as shown in Figure 9, for example, if the closing date in the billing master 106a is "31" and the date is "2024 / 8 / 31". For example, on the billing closing processing screen, the reception unit 102a displays the billing closing date "2024 / 8 / 31", the closing date "31", and the display button "Register". For example, suppose the user presses the display button "Register Set" on the billing closing processing screen using the input device 112.

[0084] As shown in Figure 8, in the billing data extraction process (step S102), the creation unit 102b extracts the sales data to be billed based on the billing master 106a and the sales data 106b. Specifically, the creation unit 102b retrieves from the storage unit 106 the sales data 106b whose sales date is within the billing closing date "2024 / 8 / 31" based on the billing master 106a and the sales data 106b. For example, the creation unit 102b retrieves from the storage unit 106 the sales data 106b containing invoice numbers "UR0001", "UR0002", "UR0007" to "UR0013" as sales data 106b whose sales date is within the billing closing date "2024 / 8 / 31" based on the billing master 106a and the sales data 106b.

[0085] As shown in Figure 8, in the billing data work creation process (step S103), the creation unit 102b creates a billing data work 106c that associates information about the customer (customer code, customer name), the aggregated sales amount of the customer, and the billing basis amount, based on the customer master 106a, sales data 106b, and the comparison result between the aggregated sales amount of the customer from the extracted sales data and the billing basis amount.

[0086] For example, the creation unit 102b sums the sales amounts "1,000", "500", "300", and "200" for the customer with the customer code "0001" and customer name "Sakaguchi-sama", and uses the sum "2,000" as the aggregated sales amount for the customer. The creation unit 102b then assigns "KEQ0004" as a temporary invoice number and creates an invoice data worksheet 106c that associates the temporary invoice number "KEQ0004", customer information (customer code "0001", customer name "Sakaguchi-sama"), the aggregated sales amount for the customer, the purchase amount "2,000", the consumption tax amount "200", the invoiced amount "2,200", and the invoice base amount "2,000".

[0087] For example, the creation unit 102b calculates the sales amount of "1,000" and "1,000" for the customer with the customer code "0002" and customer name "Mr. / Ms. Miyazaki," and uses this total of "2,000" as the aggregated sales amount for the customer. The creation unit 102b then assigns the temporary invoice number "KEQ0005" and creates an invoice data worksheet 106c that associates the temporary invoice number "KEQ0005," customer information (customer code "0002," customer name "Mr. / Ms. Miyazaki"), the aggregated sales amount for the customer (this purchase amount "2,000"), the consumption tax amount "200," the invoiced amount "2,200," and the invoice base amount "2,000."

[0088] For example, the creation unit 102b adds up the sales amounts of "300" and "200" for the customer with the customer code "0003" and customer name "Mr. Tahara," and uses the sum "500" as the aggregated sales amount for the customer. The creation unit 102b then assigns "KEQ0006" as a temporary invoice number and creates an invoice data worksheet 106c that associates the temporary invoice number "KEQ0006," customer information (customer code "0003," customer name "Mr. Tahara"), the aggregated sales amount for the customer, the purchase amount "500," the consumption tax amount "50," the invoice amount "550," and the invoice base amount "0."

[0089] Next, as shown in Figure 10, in the sales data temporary invoice number update process (step S104), the creation unit 102b registers the temporary invoice number in the extracted sales data and updates the sales data 106b.

[0090] For example, the creation unit 102b, based on sales data 106b which includes invoice numbers "UR0001", "UR0002", "UR0008", "UR0009", billing code "0001", and billing name "Sakaguchi", and invoice data work 106c which also includes billing code "0001" and billing name "Sakaguchi", registers the temporary invoice number "KEQ0004" in the invoice data work 106c, associating it with the invoice numbers "UR0001", "UR0002", "UR0008", and "UR0009" in the sales data 106b, and updates the sales data 106b.

[0091] For example, the creation unit 102b, based on sales data 106b which includes invoice numbers "UR0010" and "UR0011", billing code "0002", and billing name "Mr. Miyazaki", and billing data work 106c which also includes billing code "0002" and billing name "Mr. Miyazaki", registers the temporary invoice number "KEQ0005" in the billing data work 106c, associating it with the invoice numbers "UR0010" and "UR0011" in the sales data 106b, and updates the sales data 106b.

[0092] For example, the creation unit 102b, based on sales data 106b which includes invoice numbers "UR0012" and "UR0013", billing code "0003", and billing name "Mr. Tahara", and billing data work 106c which includes billing code "0003" and billing name "Mr. Tahara", registers the temporary billing number "KEQ0006" for the billing data work 106c, associating it with the invoice numbers "UR0012" and "UR0013" in the sales data 106b, and updates the sales data 106b.

[0093] Next, as shown in Figure 10, in the billing data work current billing flag update process (step S105), the creation unit 102b registers a current billing flag for the billing data work 106c, indicating whether or not to bill the recipient this time, and updates the billing data work 106c.

[0094] For example, in billing data work 106c, the billing code "0001" and billing name "Sakaguchi-sama" indicate that the billing aggregation category "1: Target" in billing master 106a is a target for consolidated billing, and the aggregated sales amount of the billing recipient (current purchase amount "2,000") is equal to or greater than the billing base amount "2,000". In this case, the creation unit 102b associates the billing code "0001" and billing name "Sakaguchi-sama" in billing data work 106c with the current billing flag "1: Billing Included", indicating that the billing recipient will be billed this time, and updates the billing data work 106c. In other words, the creation unit 102b created a billing data work 106c that associates information about the billing recipient (billing recipient code "0001", billing recipient name "Mr. Sakaguchi"), the total sales amount of the billing recipient (this time's purchase amount "2,000"), the consumption tax amount "200", the billing amount "2,200", the billing base amount "2,000", and the current billing flag "1: billing issued" which indicates that the billing recipient will be billed this time.

[0095] For example, for the billing address code "0002" and billing address name "Miyazaki-sama" in billing data work 106c, the billing aggregation category "1: Target" in billing address master 106a indicates that the billing address is subject to a combined billing, and the aggregated sales amount of the billing address (current purchase amount "2,000") is equal to or greater than the billing base amount "2,000". In this case, the creation unit 102b associates the billing address code "0002" and billing address name "Miyazaki-sama" in billing data work 106c with the current billing flag "1: Billing Included", indicating that the billing address will be billed this time, and updates the billing data work 106c. In other words, the creation unit 102b created a billing data work 106c that associates information about the billing recipient (billing recipient code "0002", billing recipient name "Mr. / Ms. Miyazaki"), the total sales amount of the billing recipient (this time purchase amount "2,000"), the consumption tax amount "200", the billing amount "2,200", the billing base amount "2,000", and the current billing flag "1: billing issued" which indicates that the billing recipient will be billed this time.

[0096] For example, regarding the customer code "0003" and customer name "Mr. Tahara" in the billing data work 106c, the billing aggregation classification "0: Not applicable" in the customer master 106a indicates that the customer is not subject to consolidated billing. In this case, the creation unit 102b associates the customer code "0003" and customer name "Mr. Tahara" in the billing data work 106c with the current billing flag "1: Billing Included", indicating that the customer will be billed this time, and updates the billing data work 106c. In other words, the creation unit 102b has created a billing data work 106c that associates customer information (customer code "0003", customer name "Mr. Tahara"), the total sales amount of the customer (current purchase amount "500"), the consumption tax amount "50", the billing amount "550", the billing base amount "0", and the current billing flag "1: Billing Included", indicating that the customer will be billed this time.

[0097] Next, as shown in Figure 10, in the billing data creation process (step S106), the creation unit 102b creates billing data 106d based on the updated billing data work 106c.

[0098] For example, as described above, in the billing data work current billing flag update process (step S105), the creation unit 102b creates billing data work 106c that associates information about the billing recipient (billing recipient code "0001", billing recipient name "Sakaguchi-sama"), the aggregated sales amount of the billing recipient (current purchase amount "2,000"), the consumption tax amount "200", the billing amount "2,200", the billing base amount "2,000", and the current billing flag "1: billing available" which indicates that the billing recipient will be billed this time. In this case, in the billing data creation process (step S106), the creation unit 102b creates billing data 106d based on the billing data work 106c, to bill the billing recipient with the aggregated sales amount of the billing recipient (current purchase amount "2,000") on the scheduled collection date "2024 / 9 / 30". Specifically, the creation unit 102b assigns "SEQ0003" as the invoice number and creates invoice data 106d that associates the following information: information about the customer (customer code "0001", customer name "Mr. Sakaguchi"), invoice number "SEQ0003", total sales amount for the customer (total purchase amount "2,000"), consumption tax amount "200", and total invoice amount "2,200".

[0099] For example, as described above, in the billing data work current billing flag update process (step S105), the creation unit 102b creates billing data work 106c that associates information about the billing recipient (billing recipient code "0002", billing recipient name "Miyazaki-sama"), the aggregated sales amount of the billing recipient (current purchase amount "2,000"), the consumption tax amount "200", the billing amount "2,200", the billing base amount "2,000", and the current billing flag "1: billing available" which indicates that the billing recipient will be billed this time. In this case, in the billing data creation process (step S106), the creation unit 102b creates billing data 106d based on the billing data work 106c, to bill the billing recipient with the aggregated sales amount of the billing recipient (current purchase amount "2,000") on the scheduled collection date "2024 / 9 / 30". Specifically, the creation unit 102b assigns "SEQ0004" as the invoice number and creates invoice data 106d that associates the following information: information about the customer (customer code "0002", customer name "Mr. / Ms. Miyazaki"), invoice number "SEQ0004", total sales amount for the customer (total purchase amount "2,000"), consumption tax amount "200", and total invoice amount "2,200".

[0100] For example, as described above, in the billing data work current billing flag update process (step S105), the creation unit 102b creates billing data work 106c that associates information about the billing recipient (billing recipient code "0003", billing recipient name "Mr. Tahara"), the aggregated sales amount of the billing recipient (current purchase amount "500"), the consumption tax amount "50", the billing amount "550", the billing base amount "0", and the current billing flag "1: billing available" which indicates that the billing recipient will be billed this time. In this case, in the billing data creation process (step S106), the creation unit 102b creates billing data 106d based on the billing data work 106c, to bill the billing recipient with the aggregated sales amount of the billing recipient (current purchase amount "500") on the scheduled collection date "2024 / 9 / 30". Specifically, the creation unit 102b assigns "SEQ0005" as the invoice number and creates invoice data 106d that associates the following information: customer information (customer code "0003", customer name "Mr. Tahara"), invoice number "SEQ0005", total sales amount for the customer (purchase amount "500"), consumption tax amount "50", and total invoice amount "550".

[0101] Next, as shown in Figure 11, in the sales data invoice number update process (step S107), the creation unit 102b updates the sales data 106b based on the created invoice data 106d.

[0102] For example, based on sales data 106b which includes invoice numbers "UR0001", "UR0002", "UR0008", "UR0009", billing code "0001", and billing name "Sakaguchi", and billing data 106d which includes billing code "0001" and billing name "Sakaguchi", the creation unit 102b registers the billing number "SEQ0003" from billing data 106d in place of the temporary billing number "KEQ0004" which was registered in association with the invoice numbers "UR0001", "UR0002", "UR0008", and "UR0009" in sales data 106b, and updates the sales data 106b.

[0103] For example, based on sales data 106b which includes invoice numbers "UR0010" and "UR0011", billing code "0002", and billing name "Mr. Miyazaki", and billing data 106d which includes billing code "0002" and billing name "Mr. Miyazaki", the creation unit 102b registers the billing number "SEQ0004" from billing data 106d in place of the temporary billing number "KEQ0005" which was registered in association with the invoice numbers "UR0010" and "UR0011" in sales data 106b, and updates sales data 106b.

[0104] For example, based on sales data 106b which includes invoice numbers "UR0012" and "UR0013", billing code "0003", and billing name "Mr. Tahara", and billing data 106d which includes billing code "0003" and billing name "Mr. Tahara", the creation unit 102b registers the billing number "SEQ0005" from billing data 106d in place of the temporary billing number "KEQ0006" which was registered in association with the invoice numbers "UR0012" and "UR0013" in sales data 106b, and updates sales data 106b.

[0105] As described above, according to this embodiment, sales data 106d is created by adjusting the timing of billing the aggregated sales amount (current purchase amount) of the billing recipient to the billing recipient, based on sales data 106b which associates information about the billing recipient (billing recipient code, billing recipient name), sales date, sales amount (sales amount), scheduled collection date, and collection method, and billing recipient master 106a which associates information about the billing recipient, billing base amount, billing aggregation classification indicating whether or not the billing recipient is subject to consolidated billing, and information about the collection of the billing amount (closing date, collection method, scheduled collection month, scheduled collection date). This allows for consolidated billing to customers (business partners) with a low risk of non-payment. For this reason, according to this embodiment, for example, when small transactions continue in a recurring subscription or contract service, the number of billing items can be consolidated, improving operational efficiency. Furthermore, according to this embodiment, for example, when billing is done with bank transfer as the payment condition, bank transfer fees can be reduced, contributing to profits. Thus, according to this embodiment, fees can be reduced, profits can be increased, and operational efficiency can be improved.

[0106] [4. Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This embodiment can contribute to improving operational efficiency and promoting appropriate management decisions by companies, thereby contributing to SDGs Goals 8 and 9.

[0107] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and digital processes, thereby contributing to SDGs Goals 12, 13, and 15.

[0108] Furthermore, this embodiment can contribute to strengthening control and governance, thereby enabling contributions to SDG Goal 16.

[0109] [5. Other Embodiments] In addition to the embodiments described above, the present invention may be implemented in various different embodiments within the scope of the technical idea described in the claims.

[0110] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically by known methods.

[0111] Furthermore, the processing procedures, control procedures, specific names, information including parameters such as registration data and search conditions for each process, screen examples, and database configuration shown in this specification and in the drawings may be changed at will unless otherwise specified.

[0112] Furthermore, with respect to the billing management device 100, each component shown in the illustration is a functional concept and does not necessarily need to be physically configured as shown.

[0113] For example, the processing functions of the billing management device 100, particularly those performed in the control unit, may be implemented in whole or in part by a CPU and a program interpreted and executed by the CPU, or they may be implemented as wired logic hardware. The program is recorded on a non-temporary computer-readable recording medium containing programmed instructions for the information processing device to execute the processing described in this embodiment, and is mechanically read by the billing management device 100 as needed. That is, a storage unit such as ROM or HDD (Hard Disk Drive) records a computer program that works in cooperation with the OS to give instructions to the CPU and perform various processing tasks. This computer program is executed by being loaded into RAM and works in cooperation with the CPU to constitute the control unit.

[0114] Furthermore, this computer program may be stored on an application program server connected to the billing management device 100 via any network, and it is possible to download all or part of it as needed.

[0115] Furthermore, the program for executing the processing described in this embodiment may be stored on a non-temporary computer-readable recording medium, or it may be configured as a program product. Here, "recording medium" includes any "portable physical medium" such as memory cards, USB (Universal Serial Bus) memory, SD (Secure Digital) cards, flexible disks, magneto-optical disks, ROMs, EPROMs (Erasable Programmable Read Only Memory), EEPROMs (Registered Trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROMs (Compact Disk Read Only Memory), MOs (Magneto-Optical disks), DVDs (Digital Versatile Disks), and Blu-ray (Registered Trademark) Discs.

[0116] Furthermore, "program" refers to a data processing method described in any language or writing method, regardless of its format, such as source code or binary code. Note that "program" is not necessarily limited to a single, monolithic structure; it also includes distributed structures consisting of multiple modules or libraries, and those that work in cooperation with other programs, such as an operating system, to achieve their functions. Regarding the specific configuration and reading procedures for reading the recording medium in each device shown in the embodiments, as well as the installation procedures after reading, well-known configurations and procedures can be used.

[0117] The various databases stored in the memory unit are storage means such as RAM, ROM, other memory devices, hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and website provision.

[0118] Furthermore, the billing management device 100 may be configured as a known personal computer or workstation or other information processing device, or as an information processing device to which any peripheral devices are connected. Alternatively, the billing management device 100 may be implemented by installing software (including programs or data, etc.) that enables the processing described in this embodiment on the device.

[0119] Furthermore, the specific forms of distribution and integration of the devices are not limited to those shown in the figures, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit according to various additions or functional loads. In other words, the embodiments described above may be implemented in any combination, or the embodiments may be implemented selectively. [Industrial applicability]

[0120] This invention is useful in industries that provide services on a regular contract basis in B2C and B2B businesses. [Explanation of symbols]

[0121] 100 Billing management device 102 Control Unit 102a Reception Desk 102b Creation Department 104 Communication Interface Section 106 Storage section 106a Billing Master 106b Sales Data 106c Billing Data Work 106d Billing Data 108 Input / Output Interface Section 112 Input device 114 Output device 200 servers 300 Networks

Claims

1. A billing management device equipped with a control unit, The control unit, The reception department registers sales data that associates information about the billing recipient, the sales date, the sales amount, the scheduled collection date, and the collection method. A creation unit creates billing data that adjusts the timing of billing the aggregated sales amount of the aforementioned billing recipient to the aforementioned billing recipient, based on a billing recipient master that associates information about the aforementioned billing recipient, a billing base amount, a billing aggregation classification indicating whether or not the aforementioned billing recipient is subject to collective billing, and information regarding the collection of the billing amount, and the aforementioned sales data. A billing management device characterized by comprising the following features.

2. The aforementioned creation unit, The billing data is created based on the aforementioned billing master, the sales data, and the comparison result between the aggregated sales amount of the aforementioned billing entity and the billing base amount. A bill management device according to claim 1, characterized by the following:

3. The aforementioned creation unit, Based on the aforementioned customer master, the sales data, and the comparison result between the aggregated sales amount of the customer and the billing base amount, a billing data work is created that associates information about the customer, the aggregated sales amount of the customer, the billing base amount, and a billing flag indicating whether or not to bill the customer this time. Based on the aforementioned billing data work, create the aforementioned billing data. A billing management device according to claim 2, characterized by the following:

4. The aforementioned creation unit, If the billing aggregation category in the billing recipient master indicates that the billing recipient is subject to a consolidated billing, and the aggregated sales amount of the billing recipient is equal to or greater than the billing threshold amount, then a billing data work is created that associates the billing recipient information, the aggregated sales amount of the billing recipient, the billing threshold amount, and the current billing flag indicating that the billing recipient is to be billed this time. Based on the aforementioned billing data work, billing data is created to bill the aforementioned customer for the aggregated sales amount on the scheduled collection date. A bill management device according to claim 3, characterized by the following:

5. The aforementioned creation unit, If the billing aggregation category in the billing recipient master indicates that the billing recipient is subject to consolidated billing, and the aggregated sales amount of the billing recipient falls below the billing threshold amount, then a billing data work is created that associates the billing recipient information, the aggregated sales amount of the billing recipient, the billing threshold amount, and the current billing flag indicating that the billing recipient will not be billed this time. Based on the aforementioned billing master and the aforementioned billing data work, the scheduled collection date is changed to the next scheduled collection date, and the sales data is updated. A bill management device according to claim 4, characterized by the following:

6. The aforementioned creation unit, If the billing aggregation classification in the billing recipient master indicates that the billing recipient is not subject to consolidated billing, then a billing data work is created that associates the billing recipient's information, the aggregated sales amount of the billing recipient, the billing base amount, and the current billing flag indicating that the billing recipient will be billed this time. Based on the aforementioned billing data work, billing data is created to bill the aforementioned customer for the aggregated sales amount on the scheduled collection date. A claim management device according to claim 4 or 5, characterized by the following:

7. A billing management method to be executed by a billing management device equipped with a control unit, In the control unit, A reception step registers sales data that associates information about the billing party, the sales date, the sales amount, the scheduled collection date, and the collection method. A creation step to create billing data that adjusts the timing of billing the aggregated sales amount of the aforementioned billing recipient to the aforementioned billing recipient, based on a billing recipient master that associates information about the aforementioned billing recipient, a billing base amount, a billing aggregation classification indicating whether or not the aforementioned billing recipient is subject to collective billing, and information regarding the collection of the billing amount, and the aforementioned sales data, A billing management method characterized by including the following.

8. A billing management program to be executed by a billing management device equipped with a control unit, In the control unit, A reception step registers sales data that associates information about the billing party, the sales date, the sales amount, the scheduled collection date, and the collection method. A creation step to create billing data that adjusts the timing of billing the aggregated sales amount of the aforementioned billing recipient to the aforementioned billing recipient, based on a billing recipient master that associates information about the aforementioned billing recipient, a billing base amount, a billing aggregation classification indicating whether or not the aforementioned billing recipient is subject to collective billing, and information regarding the collection of the billing amount, and the aforementioned sales data, A billing management program characterized by its ability to execute certain actions.

Images