Business support device, business support method, and business support program

Abstract

To facilitate payment management when there is a deviation in the timing of payment and collection of a billed amount.SOLUTION: A data generation section generates collection schedule data by denomination (hereinafter referred to as data), including a collection scheduled date of a billed amount billed to a customer and a denomination used for payment of the billed amount. A detection section refers to a storage section in which a period from the collection scheduled date and a collection date required until collection of the billed amount are set for each billed amount and each denomination on the basis of the billed amount of the data, and detects the period from the collection scheduled date, the collection date, and the denomination corresponding to the billed amount of the data. A calculation section adds the detected period to the collection scheduled date, calculates a month corresponding to the period from the collection scheduled date required until the collection of the billed amount, and calculates the collection date in the calculated month as the collection date of the billed amount. An update processing section performs update processing of the collection scheduled date of the data on the calculated collection date of the month, and performs update processing of the denomination of the data on the denomination detected by the detection section.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a business support device, a business support method, and a business support program. [Background technology]

[0002] Patent document 1 (JP 2020-155048 A) discloses a business support device that allows the billing closing date to be changed in response to a request from the billing recipient, and that makes it possible to issue an invoice on the changed billing closing date when permission to issue the invoice is granted by the billing recipient.

[0003] This business support device changes the billing closing date for billing data associated with an operator-specified billing recipient for whom issuance of an invoice is not permitted, changes the scheduled collection date for scheduled collection data associated with this billing data, and creates invoice data based on billing data associated with an operator-specified billing recipient for whom issuance of an invoice is permitted and for which the billing closing date corresponds to a specified year and month. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Publication No. 2020-155048 Summary of the Invention [Problem to be solved by the invention]

[0005] Here, there may be a discrepancy between the timing when the business partner makes the payment corresponding to the invoice and the timing when the company that made the invoice plans to collect the invoice amount, making it difficult for accounting staff to manage the payment.

[0006] The present invention has been made in consideration of the above-mentioned problems, and aims to provide a business support device, a business support method, and a business support program that can simplify deposit management even when there is a discrepancy between the timing of depositing the invoice amount and the timing of collecting it. [Means for solving the problem]

[0007] In order to solve the above-mentioned problems and achieve the object, the business support device of the present invention has a data generation unit that generates denomination-specific collection schedule data including the scheduled collection date of the invoice amount to be invoiced to a business partner and the denomination to be used for paying the invoice amount; a detection unit that references a memory unit in which the period from the scheduled collection date and collection date required to collect the invoice amount for each invoice amount and denomination are set, based on the invoice amount in the denomination-specific collection schedule data, and detects the period from the scheduled collection date, collection date, and denomination corresponding to the invoice amount in the denomination-specific collection schedule data; a calculation unit that adds the period detected by the detection unit to the scheduled collection date to calculate the month corresponding to the period from the scheduled collection date required to collect the invoice amount, and calculates the collection date in the calculated month as the collection date of the invoice amount; and an update processing unit that updates the scheduled collection date of the denomination-specific collection schedule data to the collection date of the calculated month, and updates the denomination of the denomination-specific collection schedule data to the denomination detected by the detection unit.

[0008] In addition, in order to solve the above-mentioned problems and achieve the object, the business support method of the present invention includes: a data generation step in which a data generation unit generates denomination-specific collection schedule data including a scheduled collection date for the invoice amount to be invoiced from the business partner and the denomination to be used for paying the invoice amount; a detection step in which a detection unit references a memory unit in which the period from the scheduled collection date and the collection date required to collect the invoice amount are set for each invoice amount and each denomination, based on the invoice amount in the denomination-specific collection schedule data, and detects the period from the scheduled collection date, collection date, and denomination that correspond to the invoice amount in the denomination-specific collection schedule data; a calculation step in which a calculation unit adds the period detected in the detection step to the scheduled collection date to calculate the month corresponding to the period from the scheduled collection date required to collect the invoice amount, and calculates the collection date in the calculated month as the collection date for the invoice amount; and an update processing step in which an update processing unit updates the scheduled collection date in the denomination-specific collection schedule data to the collection date of the calculated month, and updates the denomination of the denomination-specific collection schedule data to the denomination detected in the detection step.

[0009] In addition, in order to solve the above-mentioned problems and achieve the object, the business support program of the present invention causes a computer to function as: a data generation unit that generates denomination-specific collection schedule data including the scheduled collection date of the invoice amount to be invoiced from the business partner and the denomination to be used for paying the invoice amount; a detection unit that references a memory unit in which the period from the scheduled collection date and collection date required to collect the invoice amount for each invoice amount and denomination are set, based on the invoice amount in the denomination-specific collection schedule data, and detects the period from the scheduled collection date, collection date, and denomination corresponding to the invoice amount in the denomination-specific collection schedule data; a calculation unit that adds the period detected by the detection unit to the scheduled collection date to calculate the month corresponding to the period from the scheduled collection date required to collect the invoice amount, and calculates the collection date in the calculated month as the collection date of the invoice amount; and an update processing unit that updates the scheduled collection date of the denomination-specific collection schedule data to the collection date of the calculated month, and updates the denomination of the denomination-specific collection schedule data to the denomination detected by the detection unit. [Effects of the Invention]

[0010] The present invention can facilitate payment management even when there is a discrepancy between the timing of payment and the timing of collection of the invoice amount, thereby supporting accounting work by accountants and the like. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a block diagram illustrating a hardware configuration of a task assistance device according to an embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of a basic information management master table provided in the task support device according to the embodiment. [Figure 3] FIG. 3 is a diagram illustrating an example of a billing destination master table provided in the business support device according to the embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of a collection condition master table provided in the business support device according to the embodiment. [Figure 5] FIG. 5 is a diagram illustrating an example of a target data setting master table provided in the task assistance device according to the embodiment. [Figure 6] FIG. 6 is a diagram illustrating an example of a denomination-specific collection schedule data storage unit provided in the business support device according to the embodiment. [Figure 7] FIG. 7 is a diagram illustrating an example of a billing data storage unit provided in the business support device according to the embodiment. [Figure 8] FIG. 8 is a diagram illustrating an example of a collection schedule data storage unit provided in the business support device according to the embodiment. [Figure 9] Figure 9 is a diagram showing the types of data and extraction conditions acquired when updating the scheduled collection date and denomination (collection method) of scheduled collection data for each scheduled collection denomination based on the scheduled collection amount and denomination (collection method) in an embodiment of a business support device. [Figure 10] FIG. 10 is a diagram showing a specific example of the process of updating the denomination (collection method) and the scheduled collection date based on the scheduled collection amount in the business support device according to the embodiment. [Figure 11]FIG. 11 is a diagram showing how the denomination (collection method) and the scheduled collection date of the denomination-specific collection schedule data are updated based on the scheduled collection amount in the business support device according to the embodiment. [Figure 12] FIG. 12 is a diagram showing an example of calculation of the payment due date to be added to the denomination-specific collection schedule data when the denomination (collection method) is "bill" in the business support device according to the embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0012] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS A task support device according to an embodiment of the present invention will be described in detail below with reference to the accompanying drawings. However, the present invention is not limited to the following embodiment.

[0013] (overview) Typically, there are two patterns for billing and payment: one where a bill is made for each sale and payment is made for that bill, and one where a lump-sum bill is made once a month for all sales for the month and payment is made for that bill.

[0014] Here, a "per-use billing" system is known, where a company's equipment is billed on a per-project basis, rather than once a month. The client pays the monthly invoice amount set by the client in a lump sum for this per-use billing. This can cause problems for accounting staff, as the expected collection date and collection method set by the biller (the company) on a per-invoice basis do not match the expected payment date and payment method set by the client on a monthly basis. This creates discrepancies in the timing of collection of invoiced amounts, which can cause difficulties in the biller's (the company's) cash flow.

[0015] For this reason, the business support device of the embodiment calculates the total amount of monthly invoices for all business partners (billing destinations), for example, every night, and updates the collection conditions (scheduled collection date, collection method, and payment due date) to the correct ones (updating the collection schedule data by denomination). This makes it possible to simplify collection management and support the accounting work of accountants, even when there is a discrepancy between the timing of depositing the invoice amount and the timing of collection. Furthermore, since the exact timing of collection of the invoice amount can be recognized, cash flow can be managed based on the accurate collection timing.

[0016] (Hardware configuration) As shown in FIG. 1, the business support device 1 of the embodiment includes a storage unit 2, a control unit 3, a communication interface unit 4, and an input / output interface unit 5. An input device 6 and an output device 7 are connected to the input / output interface unit 5. The output device 7 corresponds to a display unit such as a monitor device (including a home television), a printing device, or a speaker device. The input device 6 may be a keyboard device, a mouse device, a microphone device, or a monitor device that cooperates with a mouse device to achieve a pointing device function. The communication interface unit 4 is connected to a network, for example, a wide area network such as the Internet or a private network such as a LAN (Local Area Network).

[0017] The storage unit 2 may be, for example, a read-only memory (ROM), a random access memory (RAM), a hard disk drive (HDD), or a solid state drive (SSD). The storage unit 2 stores a business support program that facilitates deposit management and supports the accounting work of accountants, even when there is a discrepancy between the timing of depositing the invoice amount and the timing of collecting it. The storage unit 2 also includes a basic information management master table 11, a billing destination master table 12, a collection condition master table 13, a target data setting master table 14, a denomination-specific collection schedule data storage unit 15, a billing data storage unit 16, and a collection schedule data storage unit 17, each of which is a storage area.

[0018] As shown in FIG. 2, the basic information management master table 11 stores accounting dates, names of business partners, addresses and telephone numbers of business partners, etc. in association with each other.

[0019] As shown in Figure 3, the billing master table 12 stores the billing code, billing name, billing closing date for each business partner, type of billing for the billing partner, and site period (site number of days or site month and date) for each business partner.

[0020] The example in Figure 3 shows that the billing codes for business partners A to D are "1001," "1002," "1003," and "1004," respectively, and that the closing date is the 31st of each month. The example in Figure 3 also shows that billing to each business partner is done in the billing format (billing category) of "billing on a per-item basis."

[0021] The number of days is the period from the scheduled collection date of the invoice amount to the specified payment due date, and for Client A, it is the date 100 days after the scheduled collection date, and for Client B, it is the date 120 days after the scheduled collection date. Also, for Client C, it is the 10th of the month two months after the scheduled collection date (for example, June 10th, August 10th, etc.).

[0022] As shown in FIG. 4, the collection condition master table 13 stores the collection method (denomination), collection month, and collection date for each planned collection amount (each base amount) of each customer.

[0023] Specifically, if the amount to be collected from Customer A, whose billing code is "1001," is less than 100,000 yen, the collection method (denomination) will be "transfer," and the collection month and date will be "the 31st of the month one month from now." Similarly, if the amount to be collected from Customer A, whose billing code is "1001," is between 100,000 yen and 200,000 yen, the collection method (denomination) will be "bill," and the collection month and date will be "the 31st of the month two months from now." Similarly, if the amount to be collected from Customer A, whose billing code is "1001," is 200,000 yen or more, the collection method (denomination) will be "cash," and the collection month and date will be "the 31st of the month three months from now."

[0024] Furthermore, if the amount to be collected from Customer B, whose billing code is "1002," is less than 100,000 yen, the collection method (denomination) will be "transfer," and the collection month and collection date will be "the 31st of the month one month from now." Similarly, if the amount to be collected from Customer B, whose billing code is "1001," is between 100,000 yen and 200,000 yen, the collection method (denomination) will be "bill," and the collection month and collection date will be "the 31st of the month two months from now." Similarly, if the amount to be collected from Customer B, whose billing code is "1001," is 200,000 yen or more, the collection method (denomination) will be "cash," and the collection month and collection date will be "the 31st of the month three months from now."

[0025] In this way, the collection method (denomination), collection month, and collection date corresponding to the planned collection amount of each customer are set in the collection condition master table 13. This collection condition master table 13 is referenced based on the planned collection amount to be billed to the customer when updating the planned collection data by denomination, which will be described later. Then, the collection method, collection month, and collection date of the planned collection data by denomination are updated (replaced) to the collection method, collection month, and collection date corresponding to the planned collection amount of the customer.

[0026] The accounting month for which the above-mentioned update process is to be performed is set in the target data setting master table 14, as shown in Fig. 5. When the above-mentioned update process is to be performed on the accounting data for the current month, "0" is set in the target data setting master table 14, and when the above-mentioned update process is to be performed on the accounting data for the next month, "1" is set.

[0027] Next, the data generating unit 21 generates collection schedule data by denomination for each customer as shown in FIG. 6 based on the input operation of the accounting staff or the like, and stores the data in the collection schedule data storage unit 15 by denomination. In this denomination-specific collection schedule data storage unit 15, the billing number, scheduled collection date, payment method (denomination), update target category, and payment due date are stored in association with each billing code of each customer, as shown in Figure 6. The billing number is a unique sequential number assigned to each customer.

[0028] The expected collection date is the date when the expected collection amount is expected to be collected; in the example of Figure 6, it is "the 31st" for each business partner. The payment method is the denomination used to pay the expected collection amount; in the example of Figure 6, it is "check" for each business partner. The update target category is information that indicates whether the business partner is a business partner for which the above-mentioned update process is to be performed. If the business partner is a business partner that is subject to the update process, "0" is set as the update target category, and if the business partner is a business partner that is not subject to the update process, "1" is set as the update target category.

[0029] The example in Figure 6 shows that the update target category of "1" is set for business partner D, whose billing code is "1004," and the above-mentioned update process will not be performed on the scheduled collection data by denomination for business partner D. Note that the update target category of "0" is set for business partners A to C, whose billing codes are "1001" to "1003," and the update process will be performed on the scheduled collection data by denomination for business partners A to C, as described below.

[0030] Next, the data generation unit 21 generates billing data as shown in FIG. 7 based on input operations by an accounting staff member or the like, and stores the data in the billing data storage unit 16. As shown in FIG. 7, the billing data storage unit 16 stores billing numbers, billing closing dates, and advance payment categories associated with billing destination codes for each business partner. The billing closing date is the closing date of the company on the business support device 1 side that calculated the billing amount (planned collection amount) to be billed to the business partner this time. In the example of FIG. 6, the closing date is set to "March 10, 2023."

[0031] The advance payment type is information that indicates whether the business partner will pay the invoice amount using the "advance payment" payment method, or the "regular" payment method, where payment is made after the invoice. The advance payment type is set to "1: advance payment" for business partners using the "advance payment" payment method, and "0: regular" for business partners using the "regular" payment method. In the example of Figure 7, the payment type "0: regular" is set for each business partner.

[0032] Next, the data generation unit 21 generates the collection schedule data shown in FIG. 8 based on input operations by the accounting staff or the like, and stores the data in the collection schedule data storage unit 17. As shown in FIG. 8, the collection schedule data storage unit 17 stores the planned collection amount, the reconciled payment amount, and the reconciliation completion classification in association with the billing code and billing number of each business partner. The example in FIG. 8 shows the amount planned to be collected from each business partner for the accounting year and month (March 2023) of the basic information management master table shown in FIG. 2. Specifically, the amount planned to be collected from business partner A with a billing code of "1001" is "99,999 yen." The amount planned to be collected from business partner B with a billing code of "1002" is "100,000 yen." The amount planned to be collected from business partner C with a billing code of "1003" is "199,999 yen."

[0033] The amount of payment that has been applied is the amount of the amount to be collected that has been paid and applied. In the example of Figure 8, the amount of the amount to be collected that has been paid and applied is "0 yen (no payment or application)" for each business partner.

[0034] The payment reconciliation completion category is information that indicates whether the payment and reconciliation of the amount to be collected have been completed (1: payment reconciliation completed, 0: payment reconciliation not completed). The example in Figure 8 shows that the amount to be collected has not been paid and reconciliation has not been completed for each business partner.

[0035] (Functional configuration of business support device) Next, the control unit 3 executes the business support program stored in the storage unit 2, thereby functioning as a data generation unit 21, a detection unit 22, a calculation unit 23, and an update processing unit 24, as shown in FIG.

[0036] The data generating unit 21 generates denomination-specific collection schedule data including the scheduled collection date of the billed amount (planned collection amount) to be billed to the business partner and the denomination (payment method) to be used for paying the billed amount (see FIG. 6).

[0037] The detection unit 22 refers to the memory unit (collection condition master table 13 in Figure 4) in which the period from the scheduled collection date and collection date required to collect the claim amount for each claim amount and denomination are set based on the claim amount of the denomination-specific collection schedule data, and detects the period from the scheduled collection date, collection date, and denomination that correspond to the claim amount of the denomination-specific collection schedule data.

[0038] The calculation unit 23 calculates the month corresponding to the period from the scheduled collection date required to collect the billed amount by adding the period (collection month in FIG. 4) detected by the detection unit 22 to the scheduled collection date. The calculation unit 23 also calculates the collection date in the calculated month (collection date in FIG. 4) as the collection date of the billed amount.

[0039] The update processing unit 24 updates the scheduled collection date of the denomination-specific collection schedule data to the collection date of the month calculated by the calculation unit 23 (the collection month and collection date in FIG. 4). The update processing unit 24 also updates the denomination of the denomination-specific collection schedule data to the denomination detected by the detection unit 22 (the collection method shown in FIG. 4).

[0040] The storage unit (billing destination master table 12 in FIG. 3) also stores, for each customer, a site period (such as the number of site days in FIG. 3) indicating the period from the scheduled collection date of the billing amount to a specified payment due date. The calculation unit 23 calculates the payment due date of the billing amount by adding the site period corresponding to the customer to the scheduled collection date. The update processing unit 24 adds the calculated payment due date to the updated denomination-specific collection schedule data.

[0041] The calculation unit 23 also calculates an end date, which is the date obtained by adding the billing closing date of the business partner stored in the storage unit (the closing date of the billing partner master table in FIG. 3) to the accounting year and month of the billing amount (the accounting year and month in FIG. 2), and a start date, which is the date obtained by subtracting one month from the end date and then adding one day to the date. The data generation unit 21 generates denomination-specific collection schedule data, which includes the scheduled collection date and denomination corresponding to the period from the start date to the end date (see FIG. 6).

[0042] In addition, the collection schedule data by denomination is added with an update target classification indicating whether or not it is subject to update processing (see FIG. 6). The update processing unit 24 performs update processing on the collection schedule data by denomination to which the update target classification indicating that it is subject to update processing has been added.

[0043] (Update processing operation of collection schedule data by denomination) Next, an update process (refresh process) of the collection schedule data by denomination in the business support device 1 of the embodiment having such a configuration will be described. This update process is executed by the control unit 3 shown in FIG. 1 functioning as the data generation unit 21, the detection unit 22, the calculation unit 23, and the update processing unit 24 based on the business support program stored in the storage unit 2. Note that in this example, the data generation unit 21 to the update processing unit 24 will be described as being realized by software in accordance with the business support program, but some or all of the data generation unit 21 to the update processing unit 24 may also be realized by hardware. In either case, the same effects as those described below can be obtained.

[0044] As an example, the update process is performed every night. At a predetermined time, the calculation unit 23 first refers to the target data setting master table 14 shown in FIG. 5 and determines whether the judgment code is "0" or "1." If the judgment code is "0," the update process for the denomination-specific collection schedule data for the current month is performed, as explained below. If the judgment code is "1," the update process for the denomination-specific collection schedule data for the next month is performed, as explained below.

[0045] Taking the case where the judgment code is "0" as an example, the calculation unit 23 acquires the accounting year and month from the basic information management master table 11 shown in FIG. 2 in order to update the collection schedule data by denomination for the current month. In the example of FIG. 2, the accounting year and month of "March 2023" is acquired. The calculation unit 23 adds the "31st," which is the closing date in the billing destination master table 12 shown in FIG. 3, to the accounting year and month of "March 2023," and sets the result of this addition as the "end date" (year and month of meeting + 31st = end date). The calculation unit 23 also subtracts one month from the calculated end date and adds one day to this subtraction result (starting from the next day), thereby calculating the "start date" (end date - 1 month + 1 day = start date).

[0046] Specifically, since the accounting year and month is "March 2023," if the closing date of the business partner is "the 31st," the calculation unit 23 calculates "March 31, 2023" as the end date by performing the calculation "March 2023 + 31 days." In addition, the calculation unit 23 subtracts one month from the calculated end date, "March 31, 2023," and adds one day to calculate the start date of "March 31, 2023 - 1 month + 1 day = March 1, 2023."

[0047] Next, the detection unit 22 detects, for each business partner, the planned collection data by denomination (see Figure 6), billing data (see Figure 7), and planned collection data (see Figure 8) corresponding to the period from March 1, 2023 to March 31, 2023, which is the period from the start date to the end date calculated by the calculation unit 23.

[0048] Fig. 9 is a diagram showing items, extraction conditions, joining conditions, etc. detected by the detection unit 22. As shown in Fig. 9, the detection unit 22 acquires the billing destination code of the collection schedule data shown in Fig. 8 as the billing code of the business partner.

[0049] To calculate the total invoice amount, the calculation unit 23 first calculates a subtraction amount for each business partner by subtracting the cleared payment amount from the expected collection amount in the collection schedule data shown in Figure 8. The calculation unit 23 then adds the subtraction amounts for the same business partner to calculate the total invoice amount for that business partner. The detection unit 22 acquires (detects) the total invoice amount calculated for each acquisition partner in this way.

[0050] In addition, the detection unit 22 refers to the billing data storage unit 16 shown in Figure 7 to detect (extract) the billing code of each customer, and detects the billing data for the period from March 1, 2023 to March 31, 2023, which is the above-mentioned start date to end date, for each customer.

[0051] Furthermore, the detection unit 22 refers to the billing data storage unit 16 shown in FIG. 7 and detects, for each business partner, billing data in which the advance payment category is set to "0: Normal (no advance payment)."

[0052] Furthermore, the detection unit 22 refers to the collection schedule data storage unit 17 shown in FIG. 8 and acquires, for each business partner, collection schedule data in which the payment clearing completion classification is set to "0: incomplete."

[0053] In addition, the detection unit 22 refers to the denomination-specific collection schedule data storage unit 15 shown in Figure 6 and acquires, for each customer, the denomination-specific collection schedule data for which the update target category (redeemable category) is set to "0: Redeem."

[0054] Furthermore, the detection unit 22 combines and groups the detected billing data, collection schedule data, and denomination-specific collection schedule data with the same billing number.

[0055] Next, based on the billing destination code and total billing amount detected in this manner, the detection unit 22 refers to the collection condition master table 13 shown in Figure 4 and detects the collection method (denomination), collection month and collection date corresponding to the total billing amount for each customer.

[0056] Specifically, as shown in Figure 10, if the total invoice amount for March 2023 to customer A, whose invoice code is "1001," is "99,999 yen," the total invoice amount is "less than 100,000 yen," so the detection unit 22 will detect the collection method of "transfer," the collection month of "one month later," and the collection date of "the 31st" by referring to the collection condition master table 13 shown in Figure 4.

[0057] Similarly, as shown in Figure 10, if the total invoice amount for March 2023 to customer B, whose invoice code is "1002," is "100,000 yen," the total invoice amount is "more than 100,000 yen and less than 200,000 yen," so the detection unit 22 will detect the collection method for the "bill," the collection month of "two months later," and the collection date of "the 30th" by referring to the collection condition master table 13 shown in Figure 4.

[0058] Similarly, as shown in Figure 10, if the total invoice amount for March 2023 to customer C, whose invoice code is "1003," is "199,999 yen," the total invoice amount is "more than 100,000 yen and less than 200,000 yen," so the detection unit 22 will detect the collection method for the "bill," the collection month of "two months later," and the collection date of "the 30th" by referring to the collection condition master table 13 shown in Figure 4.

[0059] Similarly, as shown in Figure 10, if the total invoice amount for March 2023 to customer D, whose invoice code is "1004," is "200,000 yen," the total invoice amount is "more than 200,000 yen," so the detection unit 22 detects the collection method of "cash," the collection month of "3 months later," and the collection date of "the 31st" by referring to the collection condition master table 13 shown in Figure 4.

[0060] When the collection method, collection month, and collection date corresponding to the total invoice amount for each customer are detected in this manner, the update processing unit 24 updates the scheduled collection date and collection method for each customer in the pre-update denomination-specific collection schedule data shown in Figure 11(a) to the scheduled collection date and collection method detected from the collection condition master table 13 shown in Figure 4, as shown in Figure 11(b).

[0061] That is, before the update, the scheduled collection date for business partner A, whose billing code is "1001," was "March 31, 2023," and the collection method was "check." However, as a result of referencing the collection condition master table 13 shown in Figure 4 based on the total amount invoiced to business partner A, the collection method for March 2023 for business partner A, whose billing code is "1001," was detected as "bank transfer," the collection month was detected as "one month later," and the collection date was detected as "the 31st."

[0062] Therefore, the update processing unit 24 updates the scheduled collection date for customer A, whose billing code is "1001," shown in Figure 11(b), to "April 31, 2023," which is the 31st of the month obtained by adding "one month" to "March 31, 2023," the scheduled collection date before the update. The update processing unit 24 also updates the collection method for customer A, whose billing code is "1001," from "check" to "bank transfer."

[0063] Similarly, before the update, the scheduled collection date for business partner B, whose billing code is "1002," was "March 31, 2023," and the collection method was "check." However, as a result of referencing the collection conditions master table 13 shown in Figure 4 based on the total amount invoiced to business partner B, the collection method for March 2023 for business partner B, whose billing code is "1002," was detected as "bill," the collection month was detected as "two months later," and the collection date was detected as "the 30th."

[0064] Therefore, the update processing unit 24 updates the scheduled collection date for customer B, whose billing code is "1002," shown in Figure 11(b), to "May 30, 2023," which is the 30th of the month obtained by adding "two months" to "March 31, 2023," the scheduled collection date before the update. The update processing unit 24 also updates the collection method for customer B, whose billing code is "1002," from "check" to "bill."

[0065] Similarly, before the update, the scheduled collection date for customer C, whose billing code is "1003," was "March 31, 2023," and the collection method was "check." However, as a result of referencing the collection conditions master table 13 shown in Figure 4 based on the total amount invoiced to customer C, the collection method for March 2023 for customer C, whose billing code is "1003," was detected as "bill," the collection month was detected as "two months later," and the collection date was detected as "the 30th."

[0066] Therefore, the update processing unit 24 updates the scheduled collection date of customer C, whose billing code is "1003", shown in Figure 11(b), to "May 30, 2023", which is the "30th" of the month obtained by adding "two months" to "March 31, 2023", the scheduled collection date before the update. In addition, the update processing unit 24 updates the collection method of customer C, whose billing code is "1003", from "check" to "bill".

[0067] Similarly, before the update, the scheduled collection date for business partner D, whose billing code is "1004," was "March 31, 2023," and the collection method was "check." However, as a result of referencing the collection condition master table 13 shown in Figure 4 based on the total amount invoiced to business partner D, the collection method for March 2023 for business partner D, whose billing code is "1004," was detected as "cash," the collection month was detected as "three months later," and the collection date was detected as "the 31st."

[0068] Here, as shown in Figure 11(a), the update target category for customer D, whose billing code is "1004", is set to "1: Do not perform update processing". In this case, the update processing unit 24 does not perform update processing for customer D, whose billing code is "1004". Therefore, in the case of customer D, whose billing code is "1004", the planned collection date is maintained as "March 31, 2023" before the update, and the collection method, "check", before the update, is maintained as the collection method, as shown in Figure 11(b).

[0069] In this way, by setting the desired update target category for the denomination-specific collection schedule data, it is possible to freely adjust which business partners will undergo the update process and which will not.

[0070] Next, in the business support device 1 of the embodiment, when the update process is performed to a predetermined collection method, the calculation unit 23 calculates the payment due date and adds it to the updated collection schedule data by denomination. As an example, an example of calculating the payment due date when the collection method is "bill" will be described.

[0071] In the above example, the update process updated the collection method for customer B, whose billing code is "1002," to "bill." Therefore, the calculation unit 23 references the billing master table 12 shown in FIG. 3 and detects the site period set for customer B. In the example of FIG. 3, a site period of "120 days" is set for customer B. Therefore, as shown in FIG. 12(a), the calculation unit 23 calculates the payment due date of "September 27, 2023" by adding "120 days" to "May 30, 2023," which is the scheduled collection date for customer B after the update process.

[0072] As shown in Figure 11(b), the update processing unit 24 adds the calculated payment due date of "September 27, 2023" to the denomination-specific collection schedule data for customer B (billing code 1002) for which the update processing was performed. This makes it possible to set the desired payment due date for the "bill" collection method.

[0073] Furthermore, in the above example, the update process updated the collection method for customer C, whose billing code is "1003," to "bill." Therefore, the calculation unit 23 references the billing master table 12 shown in FIG. 3 and detects the site period set for customer C. In the example of FIG. 3, the site month is set to "2 months" and the date is set to "10th." Therefore, as shown in FIG. 12(b), the calculation unit 23 calculates the payment due date to be "July 10, 2023," which is the "10th" of the month after "May 30, 2023," the scheduled collection date for customer C after the update process.

[0074] As shown in Figure 11(b), the update processing unit 24 adds the calculated payment due date of "July 10, 2023" to the scheduled collection data by denomination for customer C (billing code 1003) for which the update processing was performed. This makes it possible to set the desired payment due date for the collection method of "bills."

[0075] (Effects of the embodiment) As is clear from the above explanation, the business support device of the embodiment calculates the total monthly billing amount for all business partners (billing destinations), for example, every night, and updates the collection conditions (scheduled collection date, collection method, and payment due date) to the correct ones (updating process of the collection schedule data by denomination).

[0076] This makes it possible to simplify management of receipts even when there is a discrepancy between the timing of receipt and collection of the invoice amount, and to support the accounting work of accountants, etc. Also, since the exact timing of collection of the invoice amount can be recognized, cash flow can be managed based on the accurate collection timing.

[0077] [Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This invention can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby contributing to the achievement of goals "8" and "9" of the SDGs.

[0078] Furthermore, this invention can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of SDGs goals 12, 13, and 15.

[0079] Furthermore, the present invention can contribute to strengthening control and governance, thereby contributing to the achievement of Goal 16 of the SDGs.

[0080] [Other embodiments] The present invention can be implemented in various different forms other than the above-described embodiments within the scope of the technical concept described in the claims.

[0081] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically may be performed manually, or all or part of the processes described as being performed manually may be performed automatically using a known method or the like.

[0082] Furthermore, the processing procedures, control procedures, specific names, registered data for each process, information including parameters such as search conditions, screen examples, and database configurations shown in the specification or drawings may be changed as desired unless otherwise specified.

[0083] Furthermore, the components of the business support device 1 shown in the figure are conceptual functional components and do not necessarily have to have the physical configuration shown in the figure. For example, all or any part of the processing functions of the business support device 1, particularly the processing functions performed by the control unit 3, may be realized by a program interpreted and executed by the control unit 3 (CPU: Central Processing Unit), or may be realized by hardware using wired logic.

[0084] The program is recorded on a non-transitory computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processes described in the embodiments, and is mechanically read by the business support device 1 as needed. That is, a computer program is recorded in the storage unit 2, such as a ROM or HDD, for working with an OS (Operating System) to give instructions to a control unit 3 (CPU) and perform various processes. The computer program is loaded into RAM, expanded, and executed by the control unit 3 as appropriate.

[0085] In addition, the business support program of this business support device 1 may be stored in another server device connected to the business support device 1 via any network, and all or part of it may be downloaded and executed as needed.

[0086] Furthermore, the business support program for executing the processes described in the embodiments may be stored in a non-transitory computer-readable recording medium, or may be configured as a program product.

[0087] Here, the "recording medium" can be any "portable physical medium" such as a memory card, a USB (Universal Serial Bus) memory, an SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), an EEPROM (registered trademark) (Electrically Erasable and Programmable Read Only Memory), a CD-ROM (Compact Disk Read Only Memory), an MO (Magneto-Optical Disk), a DVD (Digital Versatile Disk), and a Blu-ray (registered trademark) Disc.

[0088] Furthermore, a "program" is a data processing method written in any language or description method, regardless of the format, such as source code or binary code.

[0089] It should be noted that a "program" is not necessarily limited to a single structure, but includes a structure that is distributed as multiple modules or libraries, and a structure that achieves its function by working together with other programs, such as an OS.

[0090] Furthermore, the specific configuration for reading the recording medium in the task support device 1 of the embodiment, the reading procedure, and the installation procedure after reading can be any known configuration or procedure.

[0091] The memory unit 2 is a storage means such as a memory device such as RAM or ROM, a fixed disk device such as a hard disk, a flexible disk, or an optical disk, and stores various programs, tables, databases, web page files, etc. used for various processes or providing websites.

[0092] The business support device 1 may be configured as an information processing device such as a known personal computer or a workstation, or may be configured as an information processing device connected to any peripheral device. The information processing device may be implemented with software (including programs or data) that realizes the processes described in the embodiments.

[0093] Furthermore, the specific forms of distribution and integration of the devices are not limited to those shown in the drawings, and all or part of them can be functionally or physically distributed or integrated in any unit depending on various additions or functional loads. In other words, the above-mentioned embodiments can be selectively implemented by combining them in any way. [Industrial Applicability]

[0094] The present invention is suitable for application to deposit management in a variety of industries. [Explanation of symbols]

[0095] 1 Business support equipment 2 Storage section 3. Control Unit 4. Communication interface section 5 Input / output interface section 6 Input Devices 7 Output Devices 11 Basic information management master table 12 Billing Master Table 13 Collection Condition Master Table 14 Target Data Setting Master Table 15. Denomination-specific collection schedule data storage section 16. Billing data storage unit 17. Scheduled collection data storage section 21 Data Generation Unit 22 Detection unit 23 Calculation section 24 Update processing section

Claims

1. a data generating unit that generates denomination-specific collection schedule data including a scheduled collection date for the amount invoiced to the business partner and the denomination to be used for payment of the amount invoiced; a detection unit that refers to a storage unit in which the period from the scheduled collection date and the collection date required to collect the claim amount are set for each claim amount and each denomination, based on the claim amount of the denomination-specific collection schedule data, and detects the period from the scheduled collection date, the collection date, and the denomination that correspond to the claim amount of the denomination-specific collection schedule data; a calculation unit that calculates the month corresponding to the period from the scheduled collection date required to collect the invoice amount by adding the period detected by the detection unit to the scheduled collection date, and calculates the collection date in the calculated month as the collection date for the invoice amount; an update processing unit that updates the scheduled collection date of the denomination-specific collection schedule data to the calculated collection date of the month, and updates the denomination of the denomination-specific collection schedule data to the denomination detected by the detection unit; A business support device having the above.

2. The storage unit stores, for each of the business partners, a site period indicating a period from the scheduled collection date of the invoice amount to a predetermined payment due date, the calculation unit calculates the payment due date of the invoice amount by adding the site period corresponding to the customer to the scheduled collection date; the update processing unit adds the calculated payment due date to the denomination-specific collection schedule data that has been updated; 2. The business support device according to claim 1, wherein:

3. the calculation unit calculates an end date, which is the date obtained by adding the billing closing date of the business partner stored in the storage unit to the accounting year and month of the billing amount, and a start date, which is the date obtained by subtracting one month from the end date and then adding one day to the date obtained by subtracting one month from the end date; the data generation unit generates the denomination-specific collection schedule data including the scheduled collection date and the denomination corresponding to the period from the start date to the end date; 3. The business support device according to claim 2, wherein:

4. The denomination-specific collection schedule data is added with an update target classification indicating whether or not the data is subject to the update process, the update processing unit performs the update process on the denomination-specific collection schedule data to which the update target classification indicating that the data is subject to the update process is added; 4. The business support device according to claim 1, wherein:

5. a data generation step in which a data generation unit generates denomination-specific collection schedule data including a scheduled collection date for the invoice amount to be invoiced to the business partner and the denomination to be used for payment of the invoice amount; a detection step in which a detection unit refers to a storage unit in which the period from the scheduled collection date and the collection date required to collect the claim amount are set for each claim amount and each denomination, based on the claim amount of the denomination-specific collection schedule data, and detects the period from the scheduled collection date, the collection date, and the denomination corresponding to the claim amount of the denomination-specific collection schedule data; a calculation step in which a calculation unit calculates a month corresponding to a period from the scheduled collection date required to collect the invoice amount by adding the period detected in the detection step to the scheduled collection date, and calculates the collection date in the calculated month as the collection date of the invoice amount; an update processing step in which an update processing unit updates the scheduled collection date of the denomination-specific collection schedule data to the calculated collection date of the month, and updates the denomination of the denomination-specific collection schedule data to the denomination detected in the detection step; A business support method having the above.

6. Computer, a data generating unit that generates denomination-specific collection schedule data including a scheduled collection date for the amount invoiced to the business partner and the denomination to be used for payment of the amount invoiced; a detection unit that refers to a storage unit in which the period from the scheduled collection date and the collection date required to collect the claim amount are set for each claim amount and each denomination, based on the claim amount of the denomination-specific collection schedule data, and detects the period from the scheduled collection date, the collection date, and the denomination that correspond to the claim amount of the denomination-specific collection schedule data; a calculation unit that calculates the month corresponding to the period from the scheduled collection date required to collect the invoice amount by adding the period detected by the detection unit to the scheduled collection date, and calculates the collection date in the calculated month as the collection date for the invoice amount; updating the scheduled collection date of the denomination-specific collection schedule data on the calculated collection date of the month, and functioning as an update processing unit that updates the denomination of the denomination-specific collection schedule data to the denomination detected by the detection unit; A business support program that features:

Images