Work support system, work support method, and work support program

Abstract

To enable supporting work to make a transfer entry of unpaid advance payment requests to accounts receivable.SOLUTION: An acquisition unit acquires invoice data of which the expected sales date has elapsed and estimate data indicating a breakdown of the invoice. A billing payment schedule data generation unit generates billing payment schedule data corresponding to the breakdown indicated in the acquired estimate data. A journal entry data generation unit generates and records journal entry data based on the generated billing payment schedule data, with the debit side representing an amount of the breakdown as accounts receivable and the credit side representing an amount of the breakdown as sales revenue. An allocation processing unit performs allocation processing, for each amount of the breakdown of the billing payment schedule data recorded as sales revenue, using a paid amount that can be allocated. The journal entry data generation unit generates and records journal entry data with the debit side representing an amount of the breakdown for which the allocation processing has been performed as an advance payment and the credit side representing an amount of the breakdown for which the allocation processing has been performed as accounts receivable.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-112948 A) discloses an allocation device that can reduce the burden of allocation work on accounting staff.

[0003] In this allocation device, a pre-processing unit extracts billing information that includes the same transaction partner information as the transaction partner information included in the deposit information from among billing information for which allocation work has not been completed. A grouping unit generates billing groups by grouping the billing information extracted by the pre-processing unit based on predetermined conditions.

[0004] The allocation processing unit calculates the degree of association with the payment information for the billing groups grouped by the grouping processing unit, and searches for a combination of billing groups having a total billing amount that matches the payment amount included in the payment information, starting with the most relevant.The allocation processing unit then outputs the billing information included in the combination of billing groups having a total billing amount that matches the payment amount as a billing allocation candidate for each combination.

[0005] If there are multiple combinations of billing groups with a total billing amount that matches the deposit amount, the presentation processing unit presents the combinations of billing groups according to the relevance of the billing groups included in the billing allocation candidates.

[0006] In paragraph 0048 of this patent document 1, it is stated that the allocation processing unit calculates the degree of association based on the difference between the payment deadline date of the billing information within the billing group and the payment date of the payment information. Also, in paragraph 0049, it is stated that the allocation processing is performed using the difference between the payment deadline date of the billing information and the payment date of the payment information as the degree of association. [Prior art documents] [Patent documents]

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

[0008] In some cases, advance payments are received before the sale or provision of the commercial transaction object. In this case, the advance payments are transferred to revenue accounts and recorded when the commercial transaction object is sold or provided.

[0009] However, if a commercial transaction object is sold or provided without the advance payment being received, the unpaid advance payment request must be transferred to accounts receivable. In such cases, accounting staff had to individually organize the payment status, create transfer slips, and record the transaction, which was a tedious task.

[0010] 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 support the business of transferring and recording unpaid advance payments as accounts receivable. [Means for solving the problem]

[0011] In order to solve the above-mentioned problems and achieve the object, the business support device of the present invention comprises an acquisition unit that acquires invoice data for which the expected sales date has passed and estimate data showing the breakdown of the invoice, a billing payment schedule data generation unit that generates billing payment schedule data corresponding to the breakdown shown in the acquired estimate data, a journal data generation unit that generates and records journal entry data based on the generated billing payment schedule data, in which the debit side is accounts receivable for the amount that corresponds to the breakdown and the credit side is sales for the amount that corresponds to the breakdown, and an allocation processing unit that performs allocation processing for the amount that can be allocated from the amount that has already been paid, for each amount of the breakdown of the billing payment schedule data that has been accounted for as sales, and the journal data generation unit generates and records journal entry data in which the debit side is an advance payment for the amount of the breakdown for which allocation processing has been performed and the credit side is accounts receivable for the amount of the breakdown for which allocation processing has been performed.

[0012] In addition, in order to solve the above-mentioned problems and achieve the object, the business support method of the present invention comprises an acquisition step in which an acquisition unit acquires invoice data for which the expected sales date has passed and estimate data showing a breakdown of the invoice; a invoice expected payment data generation step in which a invoice expected payment data generation unit generates invoice expected payment data corresponding to the breakdown shown in the acquired estimate data; a journal data generation step in which a journal data generation unit generates and records journal data based on the generated invoice expected payment data, with the debit side set to accounts receivable for the amount that corresponds to the breakdown and the credit side set to sales for the amount that corresponds to the breakdown; and an allocation processing step in which an allocation processing unit performs allocation processing for the amount that can be allocated from the amount that has already been paid, for each amount of the breakdown of the invoice expected payment data that has been allocated, and in the journal data generation step, journal data is generated and recorded with the debit side set to advance payment for the amount of the breakdown for which allocation processing has been performed on the credit side.

[0013] 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 an acquisition unit that acquires billing data for which the expected sales date has passed and estimate data showing the breakdown of the billing, an expected billing payment data generation unit that generates expected billing payment data corresponding to the breakdown shown in the acquired estimate data, a journal data generation unit that generates and records journal entry data based on the generated expected billing payment data, with the debit side set to accounts receivable for the amount that corresponds to the breakdown and the credit side set to sales for the amount that corresponds to the breakdown, and an allocation processing unit that performs allocation processing for the amount that can be allocated from the amount that has already been paid, for each amount of the breakdown of the expected billing payment data that has been allocated, and the journal data generation unit generates and records journal entry data with the debit side set to advance payment for the amount of the breakdown for which allocation processing has been performed and the credit side set to accounts receivable for the amount of the breakdown for which allocation processing has been performed. [Effects of the Invention]

[0014] The present invention can support the process of transferring unpaid advance payments to accounts receivable. [Brief explanation of the drawings]

[0015] [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 transaction classification master table provided in the business support device according to the embodiment. [Figure 3] FIG. 3 is a diagram illustrating an example of application fee request data generated by the business support device according to the embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of quotation data generated in association with billing data for an application fee in the business support device according to the embodiment. [Figure 5] FIG. 5 is a diagram illustrating an example of advance payment schedule data generated based on an application fee in the business support device according to the embodiment. [Figure 6] FIG. 6 is a diagram illustrating an example of deposit data generated when an application fee is deposited in the business support device according to the embodiment. [Figure 7] FIG. 7 is a diagram illustrating an example of payment reconciliation data generated based on the deposited application fee in the business support device according to the embodiment. [Figure 8] FIG. 8 is a diagram illustrating an example of advance receipt detail data generated based on the deposited application fee in the business support device according to the embodiment. [Figure 9] FIG. 9 is a diagram illustrating an example of journal data generated based on a deposited application fee in the business support device according to the embodiment. [Figure 10] FIG. 10 is a diagram illustrating an example of billing data for half the estimated amount generated by the business support device according to the embodiment. [Figure 11] FIG. 11 is a diagram illustrating an example of quotation data generated in association with billing data for half a payment in the business support device according to the embodiment. [Figure 12] FIG. 12 is a diagram illustrating an example of advance payment request schedule data generated based on half payment in the business support device according to the embodiment. [Figure 13] FIG. 13 is a diagram illustrating an example of deposit data generated when half money is deposited in the business support device according to the embodiment. [Figure 14] FIG. 14 is a diagram illustrating an example of deposit reconciliation data generated based on the deposited half amount in the business support device according to the embodiment. [Figure 15] FIG. 15 is a diagram illustrating an example of advance receipt detail data generated based on the half payment deposited in the business support device according to the embodiment. [Figure 16] FIG. 16 is a diagram illustrating an example of journal data generated based on a deposited half-payment in the business support device according to the embodiment. [Figure 17] FIG. 17 is a diagram illustrating an example of billing data for the remaining amount of the estimated amount generated by the business support device according to the embodiment. [Figure 18] FIG. 18 is a diagram illustrating an example of estimate data generated in association with billing data of the remaining amount in the business support device according to the embodiment. [Figure 19] FIG. 19 is a diagram illustrating an example of advance payment schedule data generated based on the remaining balance in the business support device according to the embodiment. [Figure 20] FIG. 20 is a diagram illustrating an example of billing data for the remaining balance generated when the expected sales date has passed without the remaining balance being deposited in the business support device according to the embodiment. [Figure 21] FIG. 21 is a diagram showing an example of quotation data generated in association with billing data for the remaining balance generated when the expected sales date has passed without payment in the business support device of the embodiment. [Figure 22] FIG. 22 is a diagram illustrating an example of bill payment schedule data generated based on the remaining unpaid amount in the business support device according to the embodiment. [Figure 23] FIG. 23 is a diagram illustrating an example of journal data of accounts receivable generated based on the remaining amount of unpaid money in the business support device according to the embodiment. [Figure 24] FIG. 24 is a diagram showing an example of advance receipt detail data generated based on the application fee and half payment already paid in the business support device according to the embodiment. [Figure 25]FIG. 25 is a diagram showing an example of bill payment schedule data in which allocation processing has been performed based on the application fee and half payment that have already been paid in the business support device according to the embodiment. [Figure 26] FIG. 26 is a diagram showing an example of journal data for an advance payment, which is an amount of unpaid accounts receivable that can be completely offset with the application fee and half payment that have already been paid. [Figure 27] Figure 27 is a diagram for explaining the operation of an embodiment of a business support device, in which scheduled invoice payment data generated before scheduled invoice payment data generated based on the remaining unpaid balance is generated is treated as completed to prevent duplicate management. [Figure 28] FIG. 28 is a diagram illustrating an example of deposit data generated by depositing the remaining uncollected amount in the business support device according to the embodiment. [Figure 29] FIG. 29 is a diagram illustrating an example of deposit reconciliation data generated based on the remaining uncollected amount deposited in the business support device according to the embodiment. [Figure 30] FIG. 30 is a diagram illustrating an example of journal data generated based on the remaining amount of money deposited but not collected in the business support device according to the embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0016] 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.

[0017] (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).

[0018] 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 capable of supporting operations such as transferring unpaid advance payments to accounts receivable. The storage unit 2 also includes a transaction classification master table 11, a billing data storage unit 12, an estimate data storage unit 13, a billing payment schedule data storage unit 14, a payment data storage unit 15, a payment reconciliation data storage unit 16, an advance payment detail data storage unit 17, and a journal data storage unit 18, which are storage areas.

[0019] As shown in Figure 2, the transaction category master table 11 stores data types, revenue transfer flags, revenue recognition transaction categories, and debt items in association with each other for transaction categories of commercial transaction objects such as services or goods.

[0020] In the example of Figure 2, the types of amounts to be deposited as transaction categories, such as application fee, half payment, remaining balance, and post-construction sales, are stored in the transaction category master table 11. Also, in the example of Figure 2, the application fee, half payment, and remaining balance are set as the data type of "advance payment." Also, the post-construction sales are set as the data type of "sales."

[0021] The revenue transfer flag is information that indicates whether or not to transfer the accounts receivable corresponding to the remaining amount when there is a payment (balance) that has not been received by the due date. In the example of Figure 2, the revenue transfer flag of "1" is set for the "balance" to indicate that transfer processing will be performed, and the revenue transfer flag of "0" is set for the application fee, half payment, and post-construction sales, indicating that transfer processing will not be performed.

[0022] The revenue recognition transaction category indicates the transaction category used at the time of recognition. The example in Figure 2 shows the setting to use the transaction category of "Post-implementation sales," which indicates sales after the provision of the commercial transaction object, when the transfer process of accounts receivable for the "balance" is performed.

[0023] Receivables are account items assigned to commercial transactions in each transaction category. In the example in Figure 2, "Advance Payment" is set as the receivables item for the transaction categories of application fee, half payment, and remaining payment, and "Accounts Receivable" is set as the receivables item for the transaction category of post-construction sales.

[0024] (Functional configuration of business support device) Next, the control unit 3 executes the business support program stored in the memory unit 2, and thereby functions as an acquisition unit 21, a data generation unit 22, an allocation processing unit 23, an accounting data generation unit 24, a billing payment schedule data generation unit 25, a payment data generation unit 26, and a payment reconciliation data generation unit 27, as shown in Figure 1.

[0025] In this example, the acquisition unit 21 to the deposit reconciliation data generation unit 27 are described as being realized by software based on a business support program. However, part or all of the acquisition unit 21 to the deposit reconciliation data generation unit 27 may also be realized by hardware. In either case, the same effects as those described below can be obtained.

[0026] The acquisition unit 21 acquires billing data (see FIG. 20) for which the expected sales date has passed and estimate data (see FIG. 21) showing the breakdown of the billing.

[0027] The data generation unit 22 includes a billing payment schedule data generation unit 25, a payment data generation unit 26, a payment reconciliation data generation unit 27, and the like.

[0028] The billing payment schedule data generating unit 25 generates billing payment schedule data (see FIG. 22) corresponding to the breakdown indicated in the estimate data acquired by the acquiring unit 21.

[0029] Based on the generated expected billing payment data, the journal data generation unit 24 generates and records journal data (see Figure 23) in which the debit side is the accounts receivable amount that corresponds to the breakdown and the credit side is the sales amount that corresponds to the breakdown.

[0030] The allocation processing unit 23 performs allocation processing for the amount that can be allocated from the amount that has been paid, for each amount of the breakdown of the billing payment schedule data that has been recorded as sales (see FIG. 25).

[0031] The journal data generation unit 24 generates and records journal data in which the debit side is the advance payment for the amount of the breakdown for which allocation processing has been performed and the credit side is the accounts receivable for the amount of the breakdown for which allocation processing has been performed (see Figure 26).

[0032] In addition, the acquisition unit 21 acquires billing data (see Figure 20) assigned a transaction category (in the example of Figure 2, the transaction category of the remaining balance) for which the execution of the allocation process is specified by the revenue transfer flag stored in the memory unit (transaction category master table 11 in Figure 2) and estimate data (see Figure 21) showing the breakdown of the billing data.

[0033] In addition, the billing payment schedule data generation unit 25 assigns a billing completion flag, which is information indicating that the payment process has been completed, to billing payment schedule data corresponding to the unpaid amount generated before the expected sales date has passed, thereby making the billing payment schedule data generated before the expected sales date into billing payment schedule data for which payment has been completed (see Figure 27).

[0034] In addition, when the remaining amount, which is the amount not yet deposited after the allocation process, is deposited, the data generation unit 22 generates deposit data corresponding to the deposited amount (see Figure 28), and also generates deposit reconciliation data including specific information (invoice deposit schedule number in Figure 29) that identifies the billing deposit schedule data (invoice deposit schedule data in Figure 25) generated based on the billing data and estimate data for which the expected sales date has passed, and a deposit reconciliation amount equivalent to the deposited amount (see Figure 29).

[0035] In this case, the journal data generation unit 24 generates and records journal data based on the deposit reconciliation data, with the debit account item on the debit side being a deposit, the debit amount being the deposit reconciliation amount, the credit account item on the credit side being accounts receivable, and the credit amount being the deposit reconciliation amount.

[0036] (Operation of the business support device according to the embodiment) Next, as an example, the accounting process operation of the business support device 1 of the embodiment will be described based on the payment forms of "application fee," "half payment," and "remaining payment" that are payments to a wedding hall.

[0037] (Accounting process for application fee) First, at the wedding hall, for example, an accounting staff member performs an input operation to create billing data for the "application fee" via the input device 6 of the business support device 1. In response to this input operation, the data generation unit 22 generates the billing data exemplified in Fig. 3 and stores it in the billing data storage unit 12 shown in Fig. 1, and generates quotation data exemplified in Fig. 4 and stores it in the quotation data storage unit 13 shown in Fig. 1.

[0038] As shown in Figure 3, the billing data includes the billing number, business partner, billing date, transaction category, billing amount, expected collection date, expected sales date, and the quotation number of the quotation data associated with this billing data. At this stage, the transaction category is "application fee." In this example, the amount of the application fee is "100,000 yen." The quotation number of the quotation data associated with this billing data is "M0001."

[0039] As shown in Figure 4, the quotation data includes the quotation number, which is the same as the quotation number entered in the billing data, the line number, the client, the details of the goods or services (details) to be provided at the wedding, the sales account, the tax rate, the base price, and the amount of consumption tax.

[0040] Figure 4 shows an example where a wedding cake, drinks, food, and attire are provided. The sales account for the wedding cake, drinks, and food is "Sales_Beverage," the consumption tax rate is "10%," the base price is "200,000 yen," "400,000 yen," and "1,000,000 yen," respectively, and the consumption tax amount is "20,000 yen," "40,000 yen," and "100,000 yen," respectively. The sales account for the attire is "Sales_Attire," the consumption tax rate is "10%, the base price is "500,000 yen," and the consumption tax amount is "50,000 yen."

[0041] The quotation number of this quotation data is "M0001", the same as the quotation number assigned to the billing data shown in Figure 3. Therefore, the billing data in Figure 3 and the quotation data in Figure 4 are handled in association with each other based on the quotation number "M0001".

[0042] Next, the billing payment schedule data generation unit 25 generates billing payment schedule data indicating the amount of the application fee that is scheduled to be deposited, as shown in Fig. 5, and stores this invoice payment schedule data in the billing payment schedule data storage unit 14 shown in Fig. 1. As shown in Fig. 5, this billing payment schedule data includes the billing payment schedule number, line number, billing date, business partner, transaction classification, sales item, credit item, tax rate, main amount, consumption tax amount, billing number, etc.

[0043] At this stage, the transaction category is "application fee." The credit item for this "application fee" is "advance payment," as set in the transaction category master table 11 shown in Figure 2. The amount is "100,000 yen," and the invoice number is "S0001," the same as the invoice number in the invoice data shown in Figure 3. This invoice number associates the invoice data in Figure 3 with the expected invoice payment data in Figure 5.

[0044] Next, let's say that an application fee is deposited by a user of the wedding hall. The accounting staff then deposits the deposited application fee, clears the deposit, and enters the advance payment. In response to the deposit operation, the deposit data generation unit 26 generates the deposit data shown in FIG. 6 and stores it in the deposit data storage unit 15. The deposit clearing data generation unit 27 generates the deposit clearing data shown in FIG. 7 and stores it in the deposit clearing data storage unit 16. The data generation unit 22 also generates the advance payment detail data shown in FIG. 8 and stores it in the advance payment detail data storage unit 17.

[0045] As shown in FIG. 6, the deposit data includes the deposit number, line number, deposit date, customer, deposit type, deposit amount, etc.

[0046] As shown in Figure 7, the deposit reconciliation data is composed of the deposit reconciliation number, line number, deposit number, line number, deposit reconciliation date, deposit reconciliation amount, and scheduled invoice deposit number. The deposit number is entered as the deposit number of the deposit data to be reconciled. In this example, the deposit number "NY0001" of the deposit data shown in Figure 6 is entered as the deposit number of the deposit reconciliation data as shown in Figure 7. In addition, the scheduled invoice deposit number "SN0001", which is the same as the scheduled invoice deposit number of the scheduled invoice deposit data shown in Figure 5, which was created as the deposit schedule for the application fee, is entered as the scheduled invoice deposit number of the deposit reconciliation data shown in Figure 7.

[0047] The advance payment detail data includes the advance payment detail number, advance payment date, advance payment amount, invoice number, expected invoice payment number, line number, and transaction category, as shown in Figure 8. In this case, the transaction category is "application fee," and the advance payment amount is "100,000 yen" deposited as the application fee.

[0048] Additionally, the billing number "S0001" is entered as the billing number, which is the same as the billing number of the billing data shown in Figure 3, which is the billing data for the application fee. This causes the billing data in Figure 3 and the advance receipt detail data in Figure 8 to be associated with each other.

[0049] Additionally, the expected billing payment number "SN0001" is entered as the expected billing payment number, which is the same as the expected billing payment number in the expected billing payment data shown in Figure 5, which was created as the expected payment of the application fee. This causes the expected billing payment data in Figure 5 and the advance receipt detail data in Figure 8 to be associated with each other.

[0050] Next, the journal data generation unit 24 generates journal data corresponding to the deposited application fee of "100,000 yen" as shown in Fig. 9, and stores (accounts) it in the journal data storage unit 18 shown in Fig. 1. In this case, the debit account item on the debit side will be "Deposit," and the debit amount will be the deposited application fee of "100,000 yen." Also, the credit account item on the credit side will be "Advance Payment," and the credit amount will be the deposited application fee of "100,000 yen."

[0051] (Accounting process for half-payment) As shown in Figure 4, the breakdown of the wedding expenses, including consumption tax, is as follows: wedding cake cost 220,000 yen, drinks cost 440,000 yen, food cost 1,100,000 yen, and attire cost 550,000 yen, so the total is 2,310,000 yen, or 220,000 yen + 440,000 yen + 1,100,000 yen + 550,000 yen. Therefore, at this stage, with the application fee of 100,000 yen paid, the remaining balance is 2,210,000 yen.

[0052] The accounting staff performs an input operation to create billing data for "1.1 million yen," which is roughly half of the remaining balance of "2.21 million yen" at this point. In response to this input operation, the data generation unit 22 generates billing data as shown in Fig. 10 and stores it in the billing data storage unit 12 shown in Fig. 1, and generates quotation data as shown in Fig. 11 and stores it in the quotation data storage unit 13 shown in Fig. 1.

[0053] In this case, a new invoice number such as "S0002" is assigned to the invoice data, as shown in Figure 10. In addition, the transaction category of "half payment" is entered, and "1,100,000 yen" is entered as the amount of half payment. Furthermore, as the estimate number of the estimate data associated with this invoice data, the estimate number of "M0002" of the estimate data shown in Figure 11 is entered as the estimate number of the invoice data shown in Figure 10.

[0054] Even when the data generation unit 22 generates the billing data for this half payment, it generates quotation data with the same breakdown as the quotation data corresponding to the application fee, as shown in FIG. 11. However, the data generation unit 22 inputs a quotation number "M0002" that is different from the quotation number (M0001) of the quotation data corresponding to the application fee as the quotation number for the quotation data corresponding to the half payment. This quotation number "M0002" is also input as the quotation number for the billing data, as shown in FIG. 10. As a result, the billing data shown in FIG. 10 and the quotation data shown in FIG. 11 are mutually associated.

[0055] Next, the billing payment schedule data generation unit 25 generates billing payment schedule data indicating the amount of the half payment scheduled to be received, as shown in FIG. 12, and stores this in the billing payment schedule data storage unit 14 shown in FIG. 1. As shown in FIG. 12, the transaction category of the billing payment schedule data at this stage is "half payment." Furthermore, the credit item for this "half payment" is "advance payment," as set in the transaction category master table 11 shown in FIG. 2. Furthermore, the main amount is "1,100,000 yen," and the billing number is "S0002," the same as the billing data shown in FIG. 10. This billing number associates the billing data in FIG. 10 and the billing payment schedule data in FIG. 12 with each other.

[0056] Next, let's say that half the payment is deposited by a customer at the wedding hall. The accounting staff then deposits the deposited half the payment, clears the deposit, and inputs the advance payment. In response to the deposit operation, the deposit data generation unit 26 generates the deposit data shown in FIG. 13 and stores it in the deposit data storage unit 15. The deposit clearing data generation unit 27 generates the deposit clearing data shown in FIG. 14 and stores it in the deposit clearing data storage unit 16. The data generation unit 22 also generates the advance payment detail data shown in FIG. 15 and stores it in the advance payment detail data storage unit 17.

[0057] A new deposit number "NY0002" is assigned to the deposit data as shown in Figure 13. Also, the deposit amount of "1.1 million yen", which is half the amount, is entered into the deposit data.

[0058] The deposit number of the deposit data to be cleared is entered into the deposit reconciliation data, as shown in Figure 14. In this example, the deposit number "NY0002" of the half-money deposit data shown in Figure 13 is entered as the deposit number of the deposit reconciliation data, as shown in Figure 14. In addition, the scheduled billing payment number "SN0002", which is the same as the scheduled billing payment number of the scheduled billing payment data shown in Figure 12, which was created as the half-money deposit schedule, is entered as the scheduled billing payment number of the deposit reconciliation data shown in Figure 14.

[0059] As shown in Figure 15, the transaction category in this case, "half payment," is entered in the advance payment detail data, and the advance payment amount of "1.1 million yen" deposited as half payment is entered as the advance payment amount.

[0060] Additionally, the billing number "S0002" is entered as the billing number, which is the same as the billing number of the billing data shown in Figure 10, which is the billing data for half payment. This causes the billing data in Figure 10 and the advance receipt detail data in Figure 15 to be associated with each other.

[0061] Additionally, the billing payment schedule number "SN0002" is entered as the billing payment schedule number, which is the same as the billing payment schedule number in the billing payment schedule data shown in Figure 12, which was created as the half-payment payment schedule. This causes the billing payment schedule data in Figure 12 and the advance receipt detail data in Figure 15 to be associated with each other.

[0062] Next, the journal data generation unit 24 generates journal data corresponding to the half of the deposited "1.1 million yen" as shown in Fig. 16, and stores (records) it in the journal data storage unit 18 shown in Fig. 1. In this case, the debit account item on the debit side will be "Deposit" and the debit amount will be the half of the deposited "1.1 million yen". Also, the credit account item on the credit side will be "Advance Received" and the credit amount will be the half of the deposited "1.1 million yen".

[0063] (Accounting process for remaining balance) As shown in Figure 4, the breakdown of the wedding expenses, including consumption tax, is as follows: wedding cake cost 220,000 yen, drinks cost 440,000 yen, food cost 1,100,000 yen, and attire cost 550,000 yen, so the total is 2,310,000 yen, or 220,000 yen + 440,000 yen + 1,100,000 yen + 550,000 yen. Therefore, at this stage, the application fee of 100,000 yen and half the payment of 1,100,000 yen have been paid, so the remaining balance is 1,110,000 yen.

[0064] The accounting staff performs an input operation to create billing data for the remaining balance at this point, "1,110,000 yen." In response to this input operation, the data generation unit 22 generates the billing data exemplified in Fig. 17 and stores it in the billing data storage unit 12 shown in Fig. 1, and generates quotation data exemplified in Fig. 18 and stores it in the quotation data storage unit 13 shown in Fig. 1.

[0065] In this case, a new invoice number such as "S0003" is assigned to the invoice data, as shown in Figure 17. In addition, the transaction category of "balance" is entered, and "1,110,000 yen" is entered as the balance amount. Furthermore, as the estimate number of the estimate data associated with this invoice data, the estimate number of "M0003" of the estimate data shown in Figure 18 is entered as the estimate number of the invoice data shown in Figure 17.

[0066] When the data generation unit 22 generates the billing data for this remaining balance, it generates quotation data with the same breakdown as the quotation data corresponding to the application fee, as shown in FIG. 18. However, the data generation unit 22 inputs the quotation number "M0003," which is different from the quotation numbers (M0001 or M0002) of the quotation data for the application fee and half payment previously generated, as the quotation number for the quotation data corresponding to the remaining balance. This quotation number "M0003" is also input as the quotation number for the billing data, as shown in FIG. 17. As a result, the billing data shown in FIG. 17 and the quotation data shown in FIG. 18 are mutually associated.

[0067] Next, the billing payment schedule data generation unit 25 generates billing payment schedule data indicating the amount of the remaining balance that is scheduled to be deposited, as shown in FIG. 19, and stores this in the billing payment schedule data storage unit 14 shown in FIG. 1. As shown in FIG. 19, the transaction category of the billing payment schedule data at this stage is "balance." The credit item for this "balance" is "advance payment," as set in the transaction category master table 11 shown in FIG. 2. The main amount is "1,110,000 yen," and the billing number is "S0003," the same as the billing number for the billing data shown in FIG. 17. This billing number associates the billing data in FIG. 17 and the billing payment schedule data in FIG. 19 with each other.

[0068] Here, let's assume that a wedding ceremony is held (services are provided) without the remaining balance being paid by the wedding hall user. As a nighttime process, at midnight or the like, the acquisition unit 21 compares the expected sales date of each billing data stored in the billing data storage unit 12 shown in FIG. 1 with the current date. Then, the acquisition unit 21 acquires from the billing data storage unit 12 any billing data that has passed the expected sales date.

[0069] For example, suppose the expected sales date, which is the date on which the remaining balance is scheduled to be deposited, is December 1, 2023, and a wedding is held on December 1, 2023, with the remaining balance not yet deposited. In this case, the acquisition unit 21 acquires, just after midnight on December 2, 2023, billing data in which December 1, 2023 is set as the expected sales date and which has a transaction classification of "balance" from the billing data storage unit 12. As a result, in this example, as shown in FIG. 20, billing data with a billing number of "S0003," a transaction classification of "balance," and an "expected sales date" of December 1, 2023 is acquired from the billing data storage unit 12.

[0070] In addition, the acquisition unit 21 acquires the quotation data shown in FIG. 21, which has the same quotation number as the quotation number "M0003" assigned to the acquired billing data, from the quotation data storage unit 13 shown in FIG.

[0071] Next, the billing payment schedule data generation unit 25 references the transaction classification master table 11 shown in Fig. 2 and detects the transaction classification of "post-implementation sales (sales after service is provided)" as the transaction classification of "balance." Then, the billing payment schedule data generation unit 25 generates billing payment schedule data corresponding to the breakdown of the quotation data shown in Fig. 21 and stores it in the billing payment schedule data storage unit 14 shown in Fig. 1 (sales corresponding to the quotation data are recorded even though the advance payment has not yet been received).

[0072] The billing payment schedule data shown in Fig. 22 is the billing payment schedule data newly generated by the billing payment schedule data generation unit 25. In this case, the billing payment schedule data generation unit 25 generates billing payment schedule data by adding a new billing payment schedule number "SN0004", setting the transaction category to "post-construction sales", setting the sales item to "sales_food and beverage" or "sales_costume" depending on the breakdown, and setting the receivable item to "accounts receivable".

[0073] The billing number for the sales amount in the billing payment schedule data shown in FIG. 22 is not entered because there is no original billing data.

[0074] Based on the generated expected billing payment data, the journal data generation unit 24 generates journal data in which the debit account item on the debit side is "accounts receivable," the debit amount is the amount of each breakdown, the credit account item on the credit side is "sales_food and beverage" or "sales_costumes" depending on each breakdown, and the credit amount is the amount of each breakdown, as shown in Figure 23, and stores the data in the journal data storage unit shown in Figure 1.

[0075] Next, at this point in time, the advance receipt detail data stored in the advance receipt detail data storage unit 17 shown in Fig. 1 becomes the above-mentioned advance receipt detail data for the application fee and the advance receipt detail data for the half payment, as shown in Fig. 24. In other words, at this point in time, the amount already deposited is a total of 1.2 million yen, consisting of the application fee of 100,000 yen and the half payment of 1.1 million yen.

[0076] The allocation processing unit 23 inputs the advance payment transfer amount, which is the amount of "1.2 million yen" that has already been deposited, into the billing payment schedule data as shown in FIG. 25 for each account receivable in the billing payment schedule data shown in FIG. 22, which was recorded by the sales recording process for the amount not yet deposited after the wedding ceremony (sales recording process after construction).

[0077] That is, in this example, since the amount deposited is "1.2 million yen," the allocation processing unit 23 allocates "220,000 yen," which will be the accounts receivable for the wedding cake, from this "1.2 million yen." Furthermore, as a result of this allocation processing, the amount that can be allocated becomes "1.2 million yen - 220,000 yen = 980,000 yen." Therefore, the allocation processing unit 23 allocates "440,000 yen," which will be the accounts receivable for the drink costs, from this "980,000 yen."

[0078] Furthermore, as a result of this allocation process, the amount that can be allocated becomes "980,000 yen - 440,000 yen = 540,000 yen." Therefore, allocation processing unit 23 allocates this "540,000 yen" to "1,000,000 yen," which is the accounts receivable for the food costs. The balance after this allocation process becomes "1,110,000 yen."

[0079] Next, the journal data generation unit 24 generates journal data for the accounts receivable for which the allocation process has been completed, as shown in Fig. 26. In this case, the journal data is journal data for recording sales of 220,000 yen, 440,000 yen, and 540,000 yen for which the allocation process has been completed, as shown in Fig. 26, and is stored in the journal data storage unit 18 in Fig. 1.

[0080] In this way, the business support device 1 of the embodiment records the transfer of services to revenue accounts as accounts receivable / sales rather than advance receipts / sales, and then automatically records the advance receipts / accounts receivable separately. This makes it possible to automatically transfer and record accounts receivable for unpaid amounts. It also eliminates the need to journalize unpaid advance receipts as accounts receivable after the commercial transaction object has been provided, thereby supporting the accounting work of accounting personnel. It also prevents the inconvenience of having to correct accounting procedures due to omissions, etc.

[0081] Next, as explained using Figure 19, the billing payment schedule data generation unit 25 attaches a billing completion flag (billing completion flag of "1" in Figure 27) which is information indicating that the deposit process has been completed, to the billing payment schedule data corresponding to the unpaid amount that was generated before the expected sales date (in this example, December 1, 2023), as shown in Figure 27. This allows the billing payment schedule data shown in Figure 19 that was generated before the expected sales date has passed to be treated as billing payment schedule data for which deposit has been completed, preventing duplicate management.

[0082] Next, after the wedding ceremony, if the user deposits the remaining balance of "1.11 million yen," the deposit data generation unit 26 generates deposit data corresponding to the remaining balance of "1.11 million yen" shown in Figure 28 based on the accounting staff's deposit input operation, and stores it in the deposit data storage unit 15 shown in Figure 1.

[0083] In addition, based on the accounting staff's deposit reconciliation input operation, the deposit reconciliation data generation unit 27 generates deposit reconciliation data corresponding to the remaining balance of "1,110,000 yen" shown in Figure 29, and stores it in the deposit reconciliation data storage unit 16 shown in Figure 1.

[0084] Finally, the journal data generation unit 24 generates journal data corresponding to the remaining amount of the deposited "1,110,000 yen" as shown in Figure 30, and stores it in the journal data storage unit 18 shown in Figure 1. In this case, the debit account item on the debit side will be "Deposit" and the debit amount will be "1,110,000 yen", the half amount deposited. Also, the credit account item on the credit side will be "Accounts Receivable" and the credit amount will be "1,110,000 yen", the half amount deposited.

[0085] (Effects of the embodiment) As is clear from the above explanation, the business support device 1 of the embodiment records the transfer to the revenue account at the time of service provision as accounts receivable / sales rather than advance payment / sales, and then automatically records the advance payment / accounts receivable separately.

[0086] This allows for automatic transfer and accounting of unpaid accounts receivable. It also eliminates the need to journalize unpaid advances received as accounts receivable after providing the subject of a commercial transaction, thereby supporting accounting staff in their accounting work. It also prevents the inconvenience of having to correct accounting procedures due to omissions, etc.

[0087] [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.

[0088] 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.

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

[0090] [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.

[0091] 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.

[0092] 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.

[0093] 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.

[0094] 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.

[0095] 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.

[0096] 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.

[0097] 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.

[0098] 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.

[0099] 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.

[0100] 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.

[0101] 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.

[0102] 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.

[0103] 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]

[0104] The present invention is suitable for supporting businesses that perform advance billing and payment processing before services are provided, such as bridal businesses, travel businesses, and banquet businesses. [Explanation of symbols]

[0105] 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 Transaction Classification Master Table 12. Billing data storage unit 13 Estimate data storage unit 14. Billing and payment schedule data storage section 15 Deposit data storage unit 16. Deposit reconciliation data storage section 17 Advance receipt detail data storage unit 18 Journal data storage unit 21 Acquisition Department 22 Data Generation Unit 23 Allocation Processing Unit 24 Journal data generation unit 25. Billing and payment schedule data generation section 26 Deposit data generation unit 27 Deposit reconciliation data generation section

Claims

1. an acquisition unit that acquires billing data for which the expected sales date has passed and quotation data indicating the details of the billing; a billing payment schedule data generation unit that generates billing payment schedule data corresponding to the breakdown indicated in the acquired estimate data; a journal data generation unit that generates and records journal data based on the generated bill payment schedule data, with the debit side representing accounts receivable of the breakdown amount and the credit side representing sales of the breakdown amount; and an allocation processing unit that performs allocation processing for the amount that can be allocated from the amount that has been paid, for each amount of the breakdown of the billing payment schedule data that has been recorded as sales, the journal data generation unit generates and records journal data in which the debit side is the advance payment of the amount of the breakdown for which the allocation process has been performed and the credit side is the accounts receivable of the amount of the breakdown for which the allocation process has been performed; A business support device characterized by the above.

2. The acquisition unit acquires billing data to which a transaction classification for which execution of the allocation process is designated by a revenue transfer flag stored in a storage unit is assigned and the quotation data indicating a breakdown of the billing data; 2. The business support device according to claim 1, wherein:

3. the billing payment schedule data generation unit attaches a billing completion flag, which is information indicating that the payment process has been completed, to the billing payment schedule data corresponding to the unpaid amount generated before the expected sales date has passed, thereby making the billing payment schedule data generated before the expected sales date into billing payment schedule data for which payment has been completed; 3. The business support device according to claim 2, wherein:

4. a data generating unit that, when the remaining amount, which is the unpaid amount after the allocation process, is deposited, generates deposit data corresponding to the deposited amount, and generates deposit reconciliation data including specific information for identifying the billing deposit scheduled data generated based on the billing data and the estimate data for which the expected sales date has passed, and a deposit reconciliation amount equivalent to the deposited amount; the journal data generation unit generates and records journal data based on the payment reconciliation data, with the debit account item on the debit side being a deposit, the debit amount being the payment reconciliation amount, the credit account item on the credit side being accounts receivable, and the credit amount being the payment reconciliation amount; 4. The business support device according to claim 3, wherein:

5. an acquisition step in which an acquisition unit acquires billing data for which the expected sales date has passed and quotation data indicating details of the billing; a billing payment schedule data generation step in which a billing payment schedule data generation unit generates billing payment schedule data corresponding to the breakdown indicated in the acquired estimate data; a journal data generation step in which a journal data generation unit generates and records journal data based on the generated bill payment schedule data, with the debit side representing accounts receivable of the amount that constitutes the breakdown and the credit side representing sales of the amount that constitutes the breakdown; an allocation processing step in which an allocation processing unit performs allocation processing for the amount that can be allocated from the amount that has been deposited, for each amount of the breakdown of the billing payment schedule data that has been recorded as sales; In the journal data generation step, journal data is generated and recorded in which the debit side is the advance payment of the amount of the breakdown for which the allocation process has been performed and the credit side is the accounts receivable of the amount of the breakdown for which the allocation process has been performed; A business support method characterized by the above.

6. Computer, an acquisition unit that acquires billing data for which the expected sales date has passed and quotation data indicating the details of the billing; a billing payment schedule data generation unit that generates billing payment schedule data corresponding to the breakdown indicated in the acquired estimate data; a journal data generation unit that generates and records journal data based on the generated bill payment schedule data, with the debit side representing accounts receivable of the breakdown amount and the credit side representing sales of the breakdown amount; The system functions as an allocation processing unit that performs allocation processing for the amount that can be allocated from the amount that has been paid, for each amount of the breakdown of the billing payment schedule data that has been recorded as sales, the journal data generation unit generates and records journal data in which the debit side is the advance payment of the amount of the breakdown for which the allocation process has been performed and the credit side is the accounts receivable of the amount of the breakdown for which the allocation process has been performed; A business support program that features:

Images