JP7426517B2 - Business support devices, business support programs, and business support methods - Google Patents

Description

The present invention relates to a business support device, a business support program, and a business support method.

Regarding the issuance of invoices in companies, it is common for companies to issue invoices to customers on a closing basis once products have been delivered to the customer and verification has been completed. There are companies that have customers (for example, customers in the construction industry) who give industry-specific instructions such as, ``If we give permission, we will issue invoices.''

Regarding the conventional technology related to issuing a bill, Patent Document 1 describes processing details regarding creation of total bill data (for example, see paragraphs 0047 to 0050).

JP2018-128798A

For companies that have customers who issue the above-mentioned instructions, if the billing deadline is allowed to be changed in response to the request of the billing party and the billing party gives permission to issue an invoice, the billing deadline after the change is granted. In order to improve business efficiency, an information processing means that enables the issuance of invoices is required, but such information processing means have not existed in the past.

The present invention has been made in view of the above, and allows the billing deadline to be changed in response to a request from the billing party, and when permission to issue an invoice is granted from the billing party, the billing deadline after the change is made. The purpose is to provide a business support device, a business support program, and a business support method that enable the issuance of invoices.

In order to solve the above-mentioned problems and achieve the purpose, a business support device according to the present invention is a business support device including a control unit, wherein the control unit is configured to collect data from a billing data storage unit and a collection schedule data storage unit. , extracts the billing data associated with the specified billing party for whom permission to issue an invoice was not obtained and the collection schedule data associated with the billing data, and extracts the billing cut-off date included in the extracted billing data and the extracted collection. The scheduled collection date included in the schedule data is output to the screen displayed on the display unit, and when the billing deadline is changed on the screen, the billing deadline of the extracted billing data is changed to the billing deadline after the change. and changing the scheduled collection date of the extracted collection scheduled data to the scheduled collection date derived according to a predetermined rule regarding the changed billing deadline and timing of billing and collection; From the billing data storage section, billing data that is linked to a designated billing party who has been given permission to issue a bill and whose billing deadline falls within a predetermined year and month is extracted, and based on the extracted billing data, the specified billing address is and creating means for creating bill data regarding bills for years and months.

Further, the business support program according to the present invention causes the information processing device including the control unit to request a request from the billing data storage unit and the collection schedule data storage unit to be associated with a specified billing party for which permission to issue an invoice has not been obtained. Extract the data and collection schedule data linked to the billing data, and output the billing closing date included in the extracted billing data and the scheduled collection date included in the extracted collection schedule data to the screen displayed on the display unit. However, when the billing deadline date is changed on the screen, the billing deadline date of the extracted billing data will be changed to the billing deadline date after the change, and the scheduled collection date of the extracted collection schedule data will be changed to the billing deadline date of the extracted billing data. A changing means for changing the billing due date and a scheduled collection date derived in accordance with predetermined rules regarding billing and collection timing; Functions as a creation means that extracts billing data that is linked and has a billing cut-off date that corresponds to a predetermined year and month, and creates bill data regarding bills for the predetermined year and month based on the extracted billing data. It is for.

Further, in the business support method according to the present invention, the control section of the information processing device including the control section executes the task support method for the specified case where permission to issue an invoice has not been obtained from the billing data storage section and the collection schedule data storage section. Extracts the billing data linked to the billing party and the collection schedule data linked to the billing data, and displays the billing closing date included in the extracted billing data and the scheduled collection date included in the extracted collection schedule data on the display. When the billing deadline is changed on the screen, the billing deadline of the extracted billing data is changed to the billing deadline after the change, and the billing deadline of the extracted collection schedule data is changed. a changing step of changing the scheduled collection date to a scheduled collection date derived according to the changed billing cutoff date and predetermined rules regarding billing and collection timing; and obtaining permission to issue a bill from the billing data storage unit. Extract billing data that is linked to the designated billing party and whose billing cut-off date falls within a predetermined year and month, and create billing data regarding the bill for the predetermined year and month based on the extracted billing data. The method includes a step of creating the image.

The present invention allows the billing deadline to be changed in response to a request from the billing party, and when the billing party gives permission to issue an invoice, the bill can be issued on the changed billing deadline. be effective.

FIG. 1 is a diagram showing an example of the content of billing data that is the basis of a bill for July 2018 that could not be issued because permission was not obtained from the billing party. FIG. 2 is a diagram showing an example of billing data that is the basis of a bill for August 2018 that can be issued because permission has been granted from the billing party. FIG. 3 is a diagram illustrating an example of the content of the billing data that is the basis of the bill for August 2018, assuming that the bill for July 2018 has been issued. FIG. 4 is a diagram showing an example of the configuration of the business support device. FIG. 5 is a diagram illustrating an example of a business flow and a processing flow. FIG. 6 is a diagram showing an example of created billing data and collection schedule data. FIG. 7 is a diagram showing an example of a change input screen. FIG. 8 is a diagram showing an example of changed billing data and collection schedule data. FIG. 9 is a diagram showing an example of created billing data and collection schedule data. FIG. 10 is a diagram illustrating an example of billing data creation status. FIG. 11 is a diagram showing an example of an issued bill.

Embodiments of a business support device, a business support program, and a business support method according to the present invention will be described in detail below based on the drawings. Note that the present invention is not limited to this embodiment.

[1. overview]
An overview of this embodiment will be described with reference to FIGS. 1 to 3. FIG. 1 is a diagram showing an example of the content of billing data that is the basis of a bill for July 2018 that could not be issued because permission was not obtained from the billing party. FIG. 2 is a diagram showing an example of billing data that is the basis of a bill for August 2018 that can be issued because permission has been granted from the billing party. FIG. 3 is a diagram illustrating an example of the content of the billing data that is the basis of the bill for August 2018, assuming that the bill for July 2018 has been issued.

For example, a request for 1 million yen was made to billing party A for a bill due in July 2018, but the bill could not be issued in July because billing party A did not give permission to issue the invoice. (See Figure 1). Then, in August, the next month, there is a bill for 1.2 million yen, and at this time, billing party A gives permission to issue the bill, so the bill is billed for July and August together (see Figure 2). Here, if the billing for July was done as scheduled, the billing amount for July would be set as the billing amount for the previous month in the billing data for August, so the billing data for August shown in Figure 3 would be set as the billing amount for the previous month. An invoice will be issued based on this. This embodiment provides a mechanism that can create bill data based on bill data for August shown in FIG. 2. Note that sales results are generated in July and August, respectively, without being affected by billing information. In addition, regarding the collection schedule based on the predetermined rules regarding billing and collection timing such as "billing at the end of the current month and collection at the end of the following month," the collection schedule data corresponding to the billing data for August shown in Figure 3 is However, the scheduled collection data corresponding to the August billing data shown in Figure 2 is "September collection: 2.2 million yen." .

[2. composition]
An example of the configuration of the business support device according to this embodiment will be described with reference to FIG. 4 and the like. FIG. 4 is a block diagram showing an example of the configuration of the business support device.

The business support device 100 is a commercially available desktop personal computer. Note that the business support device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may also be a portable type such as a commercially available notebook personal computer, a PDA (Personal Digital Assistant), a smartphone, or a tablet personal computer. It may also be an information processing device.

The business support device 100 includes a control section 102, a communication interface section 104, a storage section 106, and an input/output interface section 108. Each part included in the business support device 100 is communicably connected via an arbitrary communication path.

The communication interface unit 104 communicatively connects the business support device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via a communication line. Here, the network 300 has a function of connecting the business support device 100 and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network). Note that the data stored in the storage unit 106 (for example, billing data, collection schedule data, bill data, etc., which will be described later) may be stored in the server device 200, for example.

An input device 112 and an output device 114 are connected to the input/output interface unit 108 . As the output device 114, in addition to a monitor (including a home television), a speaker or a printer can be used. As the input device 112, in addition to a keyboard, a mouse, and a microphone, a monitor that cooperates with the mouse to realize a pointing device function can be used. Note that in the following description, the output device 114 may be referred to as a monitor 114, and the input device 112 may be referred to as a keyboard 112 or a mouse 112.

The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 stores a computer program for giving instructions to a CPU (Central Processing Unit) to perform various processes in cooperation with an OS (Operating System). As the storage unit 106, for example, a memory device such as a RAM (Random Access Memory) or a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, etc. can be used.

The storage unit 106 includes a billing data storage unit 106a, a collection schedule data storage unit 106b, and the like. Note that the storage unit 106 may include a bill data storage unit 106c for storing bill data created by a creation unit 102c, which will be described later.

The billing data includes, for example, billing identification information (e.g., billing number to uniquely identify the billing data), billing party identification information (eg, billing party code to uniquely identify the billing party), creation date (billing date of data creation), billing cut-off date (date of billing deadline), previous month's billing amount (amount billed in the previous month), current month's payment amount (amount deposited in the current month), current month's sales amount ( This includes data regarding the amount recorded in sales for the current month) and the amount billed for the current month (the amount billed for the current month).

Collection schedule data includes, for example, collection schedule identification information (e.g., collection schedule number to uniquely identify collection schedule data), billing identification information, creation date (year, month, and day when collection schedule data was created), and collection schedule date. (Example: Scheduled collection date determined based on predetermined rules regarding billing and collection timing such as "bill at the end of the current month / collection at the end of the following month"), collection method (example: transfer payment), scheduled collection amount (planned collection date) Contains data regarding such things as monetary amounts).

Invoice data includes, for example, invoice identification information (e.g. invoice number to uniquely identify invoice data), issue date (e.g. year, month and day the invoice was issued), previous invoice amount, and current month. Contains data on deposit amount, amount accrued in the current month, amount billed at the end of the month, etc.

The control unit 102 is a CPU or the like that controls the business support device 100 in an integrated manner. The control unit 102 has an internal memory for storing control programs such as an OS, programs specifying various processing procedures, required data, etc., and performs various information processing based on these stored programs. Execute.

Functionally, the control unit 102 includes a billing processing unit 102a, a changing unit 102b, and a creation unit 102c.

The bill processing unit 102a performs information processing related to bill processing operations, including creation of bill data and collection schedule data.

The changing unit 102b allows the operator to change the billing party (for example, billing party code) for which permission to issue an invoice has not been obtained on the change input screen (see FIG. 7) displayed on the monitor 114 (corresponding to the display unit of the present invention). , and the billing data associated with the specified billing destination and the collection schedule data associated with the billing data are extracted from the billing data storage unit 106a and the collection schedule data storage unit 106b. The change unit 102b outputs the billing cut-off date included in the extracted billing data and the scheduled collection date included in the extracted scheduled collection data to the change input screen. When the billing deadline is changed on the change input screen, the changing unit 102b changes the billing deadline of the extracted billing data to the changed billing deadline, and changes the collection schedule of the extracted collection schedule data. The date is changed to the billing cut-off date after the change and the scheduled collection date derived according to the predetermined rules regarding billing and collection timing (e.g., billing at the end of the current month and collection at the end of the following month).

The creation unit 102c allows the operator to specify a billing party (for example, a billing party code) for which permission has been given to issue a bill on the billing screen (not shown) displayed on the monitor 114, and stores the billing data storage unit 106a. From there, billing data that is linked to the designated billing party and whose billing cut-off date falls within a predetermined year and month (for example, the current year and month or the year and month specified on the bill issuance screen) is extracted. The creation unit 102c creates bill data regarding the bill for the predetermined year and month based on the extracted bill data. Specifically, the creation unit 102c adds (1) the previous month's billing amount of billing data other than the billing data whose creation date corresponds to the predetermined year and month among the extracted billing data to the previous billing amount of the billing data. (2) set the total amount of the extracted billing data for the current month in the current month's received amount of the billing data, and (3) set the extracted billing data as the current month's accrued amount of the billing data. (4) Set the current month's billing amount of the billing data whose creation date corresponds to the specified year and month among the extracted billing data to the billing amount at the end of the month of the billing data. . The creation unit 102c prints an invoice via a printer, which is an example of the output device 114, based on the created invoice data (see FIG. 11).

[3. process]
Here, an example of a business flow and a process executed by the business support device 100 will be described with reference to FIG. 5 and the like.

[Step S1: End of July 2018 closing billing process]
The operator inputs necessary information into the billing process screen (not shown) displayed on the monitor 114 in order to carry out the billing process (billing confirmation process) for billing party X for the end of July 2018.
The billing processing unit 102a creates billing data (creation date: July 31, 2018) and collection schedule data (creation date: July 31, 2018) for the end of July 2018 based on the input information. Then, the created billing data is stored in the billing data storage unit 106a, and the created collection schedule data is stored in the collection schedule data storage unit 106b (see FIG. 6). For the sake of brevity, it is assumed that no deposit is made. It is also assumed that no consumption tax will be generated. Regarding the collection schedule, collection will be at the end of the month following the closing date.

[Step S2: Change the billing deadline to the next month/end of August 2018]
The operator displays a change input screen MA on the monitor 114 to change the dates of the billing data and collection schedule data created in step S1 because the operator did not receive permission to issue an invoice due at the end of July 2018 from billing party X. and enters the identification number of the billing party X in the input field for specifying the billing party provided on the change input screen MA (see FIG. 7).
The changing unit 102b extracts billing data associated with the input identification number from the billing data storage unit 106a, and extracts collection schedule data associated with the billing data from the collection schedule data storage unit 106b (Fig. 6 reference).
The change unit 102b outputs the billing deadline date included in the extracted billing data and the scheduled collection date included in the extracted scheduled collection data to the change input screen MA (see FIG. 7).
The operator changes the billing deadline date of July 31, 2018, which is output on the change input screen MA, to August 31, 2018, to change the billing date to the billing deadline of the end of August 2018.
The changing unit 102b changes the claim closing date (July 31, 2018) of the extracted claim data to the changed claim closing date (August 31, 2018). In addition, the change unit 102b updates the new collection according to the changed billing deadline (August 31, 2018) and predetermined rules regarding billing and collection timing such as "collection will be made at the end of the month following the closing." The scheduled date (September 30, 2018) is derived, and the scheduled collection date of the extracted collection scheduled data is changed to the derived scheduled collection date.
As a result of the process in step S2, the extracted billing data and collection schedule data change from the state shown in FIG. 6 to the state shown in FIG. 8 (however, the creation date remains unchanged as July 31, 2018).

Please note that we will not issue an invoice for the end of July 2018 because we did not receive permission from billing party X to issue an invoice for the end of July 2018.

[Step S3: End of August 2018 closing billing process]
The operator inputs necessary information into the billing process screen (not shown) displayed on the monitor 114 in order to carry out the billing process (billing confirmation process) for billing party X for the end of August 2018.
The billing processing unit 102a creates billing data (creation date: August 31, 2018) and collection schedule data (creation date: August 31, 2018) for the end of August 2018 based on the input information. Then, the created billing data is stored in the billing data storage unit 106a, and the created collection schedule data is stored in the collection schedule data storage unit 106b (see FIG. 9).

Furthermore, since permission to issue an invoice due at the end of August 2018 has been obtained from billing party X, the billing deadline will not be changed.

[Step S4: Issuance of invoice due at the end of August 2018]
Since the operator has received permission from billing party X to issue an invoice due at the end of August 2018, the operator requests billing party X to issue an invoice due at the end of August 2018 based on the billing data that has already been created. A bill issuance screen (not shown) is displayed on the monitor 114, and the identification number of billing party X is entered in an input field for specifying a billing party provided on the bill issuing screen.
The creation unit 102c extracts, from the claim data storage unit 106a, claim data that is associated with the input identification number and whose claim closing date corresponds to the current month and year of August 2018 (see FIG. 10).
The creation unit 102c creates bill data regarding the bill for August 2018 (issue date: August 31, 2018) based on the extracted bill data. Specifically, the creation unit 102c (1) sets the previous month's billing amount of the extracted billing data of billing number: A00001 to the previous billing amount of the billing data, and (2) sets the current month's paid amount of the billing data. , set the total amount received for the current month of the extracted billing data of billing numbers A00001 and A00002, and (3) set the current month amount of the extracted billing data of billing numbers A00001 and A00002 to the current month's accrual amount of the billing data. Set the total sales amount, and (4) set the billing amount for the current month in the billing data of the extracted billing number: A00002 as the billing amount at the end of the month in the billing data.
The creation unit 102c prints a bill MB via a printer based on the created bill data (see FIG. 11).

As described above, according to this embodiment, when the billing date is allowed to be changed in response to the billing party's request and the billing party gives permission to issue an invoice, the billing date is changed and the billing date is changed. is now possible. In particular, according to this embodiment, a closing request form can be issued at any timing. Here, (1) whether or not to issue an invoice is not information that can be determined by the person entering the sales at the sales entry stage, such as at the end of the book, but information that is provided by the billing party immediately before issuing the invoice. , and (2) Unlike billing each time, it is necessary to print information such as the previous billing amount and the month-end billing amount on the issued bill. Although it is necessary to take measures such as shifting to the next month, which is not normally done, this embodiment makes this possible.

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

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 of the processes described as being performed manually can be performed manually. Alternatively, some of the steps can be performed automatically using known methods.

In addition, unless otherwise specified, information including processing procedures, control procedures, specific names, parameters such as registered data and search conditions for each process, screen examples, and database configurations shown in this specification and drawings are included. It can be changed arbitrarily.

Further, regarding the business support device 100, each illustrated component is functionally conceptual, and does not necessarily need to be physically configured as illustrated.

For example, the processing functions provided in the business support device 100, especially each processing function performed by the control unit, may be realized in whole or in part by a CPU and a program interpreted and executed by the CPU. Alternatively, it may be implemented as hardware using wired logic. Note that the program is recorded on a non-temporary computer-readable recording medium that includes programmed instructions for causing the information processing device to execute the processing described in this embodiment. Machine read to 100. That is, a storage unit such as a ROM or an HDD (Hard Disk Drive) stores a computer program that cooperates with an OS to give instructions to a CPU and perform various processes. This computer program is executed by being loaded into the RAM, and constitutes a control unit in cooperation with the CPU.

Further, this computer program may be stored in an application program server connected to the business support device 100 via an arbitrary network, and it is also possible to download all or part of it as necessary. be.

Further, a program for executing the processing described in this embodiment may be stored in a non-temporary computer-readable recording medium, or may be configured as a program product. Here, this "recording medium" includes 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), and an EEPR. OM (registration) Trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROM (Compact Disk Read Only Memory), MO (Magneto-Optical disk), DVDs (Digital Versatile Discs), Blu-ray (registered trademark) Discs, etc. shall include any “portable physical medium”.

Further, a "program" is a data processing method written in any language or writing method, and does not matter in the form of source code or binary code. Note that a "program" is not necessarily limited to a unitary structure, but may be distributed as multiple modules or libraries, or may work together with separate programs such as an OS to achieve its functions. Including things. Note that well-known configurations and procedures can be used for the specific configuration and reading procedure for reading the recording medium in each device shown in the embodiments, and the installation procedure after reading.

The various databases stored in the storage unit are storage devices such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and are used for various processing and website provision. Stores programs, tables, databases, web page files, etc.

Further, the business support device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device to which any peripheral device is connected. Further, the business support device 100 may be implemented by installing software (including programs, data, etc.) that causes the device to implement the processing described in this embodiment.

Furthermore, the specific form of dispersion and integration of devices is not limited to what is shown in the diagram, and all or part of them can be functionally or physically divided into arbitrary units according to various additions or functional loads. It can be configured in a distributed/integrated manner. That is, the embodiments described above may be implemented in any combination, or the embodiments may be implemented selectively.

The present invention is particularly useful for companies whose customers are companies in the construction industry.

100 Business support device 102 Control unit
102a Billing Processing Department
102b Change section
102c Creation unit 104 Communication interface unit 106 Storage unit
106a Billing data storage unit
106b Collection schedule data storage unit
106c Bill data storage unit 108 Input/output interface unit 112 Input device 114 Output device 200 Server device 300 Network

Claims (3)

A business support device comprising a control unit,
The control section,
From the billing data storage unit and the collection schedule data storage unit, extract the billing data associated with the specified billing party for whom permission to issue an invoice was not obtained and the collection schedule data associated with the billing data, and extract the extracted billing data. The billing deadline included in the extracted billing data and the scheduled collection date included in the extracted scheduled collection data are output to the screen displayed on the display section, and when the billing deadline is changed on the screen, the billing deadline included in the extracted billing data is displayed. Change the billing deadline date to the changed billing deadline date, and change the scheduled collection date of the extracted collection schedule data to the billing deadline date after the change, and the scheduled collection date derived according to the predetermined rules regarding the billing deadline date and the timing of billing and collection. A business support device equipped with a change means for changing the scheduled collection date. An information processing device including a control unit,
From the billing data storage unit and the collection schedule data storage unit, extract the billing data associated with the specified billing party for whom permission to issue an invoice was not obtained and the collection schedule data associated with the billing data, and extract the extracted billing data. The billing deadline included in the extracted billing data and the scheduled collection date included in the extracted scheduled collection data are output to the screen displayed on the display section, and when the billing deadline is changed on the screen, the billing deadline included in the extracted billing data is displayed. Change the billing deadline date to the changed billing deadline date, and change the scheduled collection date of the extracted collection schedule data to the billing deadline date after the change, and the scheduled collection date derived according to the predetermined rules regarding the billing deadline date and the timing of billing and collection. A business support program that functions as a means of changing the scheduled collection date. Executed by the control unit of an information processing device including a control unit,
From the billing data storage unit and the collection schedule data storage unit, extract the billing data associated with the specified billing party for whom permission to issue an invoice was not obtained and the collection schedule data associated with the billing data, and extract the extracted billing data. The billing deadline included in the extracted billing data and the scheduled collection date included in the extracted scheduled collection data are output to the screen displayed on the display section, and when the billing deadline is changed on the screen, the billing deadline included in the extracted billing data is displayed. Change the billing deadline date to the changed billing deadline date, and change the scheduled collection date of the extracted collection schedule data to the billing deadline date after the change, and the scheduled collection date derived according to the predetermined rules regarding the billing deadline date and the timing of billing and collection. A business support method that includes a change step to change the scheduled collection date.

Images