JP7401868B1 - Collection systems, programs and methods - Google Patents

Abstract

An object of the present invention is to provide a bill collection system that allows a corporation that operates multiple offices to smoothly manage collection operations at each office. [Means for solving the problem] A program that is executed by a collection system that is equipped with a processor and is used by a corporation that manages multiple business establishments to collect money from customers at the business establishment, the processor being used by a person in charge of the corporation. a step of receiving from a terminal device an aggregation instruction for at least one of information regarding billing to customers at each of the plurality of business establishments and information regarding the collection status of the bill; and in response to the acceptance of the aggregation instruction; A program that executes the steps of totalizing at least one of information regarding billing for each office and information regarding collection status, and outputting the totalized information to a terminal device. [Selection diagram] Figure 16

Description

The present disclosure relates to a collection system, program, and method.

2. Description of the Related Art Conventionally, systems have been known in which various expense claims are issued from a billing source to a payer using electronic data.

For example, Patent Document 1 discloses a system that aggregates billing information issued from each of a plurality of billing sources and bills the payer all at once.

JP2001-250069

However, with conventional systems, payment information is managed for each billing source, so for example, in a corporation that operates multiple business offices, it is necessary to check the collection status of each billing business, There was room for improvement in the integrated management of collection operations.

The present disclosure aims to provide a bill collection system that allows a corporation that operates multiple offices to smoothly manage the collection operations of each office.

A program according to an aspect of the present disclosure is a program that includes a processor and is executed by a collection system used for collecting money from customers at a business office of a corporation that manages a plurality of business establishments, the program having the processor run by a person in charge of the corporation. a step of accepting, from a terminal device to be used, an aggregation instruction for at least one of information regarding customer billing at each of a plurality of business establishments and information regarding the collection status of the bill; and responding to the acceptance of the aggregation instruction. A program that causes the computer to perform the steps of totalizing at least one of information regarding billing and information regarding collection status for each business establishment, and outputting the totalized information to a terminal device.

With the bill collection system of the present disclosure, in a corporation that operates multiple offices, it is possible to smoothly manage bill collection operations at each office.

FIG. 1 is a block diagram of a bill collection system of the present invention. FIG. 2 is a block diagram showing the configuration of the terminal device shown in FIG. 1. FIG. FIG. 2 is a block diagram showing the functional configuration of the server shown in FIG. 1. FIG. FIG. 4 is a diagram illustrating a configuration example of a database that stores information regarding corporations stored in a storage unit of the server illustrated in FIG. 3; FIG. 4 is a diagram illustrating a configuration example of a database that stores information regarding a person in charge stored in a storage unit of the server illustrated in FIG. 3; 4 is a diagram illustrating a configuration example of a database that stores information regarding members and payers stored in a storage unit of the server illustrated in FIG. 3. FIG. FIG. 4 is a diagram illustrating a configuration example of a database that stores information regarding billing that is stored in a storage unit of the server illustrated in FIG. 3; FIG. 4 is a diagram illustrating a configuration example of a database that stores information regarding operation history stored in a storage unit of the server illustrated in FIG. 3; FIG. 2 is a flowchart showing a management screen display process when a person in charge logs in, among the processes of the money collection system according to the present invention. FIG. 2 is a flowchart showing the processing from the billing of expenses by the business establishment to the payment by the payer, among the processing of the bill collection system according to the present invention. FIG. 2 is a flowchart showing billing closing processing from a person in charge of a corporation, among the processing of the bill collection system according to the present invention. FIG. 2 is a flowchart showing billing and collection status aggregation processing among the processing of the collection system according to the present invention. It is a flowchart which shows the designation process of the deposit account among the processes of a money collection system. It is a figure showing the example of the 1st screen in the money collection system concerning the present invention. It is a figure which shows the example of the 2nd screen in the collection system based on this invention. It is a figure which shows the example of the 3rd screen in the collection system based on this invention. It is a figure which shows the example of the 4th screen in the collection system based on this invention.

Hereinafter, one embodiment of the present invention will be described in detail based on the drawings. In addition, in the drawings for explaining the embodiments, the same components are generally designated by the same reference numerals, and repeated explanations thereof will be omitted.

(1) Overview of System 1 FIG. 1 is a diagram illustrating an overview of a bill collection system 1 (hereinafter simply referred to as system 1) of the present invention.
As shown in FIG. 1, a system 1 is a system used for collection work related to payments from customers. Further, the system 1 is particularly used for bill collection operations at offices by a corporation that manages a plurality of offices.
In the following description, the configuration of the system 1 will be described first, and then various processes using the system 1 will be described in detail.

(1-1) Overall Configuration The overall configuration of the system 1 according to this embodiment will be explained.
As shown in FIG. 1, the system 1 includes a plurality of terminal devices 10 and a server 20.
The plurality of terminal devices 10 and the server 20 are connected to each other via a network 80 so as to be able to communicate with each other. The network 80 is configured by a wired or wireless network.

In the following description, the terminal devices 10 are classified into the following three types depending on the type of user.
・Corporate terminal 10A used by corporate personnel
- Office terminal 10B used by the person in charge at each office
・Payer terminal 10C used by the payer

Here, a corporation is an organization (business operator) that operates any business, and refers to a group that is combined for a certain purpose. Businesses operated by corporations include various businesses that provide prescribed services to members, and examples include the following.
・Educational business: Nursery schools, kindergartens, after-school child care, elementary schools, cram schools, various lessons, etc. ・Life-related services: Schools for working adults, training gyms, etc.

In addition, as a business within the scope of System 1, a business that continuously provides services to members and in which the establishment receives regular membership fee payments is preferable.
In addition, the corporation in this explanation may include an organization that operates a prescribed business that does not have legal corporate status.
Furthermore, the system 1 may be used by an individual who operates multiple offices. In this case, the individual will be considered a legal entity for the purposes of this description.

The system 1 is used by a corporation that operates various businesses at multiple offices. In other words, a corporation is an organization that centrally manages the operations of multiple business establishments. For example, the relationship between a corporation and a business office is as follows.
・Corporate: School corporation that operates multiple kindergartens ・Business office: Each kindergarten operated by the school corporation

Here, the types of users of the system 1 will be defined.
・Corporate person in charge: A person who belongs to a corporation and performs overall management of the operations of multiple offices operated by the corporation (e.g. corporate employee, corporate representative, etc.)
・Business office personnel: Persons who belong to a business office, provide services to members, and manage the operation of the business office (e.g., business office employees, business office representatives, etc.)
・Members: Those who receive services from each business establishment (or children if the business establishment is a kindergarten)
・Payer: A member who receives services from each business establishment, or a member's guardian, etc., who pays the consideration for the services the member receives to the business establishment (or a parent if the business establishment is a kindergarten). )
Note that members and payers may be referred to as customers.

(1-2) Hardware Configuration of Terminal Device 10 As shown in FIG. 1, the terminal device 10 is an information processing device operated by each user. The terminal device 10 is realized by a stationary PC (Personal Computer), a laptop PC, or the like. In addition, the terminal device 10 may be, for example, a tablet compatible with a mobile communication system or a mobile terminal such as a smartphone.

The terminal device 10 is communicably connected to the server 20 via the network 80. The terminal device 10 has a wireless base station 81 that is compatible with communication standards such as 5G and LTE (Long Term Evolution), and a wireless LAN (Local Area Network) that is compatible with wireless LAN (Local Area Network) standards such as IEEE (Institute of Electrical and Electronics Engineers) 802.11. It is connected to the network 80 by communicating with a communication device such as a wireless LAN router 82 .

As shown in FIG. 1, the terminal device 10 includes a communication IF (Interface) 12, an input device 13, an output device 14, a memory 15, a storage section 16, and a processor 19.

The communication IF 12 is an interface for inputting and outputting signals so that the terminal device 10 communicates with an external device.
The input device 13 is an input device (for example, a keyboard, a touch panel, a touch pad, a pointing device such as a mouse, etc.) for receiving input operations from a user.

The output device 14 is an output device (display, speaker, etc.) for presenting information to the user.
The memory 15 is for temporarily storing programs and data processed by the programs, and is a volatile memory such as DRAM (Dynamic Random Access Memory).

The storage unit 16 is a storage device for storing data, and is, for example, a flash memory or an HDD (Hard Disc Drive).
The processor 19 is hardware for executing a set of instructions written in a program, and is composed of an arithmetic unit, registers, peripheral circuits, and the like.

(1-3) Hardware Configuration of Server 20 As shown in FIG. 1, the server 20 is an information processing device that supports collection of membership fees from members at a business office.
Server 20 is a computer connected to network 80. The server 20 includes a communication IF 22 , an input/output IF 23 , a memory 25 , a storage 26 , and a processor 29 .

The communication IF 22 is an interface for inputting and outputting signals so that the server 20 communicates with external devices.
The input/output IF 23 functions as an interface with an input device for accepting input operations from a user and an output device for presenting information to the user.

The memory 25 is for temporarily storing programs and data processed by the programs, and is a volatile memory such as DRAM (Dynamic Random Access Memory).
The storage 26 is a storage device for storing data, and is, for example, a flash memory or an HDD (Hard Disc Drive).
The processor 29 is hardware for executing a set of instructions written in a program, and is composed of an arithmetic unit, registers, peripheral circuits, and the like.

(2) Functional Configuration of Terminal Device 10 FIG. 2 is a block diagram showing the functional configuration of the terminal device 10 that constitutes the system 1. As shown in FIG. 2, the terminal device 10 includes a plurality of antennas (an antenna 111, an antenna 112), a wireless communication section (a first wireless communication section 121, a second wireless communication section 122) corresponding to each antenna, and an input terminal. It includes a reception section 130 (including a keyboard 131 and a display 132), an audio processing section 140, a microphone 141, a speaker 142, a camera 150, a storage section 160, and a control section 170.

The terminal device 10 also has functions and configurations that are not particularly illustrated in FIG. 2 (for example, a battery for holding power, a power supply circuit that controls the supply of power from the battery to each circuit, etc.). As shown in FIG. 2, each block included in the terminal device 10 is electrically connected by a bus or the like.

The antenna 111 radiates a signal emitted by the terminal device 10 as a radio wave. Further, the antenna 111 receives radio waves from space and provides a received signal to the first wireless communication unit 121.

The antenna 112 radiates a signal emitted by the terminal device 10 as a radio wave. Further, the antenna 112 receives radio waves from space and provides a received signal to the second wireless communication unit 122.

The first wireless communication unit 121 performs modulation and demodulation processing for transmitting and receiving signals via the antenna 111 so that the terminal device 10 communicates with other wireless devices. The second wireless communication unit 122 performs modulation and demodulation processing for transmitting and receiving signals via the antenna 112 so that the terminal device 10 communicates with other wireless devices.

The first wireless communication unit 121 and the second wireless communication unit 122 are communication modules including a tuner, an RSSI (Received Signal Strength Indicator) calculation circuit, a CRC (Cyclic Redundancy Check) calculation circuit, a high frequency circuit, and the like. The first wireless communication unit 121 and the second wireless communication unit 122 perform modulation/demodulation and frequency conversion of wireless signals transmitted and received by the terminal device 10 and provide received signals to the control unit 170.

The input receiving unit 130 has a mechanism for receiving input operations from the user. Specifically, input reception unit 130 includes a keyboard 131 and a display 132. Note that the input receiving unit 130 may be configured as a touch screen that detects the position of the user's touch on the touch panel by using, for example, a capacitive touch panel.

The keyboard 131 receives input operations from the user of the terminal device 10 . The keyboard 131 is a device for inputting characters, and outputs input character information to the control unit 170 as an input signal.

The display 132 displays data such as images, videos, and text under the control of the control unit 170. That is, the display 132 also functions as an output unit that outputs information to the user. The display 132 is realized by, for example, an LCD (Liquid Crystal Display) or an organic EL (Electro-Luminescence) display.

The storage unit 160 is configured with, for example, a flash memory, and stores data and programs used by the terminal device 10. In one aspect, storage unit 160 stores user information 161.

The user information 161 is information about a user who uses the system 1 using the terminal device 10. The user information 161 includes information for identifying the user, the user's name, account information for a message application used by the user, information regarding contact information such as the user's e-mail address, and the like.

The control unit 170 controls the operation of the terminal device 10 by reading a program stored in the storage unit 160 and executing instructions included in the program. The control unit 170 is, for example, an application program installed in the terminal device 10 in advance. The control unit 170 functions as an operation reception unit 171, a transmission/reception unit 172, a data processing unit 173, and a display processing unit 174 by operating according to a program.

The operation reception unit 171 performs a process of accepting a user's input operation on an input device such as the keyboard 131.

The transmitting/receiving unit 172 performs processing for the terminal device 10 to transmit and receive data with an external device such as the server 20 according to a communication protocol.

The data processing unit 173 performs calculations on the data input by the terminal device 10 according to a program, and outputs the calculation results to a memory or the like.

The display processing unit 174 performs a process of presenting information to the user. The display processing unit 174 performs processing such as displaying a display image on the display 132.

(3) Functional configuration of server 20 FIG. 3 is a diagram showing the functional configuration of server 20 that constitutes system 1. As shown in FIG. 3, the server 20 functions as a communication section 201, a storage section 202, and a control section 203.

The communication unit 201 performs processing for the server 20 to communicate with external devices.

(3-1) Configuration of Storage Unit 202 The storage unit 202 stores data and programs used by the server 20. The storage unit 202 stores the following database.
1) Database that stores information about corporations/corporate database (corporate DB) 2021
・Establishment information database (establishment DB) 2022
・Deposit account database (deposit account DB) 2023
2) Database that stores information about the person in charge/person in charge database (person in charge DB) 2024
・Role database (role DB) 2025
3) Database/member database (member DB) 2026 that stores information about members and payers
・Payer database (payer DB) 2027
4) Database that stores billing information/billing database (billing DB) 2028
5) Database that stores information regarding operation history by corporate personnel: Billing closing history database (billing closing history DB) 2029
・Designated account master database (designated account master DB) 2030
Details of each of these databases will be described later.

(3-2) Configuration of control unit 203 The control unit 203 shown in FIG. 3 includes various modules such as a transmission/reception control module 2031, an acquisition module 2032, and an account authentication module 2033, by the processor 29 of the server 20 performing processing according to a program. , a billing module 2034, a deposit module 2035, a totaling module 2036, and an output module 2037.

The transmission/reception control module 2031 controls processing in which the server 20 transmits and receives signals from an external device according to a communication protocol.

The acquisition module 2032 acquires various types of information received by the transmission/reception control module 2031, and controls recording processing in the corresponding database.

The account authentication module 2033 performs login authentication when logging into the system 1 using account information input by a person in charge. The account authentication module 2033 switches the management screen, which will be described later, by determining the authority of the person in charge of logging in. That is, the account authentication module 2033 outputs an operation screen for a corporate person to the corporate terminal 10A on the condition that the person in charge has been granted a predetermined authority (corporate authority).

Billing module 2034 generates billing information. The billing module 2034 creates billing information for members of each business establishment according to the bill issuance time registered in the business establishment DB 2022.

The deposit module 2035 accepts payment information from external electronic payment means and updates the billing database. The deposit module 2035 receives payment information for each payment ID issued by an external electronic payment means, and updates the column related to deposits in the billing DB 2028.
At this time, the payment module 2035 clears the billing information. That is, the deposit module 2035 refers to the billing DB 2028 to check whether the cost of the corresponding bill has already been deposited. The deposit module 2035 records the confirmation result as a new record in the item "Deposit or not" in the billing DB 2028.
The deposit module 2035 refers to the designated account master DB 2030 for the expenses deposited from the payer, and transmits instructions to the financial institution to deposit the expenses into the corresponding deposit account.

The tally module 2036 tallies unpaid bills. Specifically, the aggregation module 2036 refers to the billing information and identifies unpaid bill numbers for which payment has not been made beyond the due date. The aggregation module 2036 identifies the member ID corresponding to the unpaid bill number, and references the member DB 2026 to identify the payer ID. The aggregation module 2036 refers to the payer DB 2027 and specifies billing information corresponding to the specified payer ID. The aggregation module 2036 transmits unpaid billing information and billing destination information to the output module 2037.

The aggregation module 2036 aggregates the payment statuses of a plurality of members as aggregation of payment statuses for each establishment. Specifically, the aggregation module 2036 displays the rate of payment completion among multiple payers as the collection status. Furthermore, the aggregation module 2036 displays the payment status for each group divided based on the attributes of the payer. Furthermore, the aggregation module 2036 displays the collection status for each common expense item.

In addition, the aggregation module 2036 aggregates at least one of information regarding billing for each office and information regarding the collection status in response to receiving an aggregation instruction from a person in charge of the corporation. At this time, the aggregation module 2036 aggregates billing information and collection status of all offices managed by the corporation.

The output module 2037 notifies the payer terminal 10C of the billing information as a bill. At this time, the output module 2037 notifies the billing information as well as the URL regarding the external electronic payment means.
The output module 2037 notifies the office terminal 10B of the payment from the payer. The output module 2037 issues a receipt to the payer terminal 10C.
In addition, the output module 2037 outputs information regarding the totaled billing and collection status for each office to the corporate terminal 10A.

(4) Data structure of database Next, the structure of each database mentioned above will be explained in order. Note that these explanations are just examples, and the structure of the database can be changed arbitrarily.

(4-1) Database that stores information regarding corporations First, a database that stores information regarding corporations will be explained.
FIG. 4 is a diagram showing a database that stores information regarding corporations. Among these, FIG. 4A is a diagram showing the corporation DB 2021, FIG. 4B is a diagram showing the business office DB 2022, and FIG. 4C is a diagram showing the deposit account DB 2023.

(4-1-1) Corporate DB2021
The corporation DB 2021 shown in FIG. 4A is a database that records information regarding corporations that use the system 1 (corporate information). In the corporate DB 2021, new records are recorded by user registration when a corporation uses the service for the first time. The corporate DB 2021 can be viewed and edited by the administrator of the system 1.

As shown in FIG. 4A, each record in the corporation DB 2021 includes an item "Corporate ID", an item "Corporate name", an item "Head office location address", and an item "Representative name".

The item "Corporate ID" is identification information of a corporation that can identify the corporation. The corporate ID is assigned a unique value to each corporation.

The item "Corporate Name" is information indicating the name of the corporation corresponding to the corporation ID.

The item "head office location" is information indicating the location of the corporate headquarters corresponding to the corporate ID.

The item "Representative Name" is information indicating the name of the representative of the corporation corresponding to the member ID.
Note that other data items may be managed in the corporate DB 2021.

(4-1-2) Business establishment DB2022
The office DB 2022 shown in FIG. 4B is a database for holding information regarding offices that use the system 1 (office information). A new record is recorded in each record of the business office DB 2022 when a business office that newly uses the system 1 is registered. The business office DB 2022 can be viewed and edited by the administrator of the server 20 and the person in charge of the corporation.

As shown in FIG. 4B, each record in the business office DB 2022 includes the item "business ID", the item "corporate ID", the item "business name", the item "location", and the item "representative name". , the item ``Contact information'', and the item ``Billing period''.

The item “business ID” is identification information of a business establishment that can identify the business establishment. The office ID is assigned to each office so that it becomes a unique value.

The item "Corporate ID" is identification information of the corporation to which the business office corresponding to the business office ID belongs.

The item "business name" is information indicating the name of the business office corresponding to the business office ID.

The item "location" is information indicating the location of the business office corresponding to the business office ID.

The item "representative name" is information indicating the name of the representative of the business establishment corresponding to the business establishment ID.

The item "contact information" is information related to contact information such as a telephone number or email address of the business office corresponding to the business office ID.

The item "bill issuance time" is information registered as the time when a bill is issued in the business office corresponding to the business office ID. The item "Bill Issue Timing" is applied to regularly issued invoices. In addition, an invoice can be issued each time a request for expenses occurs.
Note that other data items may be managed in the business office DB 2022.

(4-1-3) Deposit account DB2023
The deposit account DB 2023 shown in FIG. 4C is a database for holding information regarding deposit accounts that use the system 1 (deposit account information). A new record is recorded in each record of the deposit account DB 2023 when a new deposit account to be used in the system 1 is registered. The process of registering a deposit account will be described later. The deposit account DB 2023 can be viewed and edited by the administrator of the server 20 and the person in charge of the corporation.

As shown in FIG. 4C, each record in the deposit account DB 2023 includes an item "account ID", an item "account number", and an item "corporate ID".

The item "account ID" is the identification information of the deposit account that can identify the deposit account. The deposit account ID is assigned a unique value for each deposit account.

The item "account number" is information regarding the account number managed by the financial institution for the deposit account corresponding to the deposit account ID.

The item "Corporate ID" is identification information of the corporation that uses the deposit account corresponding to the deposit account ID.
Note that other data items may be managed in the deposit account DB 2023.

(4-2) Database that stores information regarding persons in charge Next, a database that stores information regarding persons in charge will be explained.
FIG. 5 is a diagram showing the person in charge DB 2024, which is a database that stores information regarding persons in charge. Among these, FIG. 5A is a diagram showing the person in charge DB 2024, and FIG. 5B is a diagram showing the role DB 2025.

(4-2-1) Person in charge DB2024
The person in charge DB 2024 shown in FIG. 5A is a database for holding information (person in charge information) regarding the person in charge of the corporation and the person in charge of the office that uses the system 1. A new record is recorded in each record of the person in charge DB 2024 when a new person in charge to be used in the system 1 is registered. The person in charge DB 2024 can be viewed and edited by the administrator of the server 20 and the person in charge at the corporation.

As shown in FIG. 5A, each record in the person in charge DB 2024 has an item "person in charge ID", an item "name", an item "login pass", an item "corporate affiliation", and an item "office affiliation". , includes the item "authority type".

The item "person in charge ID" is identification information of a person in charge that can identify the person in charge. The person in charge ID is assigned a unique value for each person in charge.

The item "name" is information regarding the name of the person in charge corresponding to the person in charge ID.

The item “Login Pass” is a password that the person in charge corresponding to the person in charge ID is required to input when logging into the system 1.

The item "corporate affiliation" is identification information of the corporation to which the person in charge corresponding to the person in charge ID belongs.

The item "affiliated office" is identification information of the office to which the person in charge corresponding to the person in charge ID belongs. Note that if the person in charge is a person in charge of a corporation, this item may be Null.

The item "role" is information indicating the role set for the person in charge corresponding to the person in charge ID. There are two roles for the person in charge:
- Person in charge of corporation/person in charge of business office Other data items may be managed in the person in charge DB 2024.

(4-2-2) Role DB2025
The role DB 2025 shown in FIG. 5B is a database for holding information (role authority information) regarding the role authority of a person in charge of using the system 1. Each record of the role DB 2025 is set in advance when the system 1 is constructed. The role DB 2025 can be viewed and edited by the administrator of the server 20.

As shown in FIG. 5B, each record in the role DB 2025 includes an item "role name" and an item "authority".

The item "role name" defines the name of the role set for the person in charge.

The item "authority type" is information indicating the authority granted to the role corresponding to the role name. The authority of the person in charge includes corporate authority set for a person in charge of a corporation, and office authority set for a person in charge of a business office. The differences between these authorities will be described later.
Note that other data items may be managed in the role DB 2025.

(4-3) Database that stores information regarding members and payers Next, a database that stores information regarding members and payers will be explained.
FIG. 6 is a diagram illustrating a database that stores information regarding members and payers. Among these, FIG. 6A is a diagram showing the member DB 2026, and FIG. 6B is a diagram showing the payer DB 2027.

(4-3-1) Member DB2026

The member DB 2026 shown in FIG. 6A is a database for holding information (member information) regarding members to whom services are applied from each office. Each record in the member DB 2026 is recorded based on information input from the business establishment when registering a new member of the business establishment.
In the member DB 2026, each office can view information regarding its own members.

As shown in FIG. 6A, each record in the member DB 2026 includes an item "member ID", an item "office ID", an item "member name", an item "attribute", an item "payer name", Includes items such as "Payer ID".

The item "member ID" is information for identifying the member who receives services from the business establishment. The office ID is assigned to each member so that it becomes a unique value.

The item "business office ID" is information indicating the ID of the business office to which the member corresponding to the member ID belongs.

The item "member name" is information indicating the name of the member corresponding to the member ID. For example, if the business establishment is a nursery school, the members correspond to students (children) attending the nursery school.

The item "attribute" is information indicating the attribute set by the business office for the member corresponding to the member ID. For example, if the business office is a nursery school, the attributes correspond to class names such as "Elderly Rose Group" or "Younger Sakura Group." For example, if the office is a music school, the attribute may be a course to be taken, such as an "advanced class" or a "beginner class." Furthermore, if the business office is a fitness gym, the information may be information related to contract details such as "full-time membership" or "weekday membership." The item "attribute" is automatically changed as the member (kindergarten child) progresses or changes in the member's contract details.

The item "payer name" is information indicating the name of the member corresponding to the member ID who pays for the services provided by the office. The "payer's name" may be the name of the member, or, for example, if the business is a nursery school, it may be the name of the member's (student) guardian. Furthermore, in the case of a corporate contract, the "payer name" may be the corporate name.

The item "payer ID" is information for identifying the payer. The payer ID is set along with the registration of the payer's name. The payer ID may be a string of random numbers or characters.
Note that other data items may be managed in the member DB 2026.

(4-3-2) Payer DB2027

The payer DB 2027 shown in FIG. 6B is a database for holding information regarding payers who use the system 1 (payer account information). Each record in the payer DB 2027 is recorded in response to registration of billing information from a new payer. Note that each record in the payer DB 2027 can be changed according to the needs of the payer. In the payer DB 2027, each office can view information regarding payers for its own members.

As shown in FIG. 6B, each record in the payer DB 2027 includes an item "Payer ID", an item "Payer Name", an item "Registered Password", an item "Billing Party Information", and the like.

The item “payer ID” is information that refers to the payer ID set in the member DB 2026.

The item "payer name" is information indicating the name of the payer corresponding to the payer ID.

The item "registration password" is information regarding the password used when the payer corresponding to the payer ID registers account information. The billing information registration process using the registration password will be described later.

The item "billing destination information" is information regarding the billing destination registered by the payer corresponding to the payer ID. In this embodiment, an example will be described in which the account information of a message application that the payer usually uses is registered as billing information. The billing information may be information regarding an email address or other contact information that can receive billing information by electronic means.
The billing information may be a token for identifying the payer's account information in the message application.
Note that other data items may be managed in the payer DB 2027.

(4-4) Database that stores information related to billing Next, the billing DB 2028 that stores information related to billing will be explained. FIG. 7 is a diagram showing the billing database.

(4-4-1) Billing DB2028
The billing DB 2028 shown in FIG. 7 is a database for holding bill information (billing information) regarding expenses billed from the business office to the payer by the system 1. Each record in the billing DB 2028 is recorded based on payment information notified from an external electronic payment means when a bill is issued and payment is made by the external electronic payment means described below. The bill issuance process will be described later. Note that each record in the billing DB 2028 can be changed according to the needs of the business office. Payment processing using an external electronic payment method will be described later.
In the billing DB 2028, each office can view information regarding its own bill.

As shown in FIG. 7, each record in the billing DB 2028 includes an item "Invoice number", an item "Business office ID", an item "Billing date", an item "Payment date", an item "Expense item", The item ``Billed Amount'', the item ``Member ID'', the item ``Payment ID'', the item ``Deposit Date'', the item ``Deposit Method'', the item ``Deposit Amount'', and the item ``Deposit Deposit'', including.

The item "bill number" is information for identifying a bill.

The item "business office ID" is information for specifying the business office where the bill corresponding to the bill number was issued.

The item "billing date" is information indicating the date on which the billed expense was incurred in the bill corresponding to the bill number. The billing date may be information indicating a period such as a month or a week.

The item "payment date" is information indicating the payment date set for the bill corresponding to the bill number.

The item "Expense Item" is information indicating the details of the expenses charged on the bill corresponding to the bill number. If the business is a nursery school, the corresponding expenses include "childcare fees" and "teaching materials costs."

The item "Billed Amount" is information indicating the amount of expenses charged by the bill corresponding to the bill number.

The item "member ID" is information that identifies the member who has received services from the establishment in exchange for the expense charged on the invoice corresponding to the invoice number.

The item "payment ID" is information for identifying a payment process. The payment ID is assigned in correspondence with the bill number.

The item "bill number" is information that specifies the bill number for the payment ID.

The item "payment date" is information indicating the date on which payment was made regarding the bill number corresponding to the payment ID. The item "deposit date" may include information regarding time.

The item "deposit method" is information indicating the means by which payment was made regarding the bill number corresponding to the payment ID. The item "deposit method" corresponds to "credit card", "convenience store payment", etc.

The item "deposit amount" is information indicating the amount actually deposited in the payment regarding the bill number corresponding to the payment ID.

The item "Presence or absence of payment" is information indicating the payment status of expenses charged by the bill corresponding to the bill number.
Note that other data items may be managed in the billing DB 2028.

(4-5) Database that stores information regarding operation history by corporate personnel Next, a database that stores information regarding operational history by corporate personnel will be described.
FIG. 8 is a database that stores information regarding the operation history by a person in charge of a corporation. Of these, FIG. 8A is a diagram showing the billing closing process history DB, and FIG. 8B is a diagram showing the designated account master database.

(4-5-1) Billing closing history DB2029
The bill closing history DB 2029 shown in FIG. 8A is a database that records the history of bill closing processing performed by a person in charge of a corporation using the system 1. A new record is recorded in each record of the bill closing history DB 2029 when a bill closing process is performed by a person in charge of the corporation. The bill closing history DB 2029 can be viewed and edited by the administrator of the server 20 and the person in charge of the corporation.

As shown in FIG. 8A, each record in the billing closing history DB 2029 includes the item "billing closing history ID", the item "corporate ID", the item "business office ID", the item "target aggregation month", and the item " ``Person in charge ID'' and the item ``Closing date and time''.

The item "bill closing history ID" is identification information of the bill closing process that can specify the bill closing process. The bill closing history ID is assigned to be a unique value for each bill closing process.

The item "Corporation ID" is identification information of the corporation that performed the billing closing process corresponding to the billing closing history ID.

The item "business office ID" is identification information of the business office that is the target of the bill closing process corresponding to the bill closing history ID.

The item "Target aggregation month" is information regarding the aggregation month in which the bill was closed by the bill closing process corresponding to the bill closing history ID.

The item "person in charge ID" is identification information of the corporate person in charge who inputs the instruction operation regarding the bill closing process corresponding to the bill closing history ID.

The item “closing date and time” is information regarding the date and time when the billing closing process corresponding to the billing closing history ID was instructed.
Note that other data items may be managed in the bill closing history DB 2029.

(4-5-2) Designated account master DB2030
The designated account master DB 2030 shown in FIG. 8B is a database that records the master of the account (designated account) designated by the person in charge of the corporation using the system 1 and to which the collected expenses will be deposited. A new record is recorded in each record of the designated account master DB 2030 when a person in charge of the corporation designates an account to which money will be deposited. The designated account master DB 2030 can be viewed and edited by the administrator of the server 20 and the person in charge of the corporation.

As shown in FIG. 8B, each record in the designated account master DB 2030 includes the item “designated account master ID”, the item “corporate ID”, the item “business office ID”, the item “designated expense item”, and the item “account ID,” the item “person in charge ID,” and the item “designated date and time.”

The item "designated account master ID" is identification information of the designated account master that can identify the designated account master. The designated account master ID is assigned a unique value for each designated account master.

The item "Corporate ID" is identification information of a corporation to which the designated account master corresponding to the designated account ID is applied.

The item "Business establishment ID" is identification information of the business establishment to which the designated account master corresponding to the designated account ID is applied.

The item "designated expense item" is information regarding the billing expense item of the bill to which the designated account master corresponding to the designated account master ID is applied.

The item "account ID" is identification information of a deposit account to which money is to be deposited in the designated account master corresponding to the designated account master ID.

The item "person in charge ID" is identification information of the person in charge of the corporation who registered the designated account master (designated the deposit account) corresponding to the designated account master ID.

The item "designated date and time" is information regarding the date and time when the designated account master registration (designation of deposit account) corresponding to the designated account master ID was performed.
Note that other data items may be managed in the designated account master DB 2030.

(5) Processing of System 1 Next, the control processing of System 1 will be explained.

(5-1) Display processing of management screen when person in charge logs in First, account authentication processing when logging into system 1 will be explained.
FIG. 9 is a flowchart showing the management screen display process when a person in charge logs in.

As shown in FIG. 9, in the management screen display process, first, the corporate terminal 10A or the office terminal 10B receives a login operation input from a person in charge (step S101).
Specifically, the terminal device 10 acquires the account information including the person-in-charge ID and login password received by the operation reception unit 171, and transmits it to the server 20 via the transmission/reception unit 172.

After step S101, the server 20 accepts a login operation (step S221).
Specifically, the transmission/reception control module 2031 of the server 20 receives information regarding the account operation included in the login operation transmitted from the terminal device 10 in step S101. The data acquisition unit acquires the account information of the person in charge included in the information regarding the account operation, and inputs it to the account authentication module 2033.

After step S201, the server 20 performs account authentication (step S202).
Specifically, the account authentication module 2033 of the server 20 refers to the person in charge DB 2024 regarding the account information of the person in charge input from the data acquisition unit in step S201, and identifies the person in charge including the corresponding person ID and login password. Determine whether the account exists. At this time, the account authentication module 2033 determines user authority. That is, the role of the person in charge associated with the person in charge ID in the person in charge DB 2024 is specified, and the authority granted to the person in charge is specified by referring to the role DB 2025.

After step S202, the server 20 outputs a management screen (step S203).
Specifically, the output module 2037 of the server 20 outputs a management screen to the terminal device 10 in accordance with the authority of the person in charge who has logged in. That is, the output module 2037 outputs a corporate management screen to the corporate terminal 10A when corporate authority (predetermined authority) is granted to the person in charge.
On the other hand, if the person in charge is not granted corporate authority but is granted office authority, the output module 2037 outputs a business office management screen to the office terminal 10B.

That is, in the system 1, the following two management screens are set, and the display can be switched depending on the user's authority.
・Corporate management screen: This is the screen where you can check the billing information of all business offices managed by the corporation, and the screen where you can enter instructions for billing closing processing and aggregation of billing information for each business office, which will be described later.・Business office management screen: Business This is a screen where you can check billing information within the office, and a screen where you can edit individual billing information within the office.The corporate management screen can only be viewed and edited by the person in charge of the corporation. It can be viewed and edited by both corporate and office personnel.

After step S203, the terminal device 10 displays a management screen (step S102).
Specifically, the display processing unit 174 of the terminal device 10 displays the management screen output in step S203 on the display 132 of the terminal device 10.
That is, in step S102, a corporate management screen is displayed on the corporate terminal 10A. A specific display mode of the corporate management screen will be described later as a first screen example D1. Further, in step S102, a business office management screen is displayed on the business terminal 10B. A specific display mode of the office management screen will be described later as a second screen example D2.
With the above steps, the management screen display process ends.

(5-2) Issuance of invoices from businesses and payment processing by payers Next, the process of issuing invoices from businesses will be explained.
FIG. 10 is a flowchart showing the process from the request for expenses from the business establishment to the payment by the payer. This process can be performed from the office management screen displayed on the office terminal 10B.

As shown in FIG. 10, in the bill issuance process, first, billing information is input at the office terminal 10B (step S111).
Specifically, while logged in, a person in charge of the business will send a request to the office terminal for expenses that are not scheduled to be billed regularly (for example, overtime fees at a nursery school, etc.). An input operation to 10B is performed.

After step S111, the server 20 accepts billing information (S211).
Specifically, the transmission/reception control module 2031 of the server 20 receives information regarding each item of billing information transmitted from the office terminal 10B in step S111.

After step S211, the server 20 creates billing information (step S212).
Specifically, the acquisition module 2032 of the server 20 acquires the billing information received by the transmission/reception control module 2031 in step S211, and records it as a new record in the billing DB 2028.
The billing module 2034 creates billing information based on the billing information newly recorded in the billing DB 2028. In addition, the billing module 2034 automatically creates billing information for each member according to the bill issuance timing conditions set in the business office DB 2022 for expenses that are set to be billed periodically. .

After step S212, the server 20 issues a bill (step S213).
Specifically, the output module 2037 of the server 20 transmits a bill based on the created billing information to the payer terminal 10C. At this time, the output module 2037 refers to the payer ID stored in the billing information and the billing information stored in the payer DB 2027, and sends the bill to the payer's message app account. Send. Furthermore, the output module 2037 notifies the bill as well as the URL regarding the external electronic payment means.

After step S213, the payer terminal 10C receives the bill (step S311). Specifically, the message application receives the bill at the payer terminal 10C. The payer checks the bill received by the messaging app and understands the details of the bill.

After step S311, the payer executes payment (step S312). Specifically, the payer makes a payment using an external electronic payment means that is transferred from the notified URL.
The external electronic payment means is an online payment system that cooperates with a payment agency system, such as a credit card payment or a payment at a convenience store, as a payment method.
The external electronic payment method is an input form in which the payer selects credit card payment or payment at a convenience store as the payment method according to the instructions displayed on the payer terminal 10C, and inputs the credit card information used for payment. , or provide information such as the payment number used when paying at a convenience store. The external electronic payment means issues a payment ID in response to payment using the selected deposit method.

After step S312, the external electronic payment means notifies the server 20 of payment information (step S411). Specifically, the external electronic payment means transmits payment information to the server 20 for each issued payment ID.

After step S411, the server 20 accepts payment information (step S209).
Specifically, the acquisition module 2032 of the server 20 records a new record in the billing DB 2028 based on payment information received from an external electronic payment means.
Further, the payment module 2035 clears the billing information. That is, the deposit module 2035 refers to the payer DB 2027 and checks whether the cost of the corresponding bill has already been deposited based on the payment ID. The deposit module 2035 records the confirmation result as a new record in the item "Deposit or not" in the billing DB 2028.

After step S214, the server 20 notifies the user of payment (step S215). Specifically, the output module 2037 of the server 20 notifies the office terminal 10B that the payment has been made. Further, the output module 2037 may issue a receipt to the payer terminal 10C. The output module 2037 may issue receipts as well as notify information regarding payment history.
With the above steps, invoice issuance and payment processing are completed.

(5-3) Billing closing process by corporate person in charge Next, we will explain billing closing process by corporate person in charge. This process can be performed from the corporate management screen displayed on the corporate terminal 10A. Here, the necessity of billing closing processing will be explained.

In a corporation that manages multiple offices, when the corporate person in charge performs accounting processing for each office, if the office person in charge changes the billing information for the billing period that is subject to closing, the corporate person in charge will be unable to perform accounting processing. There will be a difference between the billed amount recorded and the amount actually billed, which has since been changed, causing rework in the accounting process.

For this reason, in System 1, when the corporate person in charge performs accounting processing for each business location, it is possible to specify the billing period and business location, or to perform billing closing processing for all business locations at once. I can do it. Executing the billing closing process provides the following effects:
・Creation of new invoices (addition of billing information) will be restricted for the billing period subject to closing.
・Changes to invoices already issued after the billing period subject to closing (changes to billing information) are restricted.

Note that the billing period does not necessarily have to be monthly. Alternatively, the designation of the billing period may be omitted and monthly aggregation may be set as the default setting.
The processing flow of such billing closing processing will be described below.
FIG. 11 is a flowchart showing the billing closing process from the corporate person in charge.

As shown in FIG. 11, in the bill closing process, first, input of a bill closing operation is accepted on the corporate management screen displayed in step S102 of FIG. 9 (step S121).
Specifically, the operation receiving unit 171 of the corporate terminal 10A receives a billing closing operation input from a corporate person in charge. The corporate terminal 10A transmits the input billing closing processing operation to the server 20. The specific display mode of the corporate management screen at this time will be described later as a third screen example D3.

After step S121, the server 20 accepts a bill closing operation (step S221).
Specifically, the transmission/reception control module 2031 of the server 20 receives the billing closing operation transmitted from the corporate terminal 10A in step S121. At this time, the billing closing operation includes the following information:
・Person ID and corporate ID of the corporate person in charge who performed the billing closing operation
・Business office ID subject to billing closing processing
・Aggregation month (billing period) subject to billing closing processing
・Date and time of operation when billing closing process was performed

After step S221, the server 20 performs billing closing processing (step S222).
Specifically, the acquisition module 2032 of the server 20 acquires various information included in the bill closing operation received by the transmission/reception control module 2031 in step S221, and records a new record in the bill closing history DB 2029.
With the above steps, the billing closing process by the corporate person in charge is completed.

Next, the effects of such billing closing processing will be explained.
The illustrated example assumes a situation where billing information regarding the applicable billing period is viewed on the office terminal 10B after billing closing processing has been performed.

After step S222, an instruction to display billing information is input to the office terminal 10B from a person in charge at the office (step S131).
Specifically, the operation reception unit 171 of the office terminal 10B accepts an input of an instruction to display billing information operated by a corporate person on the office management screen. The office terminal 10B transmits an instruction to display billing information to the server 20. The display instructions include the following information.
・Bill number

After step S131, the server 20 receives an instruction to display billing information (step S223).
Specifically, the transmission/reception control module 2031 of the server 20 receives the billing information display instruction transmitted from the office terminal 10B in step S131. The acquisition module 2032 of the server 20 acquires the billing information display instruction and inputs it to the output module 2037.

After step S223, the server 20 outputs billing information (step S224).
Specifically, the output module 2037 of the server 20 uses the bill number included in the billing information display instruction input from the acquisition module 2032 in step S223 to refer to the billing DB 2028 and identify the corresponding billing information. and outputs it to the office terminal 10B. At this time, the output module 2037 simultaneously outputs a message indicating that changes to the billing information are restricted.

After step S224, the office terminal 10B displays billing information (step S132).
Specifically, the display processing unit 174 of the office terminal 10B displays the billing information output from the server 20 in step S224 on the display 132 of the office terminal 10B together with a message that changes to the billing information are restricted. to be displayed. The specific display mode of the office management screen at this time will be described later as a fourth screen example D4.
In this way, changes in billing information due to billing closing processing are restricted.

(5-4) Aggregation processing by a corporate person in charge Next, aggregation processing by a corporate person in charge will be explained. This process can be performed from the corporate management screen displayed on the corporate terminal 10A. In the system 1, the corporate person in charge causes the corporate terminal 10A to perform aggregation of at least one of information regarding the billing to customers at each of a plurality of business establishments and information regarding the collection status for the billing.
FIG. 12 is a flowchart showing aggregation processing of billing and collection status for each business establishment.

As shown in FIG. 12, in the aggregation process of billing information and collection information, first, an aggregation instruction is input to the corporate terminal 10A (step S141).
Specifically, the operation receiving unit 171 of the corporate terminal 10A receives a totaling instruction input from a corporate person in charge. The corporate terminal 10A transmits the input aggregation instruction to the server 20.

After step S141, the server 20 accepts a totaling instruction (step S241).
Specifically, the transmission/reception control module 2031 of the server 20 receives the aggregation instruction transmitted from the corporate terminal 10A in step S141. At this time, the aggregation instruction includes the following information.
・Person ID and corporate ID of the person in charge of the corporation who gave the aggregation instructions
・Business office ID subject to aggregation
・Aggregation month (billing period) subject to aggregation
・Aggregation items (billing information, collection status)
・Operation date and time when aggregation processing was input

After step S241, the server 20 executes aggregation processing (step S242).
Specifically, the aggregation module 2036 of the server 30 refers to the billing DB 2028 and aggregates the designated aggregation items. Here, the collection status may include a collection rate for each establishment and a breakdown of the customer's payment means.

After step S242, the server 20 outputs the total results (step S243).
Specifically, the output module 2037 of the server 20 outputs the results compiled by the tally module 2036 to the corporate terminal 10A.

After step S242, the corporate terminal 10A displays the total results (step S142).
Specifically, the display processing unit 174 of the corporate terminal 10A displays information regarding the tally results output from the server 20 in step S243 on the display 132 of the corporate terminal 10A. This allows the corporate person in charge to check the billing and collection status for each office.
With the above steps, the billing and collection status aggregation processing for each office is completed.

(5-5) Deposit account designation process by corporate person in charge Next, description will be given of deposit account designation process by corporate person in charge. This process can be performed from the corporate management screen displayed on the corporate terminal 10A. Here, the necessity of specifying a deposit account for each expense item will be explained.

For example, in a nursery school or other establishment run by a local government, childcare expenses are paid to an account managed by the local government, and expenses related to various items used by the children are paid to an account managed by the establishment. payment must be made.
In this case, conventionally, the expenses to be paid to the account managed by the local government were paid in cash from the payer, and then the business office individually transferred the fee to the relevant local government account. Collection work was complicated. The function of allocating deposit accounts according to such expense items will be explained.
FIG. 13 is a flow diagram showing the process of specifying a deposit account.

In the deposit account designation process, first, a deposit account is designated for each expense item at the corporate terminal 10A (step S151).
Specifically, the operation receiving unit 171 of the corporate terminal 10A receives an operation for specifying a deposit account for each expense item input from a corporate person in charge. The corporate terminal 10A transmits an operation for specifying a deposit account to the server 20.

After step S151, the server 20 accepts the designation of a deposit account (step S251).
Specifically, the transmission/reception control module 2031 of the server 20 receives the designation operation transmitted from the corporate terminal 10A in step S151. At this time, the specification operation includes the following information.
・Person ID and corporate ID of the person in charge of the corporation who performed the specified operation
・Business establishment ID to be specified
・Expenses subject to specification ・Account ID of deposit account subject to specification

After step S251, the server 20 performs master registration of the designated account (step S252).
Specifically, the acquisition module 2032 of the server 20 acquires information included in the designation operation received by the transmission/reception control module 2031 in step S251, and records a new record in the designated account master DB 2030.
With the above steps, the deposit account designation process is completed.

Next, the effect of such a process of specifying a deposit account for each expense item will be explained.
For example, assume that the payment shown in FIG. 10 is executed (step S312) after step S252 described above.

In this case, in step S253, the server 20 instructs the financial institution to deposit the money into the designated account as the deposit destination (step S253).
Specifically, the deposit module 2035 of the server 20 aggregates the expenses paid by the payer to the payment account for each expense item, and then notifies the financial institution of the deposit to the corresponding designated account. . The financial institution deposits the totaled expenses for each item according to the specified details into the corresponding designated account.

After step S253, the server 20 issues a payment notification (step S254).
Specifically, the output module 2037 of the server 20 outputs to the corporate terminal 10A a notification that the totaled expenses for each expense item have been deposited into the designated account.

After step S254, the corporate terminal 10A receives the payment notification (step S152).
Specifically, the display processing unit 174 of the corporate terminal 10A displays on the display 132 of the corporate terminal 10A that the instruction to deposit has been given to the financial institution in step S254. This allows the person in charge of the corporation to confirm that the funds have been deposited into the designated account for each expense item.
In this way, in the system 1, the person in charge of the corporation can deposit money into the designated deposit account for each expense item designated in advance.

(6) Screen example Next, a screen example of the system 1 will be described.

(6-1) First screen example D1
A first screen example D1 shown in FIG. 14 is a diagram showing a corporate management screen displayed on the corporate terminal 10A in the management screen display process in step 102 shown in FIG.
On the corporate management screen, as shown in display columns C1 to C3, the billed amount and payment amount (collected amount) for each office managed by the corporation are displayed. By clicking on each display column, the person in charge of the corporation can transition to a management screen for each office (second screen example D2 to be described later).

Further, the corporate management screen displays a collective closing operation button B1 for performing collective closing processing, and individual closing operation buttons B2 to B4 for performing closing processing for each office. When the corporate person in charge clicks the batch closing operation button B1, bill closing processing for all offices is executed. On the other hand, when the corporate person in charge clicks on any of the individual closing operation buttons B2 to B4, bill closing processing for the corresponding individual facility is executed.

Further, on the corporate management screen, an operation button B5 for downloading billing information of all offices is displayed next. When the corporate person in charge clicks the operation button B5, billing information for all offices is downloaded at once.

(6-2) Second screen example D2
A second screen example D2 shown in FIG. 15 is a diagram showing a business office management screen displayed on the business office terminal 10B in the management screen display process in step 102 shown in FIG.
On the office management screen, as shown in display column C4, a list of billing information for the current month is displayed. By clicking on each field in the list, you can view the billing details for each field.

Further, on the office management screen, a collection status display field C5 is displayed that shows the collection status of all bills for the current month at the office. In the collection status display column C5, the collection status is displayed in a pie chart, and the person in charge of the office and the person in charge of the corporation can intuitively understand the collection status.

(6-3) Third screen example D3
A third screen example D3 shown in FIG. 16 is a diagram showing a corporate management screen displayed on the corporate terminal 10A in the bill closing operation in step S121 shown in FIG.
On this corporate management screen, as shown in the confirmation message field C6, by performing batch closing processing, operations on the business side are restricted for changing billing information for the billing period that is subject to closing at all facilities. is displayed. By clicking the execution button B6, the billing closing process is executed.

(6-4) Fourth screen example D4
A fourth screen example D4 shown in FIG. 17 is a diagram showing a business office management screen displayed on the business office terminal 10B in the billing information display process in step S132 shown in FIG.
On this office management screen, as shown in the confirmation message field C7, the billing closing process has already been executed, and new billing and billing information changes are restricted for the billing period subject to closing. Displayed. By clicking the re-billing button B7, it is possible to execute re-billing by issuing a bill again without changing the billing information for the billing period that has already been created and is subject to closing.

(7) Summary As explained above, according to the system 1 according to the present embodiment, it is possible to receive input from the corporate terminal 10A of billing information for customers and aggregation instructions regarding the collection status at each of a plurality of business establishments. Then, the information is totaled and output to the corporate terminal 10A.
Therefore, in a corporation that operates multiple offices, it is possible to smoothly manage the collection operations at each office.

Further, the system 1 determines the user authority granted to the person in charge, and outputs a corporate management screen to the corporate terminal 10A if the person in charge is granted a predetermined authority. Therefore, by separating the management screens that can be viewed and operated depending on the roles of the corporate person and the office person, it is possible to encourage appropriate management by the corporate person.

Furthermore, in response to receiving input from the corporate terminal 10A for billing closing processing specifying a billing period, the system 1 restricts changes to billing information in the billing period. For this reason, we prevent billing information from being changed at the business office after the corporate person in charge has compiled the sales for the billing period subject to closing, and we prevent the billing amount from being changed due to subsequent changes to billing information. Matching can occur and be avoided.

In addition, in the system 1, the collected money collection status includes at least one of the collection rate for each office and the details of the customer's payment means. Therefore, it is possible to provide information to the person in charge of the corporation after performing a multifaceted evaluation of the collection situation.

In addition, in the system 1, regarding payments related to invoices from the corporate terminal 10A, after receiving the designation of the deposit account that is the account to which the money should be deposited for each billing expense item, the system 1 You can collect the total amount and deposit the money into the designated deposit account. As a result, for example, at a business establishment such as a nursery school managed by a local government, expenses such as childcare fees that should be paid to the local government and expenses related to various goods that should be paid to the business establishment will be automatically paid. It will be possible to allocate the payment destination. Therefore, it is possible to reduce the hassle of having to individually transfer money from the business office to the local government account after receiving cash payments. Furthermore, from the payer's perspective, it is possible to avoid complications in payment due to requests for multiple transfers for each expense item.

(8) Modification Next, a modification of the system 1 will be described.
Although the above embodiment has been described using an example of a corporation that operates an educational business, the present invention is not limited to this type of embodiment. System 1 can be used by corporations running various businesses.

Further, the designation of a deposit account for each expense item is not limited to a person in charge at a corporation, and may be performed by a person in charge at a business office by operating the business office terminal 10B.
In addition, the designation of the deposit account may be made by accepting the designation by business office in addition to the designation by expense item, and by further subdividing the designation and registering the designated account master.

Further, the authority of the person in charge is not limited to two, corporate authority and office authority, but may be further subdivided. For example, the role names in the role DB 2025 may be subdivided into three or more, and a corresponding authority may be provided for each role. Examples are listed below.
・Corporate administrator: Has operational authority for all functions on the corporate management screen. ・Corporate person in charge: Has operational authority for some functions on the corporate management screen.
- Office administrator: Has operational authority for all functions on the office management screen.
- Office person in charge: Has operational authority for some functions on the office management screen.

Furthermore, in each of the above embodiments, the server 20 receives information input from the terminal device 10, performs necessary calculations, and displays the information on the terminal device 10. I can't.
For example, for some or all of the above functions, the terminal device 10 may accept input, process the input within the terminal device 10, and display the input on the display 132 of the terminal device 10. In order to have such a configuration, the user may access the server 20 via the terminal device 10, install a program provided by the server 20 into the terminal device 10, and perform processing within the terminal device 10. . In this case, the server 20 does not need to include some or all of the functional modules described above as its functions.

Although the preferred embodiments of the present disclosure have been described above, the present disclosure is not limited to such specific embodiments, and the present disclosure includes the inventions described in the claims and their equivalents. It will be done. Further, a part of the configurations of the apparatuses described in the above embodiments and modified examples can be omitted or combined as long as no technical contradiction occurs.

(9) Additional notes The matters explained in each of the above embodiments are added below.

(Appendix 1 )
A program that is equipped with a processor and is executed by a collection system used for collecting money from customers at business offices by a corporation that manages multiple business offices,
The program is sent to the processor
A step of accepting input from a terminal device used by a person in charge of the corporation of an aggregation instruction for at least one of information regarding customer invoices at each of a plurality of business offices and information regarding the collection status of the invoices (step S241). and,
In response to receiving the aggregation instruction, a step of aggregating at least one of information regarding billing for each office and information regarding the collection status (step S242);
A program that causes a step of outputting the aggregated information to a terminal device (step S243).

(Additional note 2)
In addition, the processor
a step of determining user authority granted to the person in charge (step S202);
If the person in charge is granted a predetermined authority, a step (step S203) of outputting a management screen for the corporate person in charge, which is a screen for inputting aggregation instructions, to the terminal device is executed. The program according to claim 1, wherein the program causes

(Appendix 3)
In addition, the processor
a step of receiving input from a terminal device for billing closing processing specifying a business office (step S221);
The program according to claim 1, which executes the step of restricting changes to billing information at a business office (step S222) in response to input of billing closing processing.

(Additional note 4)
2. The program according to claim 1, wherein the collection status includes at least one of a collection rate for each establishment and a breakdown of customer payment methods.

(Appendix 5)
In addition, the processor
a step of accepting from the terminal device a designation of a deposit account, which is an account to which payment should be made, for each billing expense item for payment related to the bill (step S251);
2. The program according to claim 1, wherein the program executes a step (step S253) of aggregating expenses paid by a customer for each expense item and depositing the money into a designated deposit account.

(Appendix 6)
A method carried out by a collection system equipped with a processor and used for collecting money from customers at business establishments by a corporation that manages multiple business establishments, the method comprising:
The method is that the processor
A step of accepting input from a terminal device used by a person in charge of the corporation of an aggregation instruction for at least one of information regarding customer invoices at each of a plurality of business offices and information regarding the collection status of the invoices (step S241). and,
In response to receiving the aggregation instruction, a step of aggregating at least one of information regarding billing for each office and information regarding the collection status (step S242);
A method comprising: outputting the aggregated information to a terminal device (step S243).

(Appendix 7)
A bill collection system equipped with a processor and used for collecting money from customers at business locations by a corporation that manages multiple business locations,
In the collection system, the processor
means for receiving, from a terminal device used by a person in charge of the corporation, an input of aggregation instructions for at least one of information regarding invoices to customers at each of a plurality of business offices, and information regarding the collection status of said invoices;
means for aggregating at least one of information regarding billing for each office and information regarding collection status in response to receiving an aggregation instruction;
A bill collection system comprising means for outputting aggregated information to a terminal device.

1 Bill collection system 10A Corporate terminal 10B Business terminal 10C Payer terminal 20 Server 202 Storage unit 203 Control unit 2031 Transmission/reception control module 2032 Acquisition module 2033 Account authentication module 2034 Billing module 2035 Deposit module 2036 Totalization module 2037 Output module

Claims (6)

A program that is equipped with a processor and is executed by a collection system used for collecting money from customers at the business establishments by a corporation that manages multiple business establishments,
The program causes the processor to:
receiving input from a terminal device used by a person in charge of the corporation for aggregation instructions for at least one of information regarding the billing to the customer at each of the plurality of business offices and information regarding the collection status of the bill; ,
In response to receiving the aggregation instruction, aggregating at least one of the billing information and the money collection status information for each business establishment;
outputting the aggregated information to the terminal device ;
receiving from the terminal device an input of billing closing processing for specifying the business office or for all the business offices;
A program that causes the program to execute the step of restricting changes to billing information at a specified business office or all of the business offices in response to input of the bill closing process . The bill collection system includes a memory, and the memory stores user authority granted to the person in charge,
The processor further includes:
determining the user authority granted to the person;
If the person in charge is granted a predetermined authority, the step of outputting to the terminal device a management screen for a corporate person, which is a screen for inputting the aggregation instructions, is executed. , The program according to claim 1. 2. The program according to claim 1, wherein the collection status includes at least one of a collection rate for each business establishment and a breakdown of the customer's payment means. The processor further includes:
receiving from the terminal device a designation of a deposit account, which is the account to which the payment should be made, for each expense item of the claim, for payment related to the claim;
2. The program according to claim 1, wherein the program executes the step of totaling up the expenses paid by the customer for each expense item and depositing the money into the specified deposit account. A method carried out by a collection system equipped with a processor and used for collecting money from customers at said business establishments by a corporation that manages a plurality of business establishments, the method comprising:
The method includes the processor:
receiving input from a terminal device used by a person in charge of the corporation for aggregation instructions for at least one of information regarding the billing to the customer at each of the plurality of business offices and information regarding the collection status of the bill; ,
In response to receiving the aggregation instruction, aggregating at least one of the billing information and the money collection status information for each business establishment;
outputting the aggregated information to the terminal device ;
receiving from the terminal device an input of billing closing processing for specifying the business office or for all the business offices;
and restricting changes to billing information at a specified business location or all of the business locations in response to input of the bill closing process . A bill collection system equipped with a processor and used by a corporation managing multiple business locations to collect money from customers at the business locations, the system comprising:
In the bill collection system, the processor:
means for receiving, from a terminal device used by a person in charge of the corporation, an input of an aggregation instruction for at least one of information regarding the billing to the customer at each of the plurality of business offices and information regarding the collection status of the bill; ,
means for aggregating at least one of the information regarding the billing and the information regarding the collection status for each business establishment in response to receiving the aggregation instruction;
means for outputting the aggregated information to the terminal device ;
means for receiving input of billing closing processing from the terminal device by specifying the business office or for all the business offices;
A bill collection system comprising: means for restricting changes in billing information at a specified business office or all of the business offices in response to input of the bill closing process .