Work support device, work support method, and work support program

Abstract

To reduce a workload of money receipt collation tasks for a company that operates a store development business.SOLUTION: A work support device includes: an acquisition unit that acquires sales data and money receipt data including the same store identification information from a storage unit that stores at least the sales data including store identification information assigned to each store, sales amounts, reconciliation amounts, and expected money receipt dates of the sales amounts from the stores, and the money receipt data including the store identification information, money receipt dates, money receipt amounts, and reconciliation amounts; an extraction unit that extracts expected money receipt dates before a specified base date and sales amounts associated with the expected money receipt dates from the acquired sales data, and extracts money receipt dates before the specified base date and money receipt amounts associated with the money receipt dates from the money receipt data; and a reconciliation process unit that collates the extracted sales data with the extracted money receipt data, and, if money receipt data including money receipt amounts matching the sales amounts in the sales data exists, registers the sales amounts and the money receipt amounts that match the reconciliation amounts of the sales data and the money receipt data to perform a reconciliation process.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] Today, payment reconciliation systems are able to notify the person in charge when multiple sales data matches one payment detail data, or when multiple payment detail data matches one sales data, as specific candidates for payment reconciliation.

[0003] Patent Document 1 (JP Patent Publication No. 2017-68336) discloses in paragraphs 0030 to 0034, etc., a technology for storing received sales data and received deposit detail data, comparing the sales data and the deposit detail data, and performing a deposit reconciliation process to improve business efficiency. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2017-68336 Summary of the Invention [Problem to be solved by the invention]

[0005] However, there is a demand for the development of a business support device that can reduce the workload of checking receipts for companies that operate storefronts.

[0006] The present invention has been made in view of the above-mentioned problems, and an object of the present invention is to provide a business support device, a business support method, and a business support program that can reduce the workload of checking deposits. [Means for solving the problem]

[0007] In order to solve the above-mentioned problems and achieve the objectives, the business support device of the present invention has an acquisition unit that acquires sales data and deposit data containing the same store identification information from a memory unit that stores at least sales data including store identification information assigned to each store, sales amount, write-off amount, and the expected date of deposit of the sales amount from the store, and deposit data including store identification information, deposit date, deposit amount, and write-off amount; an extraction unit that extracts expected deposit dates and sales amounts associated with the expected deposit dates that occur before a specified base date from the acquired sales data, and extracts deposit dates and deposit amounts associated with the deposit dates that occur before the specified base date from the deposit data; and a reconciliation processing unit that compares the extracted sales data with the extracted deposit data, and, if there is deposit data including a deposit amount that matches the sales amount in the sales data, registers the sales amount and deposit amount that match the reconciliation amount in the sales data and deposit data, and performs reconciliation processing.

[0008] In addition, in order to solve the above-mentioned problems and achieve the object, the business support method of the present invention includes an acquisition step in which an acquisition unit acquires sales data and deposit data containing the same store identification information from a storage unit in which sales data including at least store identification information assigned to each store, sales amount, write-off amount, and the expected date of deposit of the sales amount from the store, and deposit data including store identification information, deposit date, deposit amount, and write-off amount are stored; an extraction step in which an extraction unit extracts from the acquired sales data scheduled deposit dates and sales amounts related to the scheduled deposit dates that occur before a specified base date, and extracts from the deposit data deposit dates that occur before the specified base date and deposit amounts related to the deposit dates; and a reconciliation processing step in which a reconciliation processing unit compares the extracted sales data with the extracted deposit data, and, if there is deposit data including a deposit amount that matches the sales amount of the sales data, registers the sales amount and deposit amount that match the reconciliation amount of the sales data and deposit data, and performs a reconciliation processing.

[0009] In addition, in order to solve the above-mentioned problems and achieve the objectives, the business support program of the present invention causes a computer to function as an acquisition unit that acquires sales data and deposit data containing the same store identification information from a memory unit that stores at least sales data including store identification information assigned to each store, sales amount, write-off amount, and the expected date of deposit of the sales amount from the store, and deposit data including store identification information, deposit date, deposit amount, and write-off amount; an extraction unit that extracts expected deposit dates and sales amounts associated with the expected deposit dates that occur before a specified base date from the acquired sales data, and extracts deposit dates and deposit amounts associated with the deposit dates that occur before the specified base date from the deposit data; and a reconciliation processing unit that compares the extracted sales data with the extracted deposit data, and, if there is deposit data including a deposit amount that matches the sales amount in the sales data, registers the sales amount and deposit amount that match the reconciliation amount in the sales data and deposit data, and performs reconciliation processing. [Effects of the Invention]

[0010] The present invention can reduce the workload of checking receipts. [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 outline of a process executed by the task assistance device according to the embodiment. [Figure 3] FIG. 3 is a diagram illustrating an example of a store holiday calendar master registration process executed by the business support device according to the embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of the process of importing sales data. [Figure 5] FIG. 5 is a diagram showing an example of the first half of the operation of the method for calculating the expected deposit date. [Figure 6] FIG. 6 is a diagram showing an example of the second half of the operation of the method for calculating the expected deposit date. [Figure 7] FIG. 7 is a diagram illustrating an example of the first half of the detailed calculation logic. [Figure 8]FIG. 8 is a diagram illustrating an example of the latter half of the detailed calculation logic. [Figure 9] FIG. 9 is a diagram illustrating an example of the store holiday calendar master. [Figure 10] FIG. 10 is a diagram illustrating an example of the district master. [Figure 11] FIG. 11 is a diagram illustrating an example of the store master. [Figure 12] FIG. 12 is a diagram illustrating an example of the target category master. [Figure 13] FIG. 13 is a diagram illustrating an example of the target date division master. [Figure 14] FIG. 14 is a diagram illustrating an example of the business category master. [Figure 15] FIG. 15 is a diagram illustrating an example of the bank calendar master. [Figure 16] FIG. 16 is a diagram illustrating an example of the store holiday classification master. [Figure 17] FIG. 17 is a diagram illustrating an example of the day-of-week classification master. [Figure 18] FIG. 18 is a diagram for explaining a first calculation example of the expected deposit date. [Figure 19] FIG. 19 is a diagram for explaining a second calculation example of the expected deposit date. [Figure 20] FIG. 20 is a diagram for explaining a third calculation example of the expected deposit date. [Figure 21] FIG. 21 is a diagram for explaining a fourth calculation example of the expected deposit date. [Figure 22] FIG. 22 is a diagram showing an example of the deposit data import process. [Figure 23] FIG. 23 is a diagram showing the procedure for automatic matching processing for sales data and deposit data. [Figure 24] FIG. 24 is a diagram showing an example of sales data and deposit data before the automatic matching process. [Figure 25] FIG. 25 is a diagram showing an example of sales data and deposit data after automatic matching processing. [Figure 26]FIG. 26 is a diagram showing an example of sales data and deposit data before the automatic matching process. [Figure 27] FIG. 27 is a diagram showing an example of sales data and deposit data after automatic matching processing. [Figure 28] FIG. 28 is a diagram showing an example of the matching result data after the automatic matching process. [Figure 29] FIG. 29 is a diagram showing the procedure for inputting a comparison between sales data and deposit data. [Figure 30] FIG. 30 is a diagram showing an example of a store designation process on the verification input screen. [Figure 31] FIG. 31 is a diagram showing an example of a screen on which the designation of extraction conditions and the extraction results are displayed on the verification input screen. [Figure 32] FIG. 32 is a diagram showing an example of a screen displayed after the extraction result is selected on the comparison input screen. [Figure 33] FIG. 33 is a diagram showing an example of the verification input screen after the amount has been adjusted. [Figure 34] FIG. 34 is a diagram showing an example of sales data and deposit data before the verification input process. [Figure 35] FIG. 35 is a diagram showing an example of sales data and deposit data after the verification input process. [Figure 36] FIG. 36 is a diagram showing an example of the matching result data after the matching input process. DETAILED DESCRIPTION OF THE INVENTION

[0012] A business support device according to an embodiment of the present invention will be described in detail below with reference to the drawings. As an example, the business support device according to this embodiment is a business support device operated by a person in charge at the headquarters of a company that operates a store network. Companies that operate a store network require the headquarters to collect cash when cash sales are made at stores. The business support device according to this embodiment is a device that supports business operations by enabling automatic reconciliation of sales information and deposit information for multiple days. Note that the present invention is not limited to the following embodiment, which is described as an example.

[0013] (overview) Companies that operate store operations require headquarters to collect cash from cash sales made at stores. This cash collection process generally has set rules for depositing the cash the day after the sales date, but due to store and bank holidays, the cash is not always deposited on the scheduled date, and a reconciliation operation such as sales date: deposit date = N items: M items is required. This means that headquarters staff have to perform tedious checks to verify whether the cash has been deposited correctly, which places a heavy burden on the work.

[0014] Furthermore, when a company engaged in store development expands its business and increases the number of stores, the reconciliation and settlement processes are carried out by limited personnel at headquarters, which places a heavy workload on the company and makes it prone to errors.

[0015] Therefore, companies that operate stores manage bank holidays and holidays for each store (business type, region) in advance in a master file, and store-wide payment schedules are maintained in the system. This allows companies that operate stores to automatically reconcile sales information and payment information for multiple days by reconciling with the scheduled payment date and payment date before the specified base date, even when the sales date and payment date differ (e.g., sales date: payment date = N items: M items). This reduces the workload of the person in charge.

[0016] When importing store sales data, the business support device of the embodiment calculates the expected deposit date for the sales data based on the store holiday calendar master and the bank calendar master. Next, the business support device of the embodiment performs automatic matching for the sales data and deposit data, targeting data that is before the specified base date for the expected deposit date for the sales data and the deposit date for the deposit data. Furthermore, the business support device of the embodiment allows the person in charge to manually perform N:M (N and M are natural numbers) matching on the input screen for sales data and deposit data that were not matched by automatic matching.

[0017] This makes it possible to automatically match and reconcile sales data with deposit data, reducing the workload of staff and improving efficiency.

[0018] (Hardware configuration) FIG. 1 is a block diagram showing the hardware configuration of a task assistance device 1 according to an embodiment. As shown in FIG. 1, the task assistance device 1 according to 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 may be a display unit such as a monitor (including a home television), a printer, or a speaker. The input device 6 may be a keyboard, a mouse, a microphone, or a monitor that cooperates with a mouse to provide a pointing device function. The communication interface unit 4 is connected to a network, such as a wide area network (WLAN) or a private network such as a local area network (LAN).

[0019] For example, a storage device such as a ROM (Read Only Memory), RAM (Random Access Memory), HDD (Hard Disk Drive), or SSD (Solid State Drive) can be used as the storage unit 2. The storage unit 2 stores a business support program that enables automatic matching and settlement of sales data and deposit data, reducing the workload of staff and improving business efficiency.

[0020] The storage unit 2 also has a sales data storage unit 20, a deposit data storage unit 21, and a matching result data storage unit 22, which are storage areas. The storage unit 2 also stores various master data such as a store holiday calendar master 11, a district master 12, a store master 13, a target category master 14, a target day category master 15, a business type master 16, a bank calendar master 17, a store holiday category master 18, and a day of the week category master 19.

[0021] Furthermore, the sales data storage unit 20 stores sales data, the deposit data storage unit 21 stores deposit data, and the matching result data storage unit 22 stores matching result data.

[0022] As shown in Figure 9, the store closure calendar master 11 registers the target category, area code, business type code, store code, target day category, date (year, month, day) of the target day category, day of the week category, and holiday category, each associated with the others.

[0023] The target category indicates the stores that are the subject of the registered holiday calendar, the district in which the stores are located, the type of store, etc. The target category "0: All stores" indicates that the holiday calendar registered in the store holiday calendar master 11 is a holiday calendar that applies to all stores.

[0024] In addition, the target category "1: Area" indicates that the holiday calendar registered in the store holiday calendar master 11 is a holiday calendar for stores in the area indicated by the area code. Figure 9 is an example in which a holiday calendar for stores in "010: Gunma area" is registered.

[0025] In addition, the target category of "2: business type" indicates that the holiday calendar registered in the store holiday calendar master 11 is a holiday calendar for stores of the business type indicated by the business type code. Figure 9 is an example where a holiday calendar for a "1: directly managed" store is registered.

[0026] In addition, the target category "3: Store" indicates that the holiday calendar registered in the store holiday calendar master 11 is a holiday calendar for the store indicated by the store code. Figure 9 shows an example in which holiday calendars for stores "0001: Isesaki Store" and "0002: Maebashi Store" are registered.

[0027] The target day category is a category that indicates the registration format for either a date or a day of the week for holidays. Figure 9 shows an example in which the registration format "0: Year / Month / Date" is set for stores in the target categories of "0: All Stores," "1: Area," and "3: Store." In this case, a holiday date such as "January 1, 2022 (Saturday)" or "July 1, 2022 (Friday)" is registered in the date (year / month / day) input field for the target day category. Figure 9 also shows an example in which the registration format "1: Day of the Week" is set for stores in the target category of "2: Business Type." In this case, a holiday day such as "2: Tuesday" is registered in the input field for the day of the week category.

[0028] The holiday category indicates whether the date (year, month, and day) in the target date category, or the date or day of the week registered in the day of the week category, corresponds to a store's closed day, or corresponds to a store's open day. The example in Figure 9 indicates that "Saturday, January 1, 2022" is a closed day for all stores. The example in Figure 9 also indicates that "Friday, July 1, 2022" is a closed day for stores in the Gunma area. The example in Figure 9 also indicates that directly managed stores are closed every Tuesday. The example in Figure 9 also indicates that "Tuesday, January 4, 2022" is a business day for the Isesaki store. The example in Figure 9 also indicates that "Friday, July 1, 2022" is a closed day for the Maebashi store.

[0029] Next, the district code and district name of each district are registered in the district master 12, as shown in Fig. 10. In the example of Fig. 10, the district code of the "Gunma district" is registered in the district master 12 as "010", and the district code of the "Tokyo district" is registered in the district master 12 as "020".

[0030] Next, the store master 13 stores store data in which store codes, store names, district codes, business categories, etc. are associated with each other, as shown in Fig. 11. The example in Fig. 11 shows that the "Isesaki store" with store code "0001" is a directly managed store (1: directly managed) and belongs to the Gunma area with district code "010." Also, the "Ginza store" with store code "0003" is a franchise store (2: FC) and belongs to the Tokyo area with district code "020."

[0031] Next, the target category master 14 has target categories and target category names registered in association with each other, as shown in Figure 12. In the example of Figure 12, a target category of "0" indicates that the target category name is "all stores" and all stores are the target. A target category of "1" indicates that the target category name is "district" and stores belonging to the specified district are the target. A target category of "2" indicates that the target category name is "business type" and stores of the specified business type are the target. A target category of "3" indicates that the target category name is "store" and specified stores are the target.

[0032] Next, the target date division master 15 has target divisions and target date division names registered in association with each other, as shown in Figure 13. In the example of Figure 13, a target division of "0" indicates that the target division name is "year, month, day" and that the specifically set year, month, day is the target. A target division of "1" indicates that the target division name is "day of the week" and that the specified day of the week is the target.

[0033] Next, in the business type master 16, business type codes and business type names are registered in association with each other, as shown in Fig. 14. In the example of Fig. 14, the target category "1" indicates that the target category name is "directly managed" and that directly managed stores are the target. The target category "2" indicates that the target category name is "FC" and that franchise stores are the target.

[0034] Next, as shown in Figure 15, the bank calendar master 17 has registered therein date, day of the week, and holiday classification, each associated with the other. In the example of Figure 15, specific dates on which the bank will be closed, such as "2022 / 1 / 1" and "2022 / 1 / 2," are registered as the date of the year, month, and day. As for the day of the week, the day of the week corresponding to the year, month, and day is registered, for example, "Saturday" if the year, month, and day is "2022 / 1 / 1." As for the holiday classification, "1: Holiday," which indicates that the related date and day of the week, for example, the date "2022 / 1 / 1" and the weekday "Saturday," are bank holidays.

[0035] Next, the store holiday category master 18 has store holiday categories and store holiday category names registered in association with each other, as shown in Fig. 16. In the example of Fig. 16, a store holiday category of "0" indicates that the store holiday category name is "business day" and that the store is open. A store holiday category of "1" indicates that the store holiday category name is "holiday" and that the store is closed.

[0036] Next, in the day of the week division master 19, day of the week divisions and day of the week names are registered in association with each other, as shown in Fig. 17. In the example of Fig. 17, day of the week divisions "0" to "6" are registered in association with the day of the week names "Sun" to "Sat", respectively.

[0037] (Functional configuration of business support device) Next, the control unit 3 executes the business support program stored in the memory unit 2, thereby functioning as an acquisition unit 31, an extraction unit 32, a reconciliation processing unit 33, an adjustment unit 34, a business day confirmation unit 35, a bank confirmation unit 36, and a registration unit 37, as shown in Fig. 1. Note that while the acquisition unit 31 to the registration unit 37 will be described as being realized by software using the business support program, some or all of the acquisition unit 31 to the registration unit 37 may also be realized by hardware. In either case, the same effects as those described below can be obtained.

[0038] The acquisition unit 31 acquires records containing the same store identification information from the sales data (including store identification information, sales date, voucher number, sales amount, reconciliation amount, and expected deposit date) in the sales data storage unit 20 and the deposit data (including store identification information, deposit date, voucher number, deposit amount, and reconciliation amount) in the deposit data storage unit 21.

[0039] The extraction unit 32 extracts records containing a scheduled deposit date that is before a predetermined base date and a sales amount related to the scheduled deposit date from the acquired sales data containing the same store identification information. The extraction unit 32 also extracts records containing a deposit date that is before a predetermined base date and a deposit amount related to the deposit date from the acquired deposit data containing the same store identification information.

[0040] The reconciliation processing unit 33 compares the extracted sales data record with the extracted deposit data record. If the comparison results in a match between the sales amount in the sales data and the deposit amount in the deposit data, the reconciliation processing unit 33 registers the matched sales amount and deposit amount as the reconciliation amount for the sales data and the deposit data, and performs reconciliation processing.

[0041] Next, the reconciliation processing unit 33 calculates the total sales amount of the sales data and the total deposit amount of the deposit data, excluding any matching sales data and deposit data. If the total sales amount and the total deposit amount match, the reconciliation processing unit 33 compares the extracted sales data record with the extracted deposit data record. The reconciliation processing unit 33 allocates the deposit amounts associated with the deposit dates of the extracted deposit data in chronological order of the oldest deposit date to the oldest sales dates included in the sales data. The reconciliation processing unit 33 registers the deposit amount allocated to the sales data as the reconciliation amount of the sales data and performs the reconciliation processing. Furthermore, the reconciliation processing unit 33 registers the deposit amount allocated to the deposit data as the reconciliation amount and performs the reconciliation processing.

[0042] Next, the reconciliation processing unit 33 registers the slip identification information and line numbers in chronological order of the sales date in the matching result data (including sales identification information, line number, deposit number, line number, and reconciliation amount) stored in the matching result data storage unit 22. The reconciliation processing unit 33 generates matching result data by registering the slip numbers, line numbers, and reconciliation amounts in chronological order of the deposit dates on which the reconciliation process corresponding to the registered slip identification information and line numbers was performed.

[0043] Upon receiving instructions from the person in charge, the adjustment unit 34 displays the verification input screen on the output device 7. The person in charge specifies store identification information on the verification input screen. Furthermore, the person in charge specifies extraction conditions for the expected payment date, sales date, and payment date as necessary, and operates the display button.

[0044] The adjustment unit 34 extracts sales data and deposit data containing unreconciled amounts from the sales data and deposit data containing the specified store identification information and the specified extraction conditions, and displays the extracted sales data and deposit data on the verification input screen.

[0045] The person in charge performs an operation to specify the items to be cleared from the sales data and deposit data displayed on the matching input screen. The adjustment unit 34 adds up the sales amounts of the specified sales data and displays this as the total cleared amount this time on the sales data side of the matching input screen. The adjustment unit 34 also adds up the deposit amounts of the specified deposit data and displays this as the total cleared amount this time on the deposit data side of the matching input screen. The adjustment unit 34 also subtracts the total cleared amount of deposits from the total cleared amount of sales and displays the result of the subtraction on the matching input screen. The adjustment unit 34 subtracts the total cleared amount of deposits from the total cleared amount of sales, and if the result of the subtraction is "0," the person in charge can register the cleared amount by operating the register button. If the result of the subtraction is other than "0," the adjustment unit 34 displays an error message when the person in charge operates the register button, and prompts the person in charge to adjust the amount.

[0046] When the person in charge operates the registration button, the adjustment unit 34 registers the write-off amount specified in the sales data and deposit data and performs the write-off process. The adjustment unit 34 registers the slip identification information and line numbers in the matching result data in chronological order of the oldest sales date. The adjustment unit 34 generates the matching result data by registering the slip numbers, line numbers, and write-off amounts in chronological order of the deposit dates on which the write-off process corresponding to the registered slip identification information and line numbers was performed.

[0047] The business day confirmation unit 35 adds one day to the sales date included in the sales data and sets the date as the expected deposit date for the sales data. The business day confirmation unit 35 references the store holiday calendar master 11, which defines the store's holiday days in the memory unit 2, to confirm whether the expected deposit date is a business day or a holiday. The order of priority when the business day confirmation unit 35 references the store holiday calendar master 11 is as shown in B of Figure 5. The detailed calculation logic for calculating the expected deposit date is as shown in Figures 7 and 8.

[0048] The business day confirmation unit 35 refers to the store holiday calendar master 11, and if the acquired holiday category is a holiday, it adds one day to the calculated expected deposit date to set the new expected deposit date. The business day confirmation unit 35 again refers to the store holiday calendar master 11 in the order shown in B of Figure 5 with the new expected deposit date. The business day confirmation unit 35 repeats the process of setting the new expected deposit date and checking whether it is a business day or a holiday until the acquired holiday category becomes a business day. This process by the business day confirmation unit 35 is as shown in C of Figure 6.

[0049] The bank confirmation unit 36 refers to the bank calendar master 17 based on the expected deposit date determined by the business day confirmation unit 35, and confirms whether the expected deposit date is a bank business day or a bank holiday.

[0050] If the scheduled deposit date is confirmed to be a business day, the bank confirmation unit 36 sets this scheduled deposit date as the new one. If the scheduled deposit date is confirmed to be a holiday, the bank confirmation unit 36 adds one day to the scheduled deposit date and sets a new scheduled deposit date. The bank confirmation unit 36 causes the business day confirmation unit 35 to perform the confirmation process again on the new scheduled deposit date. If the new scheduled deposit date is confirmed to be a business day, the bank confirmation unit 36 again refers to the bank calendar master 17 to confirm whether the scheduled deposit date is a business day or a holiday, and if it is a business day, sets this scheduled deposit date as the new one. Until the scheduled deposit date is confirmed to be a business day, the bank confirmation unit 36 adds one day to the scheduled deposit date, sets a new scheduled deposit date, and repeats the confirmation process of the business day confirmation unit 35 and the bank confirmation unit 36. This process by the bank confirmation unit 36 is as shown in Figure 6D.

[0051] The registration unit 37 registers the expected date of deposit determined by the bank confirmation unit 36 in the sales data.

[0052] (Operation of the embodiment) Next, the process from the store holiday calendar master registration process (step S1) to the matching input process (step S5) in the business support device 1 of this embodiment having the above configuration will be described. FIG. 2 is a diagram showing the flow of the store holiday calendar master registration process (step S1) to the matching input process (step S5) executed by the business support device of this embodiment. The control unit 3 of the business support device 1 of this embodiment executes the business support program stored in the memory unit 2, thereby functioning as an acquisition unit 31, extraction unit 32, reconciliation processing unit 33, adjustment unit 34, business day confirmation unit 35, bank confirmation unit 36, and registration unit 37, and executes the store sales data import process of step S2 shown in FIG. 2, determining the expected deposit date and registering it in the sales data, and the automatic matching process of step S4 through the matching input process of step S5.

[0053] (Step S1: Store holiday calendar master registration process) First, as a premise, the person in charge sets up the store holiday calendar master 11 that manages store holiday days on a setting screen (not shown) for the store holiday calendar master 11, as shown in Fig. 3. At that time, the control unit 3 refers to the district master 12 shown in Fig. 10, the store master 13 shown in Fig. 11, the target category master 14 shown in Fig. 12, the target day category master 15 shown in Fig. 13, the business type master 16 shown in Fig. 14, the store holiday category master 18 shown in Fig. 16, and the day of the week category master 19 shown in Fig. 17, and has the person set up the data via the setting screen, and registers them in the store holiday calendar master 11.

[0054] (Step S2: Store sales data import process) Next, as a premise, the acquisition unit 31 acquires sales-linked data from the store shown in FIG. 4 and updates the sales data.

[0055] The business day confirmation unit 35 and the bank confirmation unit 36 carry out the processes shown in Figures 5 to 8 to determine the expected sales date. The registration unit 27 registers the determined expected sales date in the sales data.

[0056] For example, in the case of voucher number "TU0001" of the sales data in FIG. 4, as shown in FIG. 18, the business day confirmation unit 35 adds one day to the sales date "2021 / 12 / 31" included in the sales data and sets the expected sales date "2022 / 1 / 1 (Sat)". The business day confirmation unit 35 references the store holiday calendar master 11 shown in FIG. 9 based on "2022 / 1 / 1 (Sat)". The business day confirmation unit 35 confirms that the record in the target category "0" (outside column 1-1) of the store holiday calendar master 11 in FIG. 9 is "1: Holiday".

[0057] Next, the business day confirmation unit 35 adds one day to "2022 / 1 / 1 (Sat)" and sets the expected sales date as "2022 / 1 / 2 (Sun)". The business day confirmation unit 35 references the store holiday calendar master 11 shown in FIG. 9 based on "2022 / 1 / 2 (Sun)". Since this does not correspond to the store holiday calendar master 11 in FIG. 9, the business day confirmation unit 35 determines that it is a business day. Next, the bank confirmation unit 36 references the bank calendar master 17 shown in FIG. 15 based on "2022 / 1 / 2 (Sun)". Then, the bank confirmation unit 36 confirms that the record for "2022 / 1 / 2" (outside column 1-2) in the bank calendar master 17 shown in FIG. 15 indicates "1: Holiday".

[0058] The bank confirmation unit 36 adds one day to "2022 / 1 / 2 (Sun)" and sets "2022 / 1 / 3 (Mon)". The business day confirmation unit 35 references the store holiday calendar master 11 shown in FIG. 9 based on "2022 / 1 / 3 (Mon)", confirms that it does not apply, and determines that it is a business day. Next, the bank confirmation unit 36 references the bank calendar master 17 shown in FIG. 15 based on "2022 / 1 / 3 (Mon)", confirms that it does not apply, and determines that it is a business day. The registration unit 37 registers "2022 / 1 / 3 (Mon)" as the expected deposit date in the record for the sales date "2021 / 12 / 31" in the sales data shown in FIG. 18.

[0059] For example, consider the case of slip number "TU0002" in the sales data of FIG. 4. As shown in FIG. 19, the business day confirmation unit 35 adds one day to the sales date "2022 / 1 / 2" included in the sales data and sets the expected sales date "2022 / 1 / 3 (Mon)." Based on "2022 / 1 / 3 (Mon)," the business day confirmation unit 35 references the store holiday calendar master 11 shown in FIG. 9, confirms that it does not match, and determines that it is a business day. Next, based on "2022 / 1 / 3 (Mon)," the bank confirmation unit 36 references the bank calendar master 17 shown in FIG. 15, confirms that it does not match, and determines that it is a business day. The registration unit 37 registers "2022 / 1 / 3 (Mon)" as the expected deposit date in the record for the sales date "2022 / 1 / 2" in the sales data shown in FIG. 19.

[0060] For example, in the case of voucher number "TU0003" in the sales data of FIG. 4, as shown in FIG. 20, the business day confirmation unit 35 adds one day to the sales date "2022 / 1 / 3" included in the sales data, and sets the expected sales date "2022 / 1 / 4 (Tue)". The business day confirmation unit 35 references the store holiday calendar master 11 shown in FIG. 9 based on "2022 / 1 / 4 (Tue)". "2022 / 1 / 4 (Tue)" corresponds to the record (column 3-1) of target category "2: business type", business type code "1: directly managed", target day category "1: day of the week", day of the week category "2: Tuesday", and holiday category "1: closed" in the store holiday calendar master 11 shown in FIG. 9, and therefore corresponds to a holiday.

[0061] On the other hand, "2022 / 1 / 4 (Tue)" corresponds to the record (column 3-1) of the target category "3: Store," store code "0001: Isesaki Store," target date category "0: Year / Month / Day," year / month / day "2022 / 1 / 4 (Tue)," and holiday category "0: Business Day" in the store holiday calendar master 11 shown in FIG. 9. In this case, the business day confirmation unit 35 uses the record of the target category "3: Store" and store code "0001: Isesaki Store" in the store holiday calendar master 11 shown in FIG. 9, which is set at a finer granularity, and determines that it is a business day. Next, the bank confirmation unit 36 references the bank calendar master 17 shown in FIG. 15 based on "2022 / 1 / 4 (Tue)," confirms that it does not match, and determines that it is a business day. The registration unit 37 registers "2022 / 1 / 4 (Tue)" as the expected deposit date for the record of the sales date "2022 / 1 / 3" in the sales data shown in FIG. 20.

[0062] For example, in the case of voucher number "TU0004" in the sales data of FIG. 4, as shown in FIG. 21, the business day confirmation unit 35 adds one day to the sales date "2022 / 6 / 30" included in the sales data, and sets the expected sales date "2022 / 7 / 1 (Fri)." Based on "2022 / 7 / 1 (Fri)," the business day confirmation unit 35 references the store holiday calendar master 11 shown in FIG. 9. Based on the record (column 4-1) of the target category "1: Area," area code "010: Gunma Area," and holiday category "1: Closed Day" in the store holiday calendar master 11 of FIG. 9, the business day confirmation unit 35 confirms that the store code "0001" in the sales data is included in the area code "010: Gunma Area," and therefore is a closed day.

[0063] Next, the business day confirmation unit 35 adds one day to "2022 / 7 / 1 (Fri)" and sets the expected sales date as "2022 / 7 / 2 (Sat)". The business day confirmation unit 35 references the store holiday calendar master 11 shown in FIG. 9 based on "2022 / 7 / 2 (Sat)". Since this does not correspond to the store holiday calendar master 11 in FIG. 9, the business day confirmation unit 35 determines that it is a business day. Next, the bank confirmation unit 36 references the bank calendar master shown in FIG. 15 based on "2022 / 7 / 2 (Sat)". Then, the bank confirmation unit 36 confirms that the record for "2022 / 7 / 2" (column 4-2) in the bank calendar master 17 shown in FIG. 15 indicates "1: Holiday".

[0064] The bank confirmation unit 36 adds one day to "2022 / 7 / 2 (Sat)" and sets "2022 / 7 / 3 (Sun)". The business day confirmation unit 35 references the store holiday calendar master 11 shown in FIG. 9 based on "2022 / 7 / 3 (Sun)", confirms that it does not apply, and determines that it is a business day. Next, the bank confirmation unit 36 references the bank calendar master 17 shown in FIG. 15 based on "2022 / 7 / 3 (Sun)". Then, the bank confirmation unit 36 confirms that the record for "2022 / 7 / 3" (column 4-3) in the bank calendar master 17 shown in FIG. 15 is "1: Holiday".

[0065] The bank confirmation unit 36 adds one day to "2022 / 7 / 3 (Sun)" and sets "2022 / 7 / 4 (Mon)". The business day confirmation unit 35 references the store holiday calendar master 11 shown in FIG. 9 based on "2022 / 7 / 4 (Mon)", confirms that it does not apply, and determines that it is a business day. Next, the bank confirmation unit 36 references the bank calendar master 17 shown in FIG. 15 based on "2022 / 7 / 4 (Mon)", confirms that it does not apply, and determines that it is a business day. The registration unit 37 registers "2022 / 7 / 4 (Mon)" as the expected deposit date for the record of the sales date "2022 / 6 / 30" in the sales data shown in FIG. 21.

[0066] (Step S3: Deposit data import process) Next, as a premise, the acquisition unit 31 acquires the deposit data from the store shown in FIG. 22 and updates the deposit data.

[0067] (Step S4: Automatic matching process) As shown in Figure 23, the reconciliation processing unit 33 automatically matches data whose "expected deposit date" of sales data and "deposit date" of deposit data are before the matching reference date "Monday, January 3, 2022", and performs the matching in the following steps (1) to (3). (1) Regarding line-level matching, matching of the unapplied amount for each sales line (sales amount - application amount) and the unapplied amount for each receipt line (receipt amount - application amount) (2) For reconciliation by total unit, reconciliation of the total amount of unapplied sales (sales amount - applied amount) and the total amount of unapplied receipts (receipt amount - unapplied amount) (3) Regarding the results of the matching between (1) and (2) above, the data for the reconciliation amount of the sales data, the reconciliation amount of the deposit data, and the matching result data are updated.

[0068] The clearing processing unit 33 automatically executes the processes (1) to (3) at a predetermined time setting. The business support program of the business support device 1 according to the embodiment executes the processes as shown in Fig. 23. For example, when the program is executed at 23:00 every day (when the night processing does not exceed midnight), the program executes the process with the current day of the execution date and time as the base date. Also, when the program is executed at 02:00 every day (when the night processing is executed after 12:00 AM, which means the date will be the next day), the program executes the process with one day subtracted from the execution date and time as the base date.

[0069] The acquisition unit 31 acquires sales data and deposit data that contain the same store code. In this case, the acquisition unit 31 acquires a record that contains the store code "00001" from the sales data. The acquisition unit 31 acquires a record that contains the store code "00001" from the deposit data.

[0070] The extraction unit 32 extracts records containing scheduled deposit dates and sales amounts related to those scheduled deposit dates that are on or before the pre-specified reference date, "Monday, January 3, 2022," from the acquired sales data containing the store code "00001." The extraction unit 32 also extracts records containing deposit dates and deposit amounts related to those deposit dates that are on or before the pre-specified reference date, "Monday, January 3, 2022," from the acquired deposit data containing the store code "00001."

[0071] (1) Matching by item As shown in Figure 24, the reconciliation processing unit 33 refers to the extracted sales data and deposit data and confirms data where the sales amount of "300,000 yen" in the sales data matches the deposit amount of "300,000 yen" in the deposit data, and where the reconciliation processing has not been performed before the reference date of "Monday, January 3, 2022."

[0072] As shown in FIG. 25, the reconciliation processing unit 33 registers "300,000 yen" as the reconciliation amount in the sales data and the deposit data, updates each data, and performs the reconciliation process.

[0073] The reconciliation processing unit 33 registers the sales number "TU0003", row "1", deposit number "TN0003", row "1" and reconciliation amount "300,000 yen" in the matching result data as shown in Figure 25, and updates the matching result data.

[0074] (2) Verification by total unit As shown in Figure 26, the reconciliation processing unit 33 refers to the extracted sales data and calculates "300,000 yen" by adding up the sales amount "100,000 yen" and the sales amount "200,000 yen" for voucher number "TU0001" and voucher number "TU0002", whose expected payment date is before the reference date "Monday, January 3, 2022" and for which reconciliation processing has not been performed.

[0075] Next, as shown in Figure 26, the reconciliation processing unit 33 refers to the extracted deposit data and adds up the deposit amount of "160,000 yen" and the sales amount of "140,000 yen" for voucher number "TN0001" and voucher number "TN0002", whose deposit date is before the reference date "Monday, January 3, 2022" and for which reconciliation processing has not been performed, to calculate "300,000 yen".

[0076] As shown in Figure 27, since the total amounts of the sales data and the deposit data match, the reconciliation processing unit 33 registers and updates the reconciliation amounts of the sales data voucher number "TU0001" and voucher number "TU0002" to "100,000 yen" and "200,000 yen", respectively, and performs the reconciliation process.

[0077] As shown in Figure 27, since the total amounts of the sales data and the deposit data match, the reconciliation processing unit 33 registers and updates the reconciliation amounts of the deposit data slip number "TN0001" and slip number "TN0002" to "160,000 yen" and "140,000 yen", respectively, and performs the reconciliation process.

[0078] The reconciliation processing unit 33 allocates and reconciles "100,000 yen" from "160,000 yen" of deposit number "TN0001" with the oldest deposit date corresponding to sales number "TU0001" in the matching result data, as shown in Figure 28. Therefore, the reconciliation processing unit 33 registers and updates the reconciliation amount "100,000 yen" for sales number "TU0001" in the matching result data.

[0079] The reconciliation processing unit 33 allocates and reconciles the unreconciled "60,000 yen" of the "160,000 yen" of the deposit number "TN0001" with the oldest deposit date corresponding to the sales number "TU0002" in the matching result data, as shown in Figure 28. The reconciliation processing unit 33 further allocates and reconciles the "140,000 yen" of the deposit number "TN0002" with the second oldest deposit date corresponding to the sales number "TU0002" in the matching result data.

[0080] Therefore, the reconciliation processing unit 33 registers and updates the reconciliation amount of "60,000" for deposit number "TN0001" and the reconciliation amount of "140,000 yen" for deposit number "TN0002" corresponding to the two records of sales number "TU0002" in the matching result data, as shown in Figure 28.

[0081] (Step S5: Verification input process) Upon receiving instructions from the person in charge, the adjustment unit 34 displays a verification input screen on the output device 7. As shown in FIG. 29, the person in charge performs the following processing. (1) The person in charge selects the store in the header section of the verification entry screen. (2) If necessary, the person in charge specifies the expected deposit date (range specification) and sales date (range specification) of the sales information extraction conditions, and the deposit date (range specification) of the deposit information extraction conditions, and operates the display button. (3) The person in charge checks the "Subject" checkbox for the details to be cleared that are displayed on the matching input screen.

[0082] The person in charge enters the store code "000001" in the store field on the verification input screen, as shown in FIG.

[0083] The person in charge specifies the expected payment date, sales date, and payment date on the verification input screen as necessary. In this case, the person in charge specifies the expected payment date "2022 / 1 / 3" and the payment date "2022 / 1 / 3" as shown in Figure 31, and operates the display button.

[0084] The adjustment unit 34 refers to the sales data and displays on the matching input screen sales data that was not reconciled before the specified expected deposit date of "2022 / 1 / 3" as shown in Figure 31. The adjustment unit 34 also refers to the deposit data and displays on the matching input screen deposit data that was not reconciled before the specified deposit date of "2022 / 1 / 3".

[0085] The person in charge checks the checkboxes for the sales data and deposit data to be cleared to specify them. As shown in Figure 32, the adjustment unit 34 adds up the sales amounts of the checked sales data and displays this as the total amount to be cleared this time on the matching input screen. The adjustment unit 34 adds up the sales amounts of the checked sales data ("100,000 yen" and "200,000 yen") and displays "300,000 yen" as the total amount to be cleared this time on the sales data side.

[0086] The adjustment unit 34 displays the sum of the deposit amounts of the checked deposit data in the total amount to be applied this time on the matching input screen. As shown in Figure 32, the adjustment unit 34 adds up the deposit amounts of the checked deposit data ("160,000 yen" and "130,000 yen") and displays "290,000 yen" in the total amount to be applied this time on the deposit data side.

[0087] The adjustment unit 34 subtracts the total reconciliation amount of deposits, "290,000 yen," from the total reconciliation amount of sales, "300,000 yen." The adjustment unit 34 displays the subtraction result, "10,000 yen," in the "Total reconciliation amount of sales - total reconciliation amount of deposits" field on the verification input screen, as shown in Figure 32.

[0088] Furthermore, since the "Total sales reconciliation amount - Total deposit reconciliation amount" on the verification input screen is not "0", even if the person in charge operates the registration button, the adjustment unit 34 will not perform the reconciliation process. Note that the adjustment unit 34 may display a message indicating that registration is not possible and prompting the person in charge to adjust the reconciliation amount.

[0089] In response to the error, the person in charge adjusts the total sales write-off amount and the total deposit write-off amount so that they are the same, as shown in Figure 33. The example in Figure 33 shows the person in charge adjusting the current write-off amount of "200,000 yen" for the sales date "2022 / 1 / 2" in the sales data to "190,000 yen."

[0090] The adjustment unit 34 subtracts the total reconciliation amount of deposits "290,000 yen" from the total reconciliation amount of sales "290,000 yen", and displays the result of the subtraction "0 yen" in "Total reconciliation amount of sales - total reconciliation amount of deposits" on the verification input screen, as shown in Figure 33. The person in charge operates the registration button.

[0091] The adjustment unit 34 registers the amount specified by the person in charge as the reconciliation amount for the sales data and deposit data shown in Figure 34, as shown in Figure 35, updates the data, and performs the reconciliation process.

[0092] Next, the adjustment unit 34 allocates an amount to be cleared within the range of amounts specified by the person in charge and updates the matching result data, as shown in Figure 36. The adjustment unit 34 allocates and clears "100,000 yen" from the "160,000 yen" of deposit number "TN0001" with the oldest deposit date corresponding to sales number "TU0001" to the matching result data. Therefore, the clearing processing unit 33 registers and updates the clearing amount "100,000 yen" for sales number "TU0001" in the matching result data.

[0093] The adjustment unit 34 allocates and settles the remaining "60,000 yen" of the "160,000 yen" of the deposit number "TN0001" with the oldest deposit date corresponding to the sales number "TU0002" in the matching result data, as shown in Figure 36. The adjustment unit 34 further allocates and settles the "130,000 yen" of the deposit number "TN0002" with the second oldest deposit date corresponding to the sales number "TU0002" in the matching result data.

[0094] Therefore, the reconciliation processing unit 33 registers and updates the reconciliation amount of "60,000" for deposit number "TN0001" and the reconciliation amount of "130,000 yen" for deposit number "TN0002" corresponding to the two records of sales number "TU0002" in the matching result data, as shown in Figure 36.

[0095] (Effects of the embodiment) As is clear from the above description, the task support device 1 according to the embodiment can achieve the following effects.

[0096] (1) Companies that operate stores can manage the business holidays for each store (business type, region) in advance in master data, and also manage bank holidays in master data, which allows them to determine more accurate expected payment dates and register them in sales data. This enables more accurate automatic reconciliation processing.

[0097] (2) Even if the sales date of the sales data and the deposit date of the deposit data are different, sales information and deposit information for multiple days can be automatically reconciled by matching the expected deposit date of the sales data before the specified base date with the deposit date of the deposit data and performing the reconciliation process. This reduces the amount of manual reconciliation and reconciliation work, significantly reducing the workload of the person in charge.

[0098] (3) The person in charge can specify and perform the settlement process for sales data and deposit data that could not be automatically settled on the matching input screen. Since the settlement registration cannot be made unless the total amount of the sales data to be settled and the total amount of the deposit amount to be settled match, the accuracy of the settlement process by the person in charge can be improved.

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

[0100] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to SDGs Goals 12, 13, and 15.

[0101] Furthermore, this embodiment can contribute to strengthening control and governance, thereby contributing to SDG Goal 16.

[0102] [Other embodiments] The present invention may be implemented in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

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

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

[0105] Furthermore, with regard to the task support device 1, the components shown in the figures are functional concepts, and do not necessarily have to be physically configured as shown in the figures.

[0106] For example, all or any part of the processing functions of the business support device 1, particularly the control unit 3 and each processing function performed by the control unit 3, may be realized by a CPU (Central Processing Unit) and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. 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 this embodiment, and is mechanically read by the business support device 1 as needed. That is, a storage unit such as a ROM or HDD stores a computer program for cooperating with the OS to issue instructions to the CPU and perform various processes. The computer program is executed by being loaded into RAM, and cooperates with the CPU to constitute the control unit 3.

[0107] 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 as needed.

[0108] The business support program for executing the processes described in this embodiment may be stored in a non-transitory computer-readable recording medium or configured as a program product. Here, the term "recording medium" includes any portable physical medium such as a memory card, a Universal Serial Bus (USB) memory, a Secure Digital (SD) card, a flexible disk, a magneto-optical disk, a ROM, an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable and Programmable Read Only Memory (EEPROM (registered trademark)), a Compact Disk Read Only Memory (CD-ROM), a Magneto-Optical Disk (MO), a Digital Versatile Disk (DVD), and a Blu-ray (registered trademark) disc.

[0109] Furthermore, a "program" is a data processing method written in any language or description method, and does not matter whether it is in the form of source code or binary code. Note that a "program" is not necessarily limited to a single structure, but also includes a structure that is distributed as multiple modules or libraries, or a structure that achieves its function by cooperating with a separate program, such as an OS. Note that the specific structure and reading procedure for reading a recording medium in the business support device 1 described in the embodiment, as well as the installation procedure after reading, can use well-known structures and procedures.

[0110] 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, and web page files used for various processes and providing websites.

[0111] 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 realized by installing software (including programs or data) that realizes the processing described in this embodiment.

[0112] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit according to various additions or functional loads. In other words, the above-described embodiments can be implemented in any combination, or embodiments can be implemented selectively. [Industrial Applicability]

[0113] The present invention is suitable for application in supporting the operations of companies, such as retailers with many directly managed stores, whose headquarters checks sales and deposits from stores. [Explanation of symbols]

[0114] 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 Store Closure Calendar Master 12 District Master 13 Store Master 14 Object Category Master 15 Target Date Classification Master 16 Business type master 17 Bank Calendar Master 18 Store Holiday Classification Master 19 Day of the week master 20 Sales data storage section 21 Deposit data storage unit 22 Matching result data storage unit 31 Acquisition Department 32 Extraction part 33 Clearing Processor 34 Adjustment part 35 Business Day Confirmation Department 36 Bank Verification Department 37 Registration Department

Claims

1. an acquisition unit that acquires the sales data and the deposit data, each including the same store identification information, from a storage unit that stores at least sales data including store identification information, a sales amount, a write-off amount, and a scheduled date for depositing the sales amount from the store, and deposit data including the store identification information, the deposit date, the deposit amount, and the write-off amount; an extraction unit that extracts, from the acquired sales data, expected deposit dates before a specified base date and sales amounts related to the expected deposit dates, and extracts, from the deposit data, the deposit dates before the specified base date and the deposit amounts related to the deposit dates; a clearing processing unit that compares the extracted sales data with the extracted deposit data, and if there is deposit data including the deposit amount that matches the sales amount of the sales data, registers the sales amount and the deposit amount that match the clearing amount of the sales data and the deposit data, and performs a clearing process; A business support device comprising:

2. The business support device described in claim 1, characterized in that when there is no deposit data containing the deposit amount that matches the sales amount of the sales data, and when the total of the undeposited sales amounts of the extracted sales data and the total of the undeposited deposit amounts of the extracted deposit data match, the deposit processing unit allocates the deposit amounts in order of the oldest deposit date of the deposit data to the oldest sales date included in the sales data, registers the amounts allocated to the deposit amounts of the sales data and the deposit data, and performs the deposit processing.

3. The system further comprises an adjustment unit that, when the reconciliation processing unit is unable to perform the reconciliation processing for the sales amount and the deposit amount, allows the user to specify the store identification information on a verification input screen, and displays the unreconciled sales data related to the specified store identification information and the unreconciled deposit data related to the specified store identification information on the verification input screen so that the data can be selected and the amount can be changed, thereby enabling adjustment of the reconciliation amount.

3. The business support device according to claim 2.

4. a business day confirmation unit that sets the expected payment date to be the sales date included in the sales data plus one day, and that refers to a store holiday calendar master that defines store holidays included in the storage unit and confirms whether the expected payment date is a business day or a holiday; a bank confirmation unit that, if the confirmation result is that the date is a business day, refers to a bank calendar master in which bank holidays are registered and confirms whether the expected date of deposit is a bank business day or a bank holiday; a registration unit that registers the expected deposit date in the sales data when the bank confirmation unit confirms that the date is a business day; 2. The business support device according to claim 1, wherein:

5. the business day confirmation unit, when confirming that the expected deposit date is a holiday with reference to the store holiday calendar master, sets the date obtained by adding one day to the expected deposit date as the expected deposit date, and then refers to the store holiday calendar master to confirm whether it is a business day or a holiday, and repeats the confirmation process with the date obtained by adding one day to the expected deposit date until it becomes a business day, thereby determining the expected deposit date; 5. The business support device according to claim 4, wherein:

6. when the bank confirmation unit confirms, by referring to the bank calendar master, that the scheduled deposit date is a holiday, the business day confirmation unit determines the scheduled deposit date by adding one day to the scheduled deposit date, and repeats the confirmation process by the business day confirmation unit and the confirmation process by the bank confirmation unit to determine the scheduled deposit date, until it is confirmed that the date is a business day; 6. The business support device according to claim 5,

7. an acquisition step in which an acquisition unit acquires, from a storage unit in which sales data including at least store identification information assigned to each store, a sales amount, a write-off amount, and a scheduled date of deposit of the sales amount from the store, and deposit data including the store identification information, the deposit date, the deposit amount, and the write-off amount, the sales data and the deposit data including the same store identification information; an extraction step in which an extraction unit extracts from the acquired sales data an expected deposit date that is before a specified base date and a sales amount related to the expected deposit date, and extracts from the deposit data an expected deposit date that is before the specified base date and a deposit amount related to the deposit date; a clearing processing step in which a clearing processing unit compares the extracted sales data with the extracted deposit data, and if there is deposit data including the deposit amount that matches the sales amount of the sales data, registers the sales amount and the deposit amount that match the clearing amount of the sales data and the deposit data, and performs a clearing processing; A business support method having the above.

8. Computer, an acquisition unit that acquires the sales data and the deposit data, each including the same store identification information, from a storage unit that stores at least sales data including store identification information, a sales amount, a write-off amount, and a scheduled date for depositing the sales amount from the store, and deposit data including the store identification information, the deposit date, the deposit amount, and the write-off amount; an extraction unit that extracts, from the acquired sales data, expected deposit dates before a specified base date and sales amounts related to the expected deposit dates, and extracts, from the deposit data, the deposit dates before the specified base date and the deposit amounts related to the deposit dates; a clearing processing unit that compares the extracted sales data with the extracted deposit data, and if there is deposit data including the deposit amount that matches the sales amount of the sales data, registers the sales amount and the deposit amount that match the clearing amount of the sales data and the deposit data, and performs a clearing process; A business support program that functions as a

Images