JP2024091715A - Electronic money collection bag system and money collection processing apparatus - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an electronic money collection bag system and a money collection processing apparatus.

SOLUTION: An electronic money collection bag system performs money collection processing by an electronic money collection bag by generating the electronic money collection bag on a server apparatus than can be accessed from a money-collector terminal and a money collection target terminal, and receiving deposit processing and withdrawal processing for the generated electronic money collection bag. The server apparatus generates the electronic money collection bag identified by an identifier including money collection information including information on a money collection target, a money collection amount, and a due date for money collection, and processing information indicating a processing status of the money collection processing, for each of money collection processing, notifies the money collection target terminal of the information on the money collection amount and the due date for money collection by the electronic money collection bag when generating the electronic money collection bag, and when receiving a deposit to the electronic money collection bag or withdrawal of the electronic money collection bag, updates the processing information and notifies the money collector terminal of the updated processing information.

SELECTED DRAWING: Figure 7

COPYRIGHT: (C)2024,JPO&INPIT

Description

The present invention relates to an electronic money collection bag system and a money collection processing device.

In schools such as elementary and junior high schools, envelope-shaped collection bags are commonly used to collect various fees from students' parents, such as for textbooks, school lunches, PTA (Parent-Teacher Association) membership fees, and photograph fees (see, for example, Patent Document 1).

For example, if an elementary school teacher collects 500 yen for textbook fees from each child's household, the teacher writes "textbook fees" and "500 yen" in the collection item and amount columns on a collection envelope, and hands it to the child. The child takes the envelope home and hands it to the child's guardian. The child's guardian checks the collection item and amount columns on the envelope, puts the textbook fee of 500 yen into the envelope, and hands it to their child. The child takes the envelope with the textbook fee inside to school and hands it to the teacher. After the teacher checks that the envelope contains the required fee of 500 yen, he or she stamps or signs the receipt column. In this way, the school is able to collect textbook fees from each child's household.

Japanese Patent Application Laid-Open No. 9-203334

However, when collecting various fees using the above-mentioned collection bags, the guardians of the children must prepare coins to avoid receiving change, which can be a hassle. In addition, the children must carry cash, which creates the problem of the risk of it being lost.

The present invention aims to provide an electronic money collection bag system and a money collection processing device that can perform money collection processing without using actual money collection bags.

The electronic collection envelope system according to one aspect of the present invention is an electronic collection envelope system that generates an electronic collection envelope on a server device accessible from the collector terminal and the collection target terminal, and performs collection processing using the electronic collection envelope by accepting deposit processing and withdrawal processing for the generated electronic collection envelope, and the server device generates an electronic collection envelope that includes collection information including information on the collection target, the collection amount, and the collection date, as well as processing information indicating the processing status of the collection processing, and is identified by an identifier, and when the electronic collection envelope is generated, it notifies the collection target terminal of information regarding the collection amount and collection date using the electronic collection envelope, and when it accepts a deposit into the electronic collection envelope or a withdrawal from the electronic collection envelope, it updates the processing information and notifies the collector terminal of the updated processing information.

A collection processing device according to one aspect of the present invention is capable of communicating with a collector terminal and a collection target terminal, and performs collection processing using an electronic collection bag. For each collection process, the device generates an electronic collection bag that includes collection information including information regarding the collection target, the collection amount, and the collection date, as well as processing information indicating the processing status of the collection process and is identified by an identifier. When the electronic collection bag is generated, the device notifies the collection target terminal of information regarding the collection amount and collection date using the electronic collection bag, and when a deposit into the electronic collection bag or a withdrawal from the electronic collection bag is accepted, the device updates the processing information and notifies the collection terminal of the updated processing information.

According to this application, the money collection process can be carried out without using actual money collection bags.

FIG. 1 is a schematic explanatory diagram illustrating a bill collection processing system according to a first embodiment. FIG. 2 is a block diagram illustrating the internal configuration of a bill collector terminal. FIG. 2 is a block diagram illustrating the internal configuration of a payer terminal. FIG. 2 is a block diagram illustrating an internal configuration of the server device. FIG. 13 is a conceptual diagram illustrating an example of a bill collector table. FIG. 13 is a conceptual diagram illustrating an example of a payer table. 1 is a conceptual diagram showing an example of a data structure of an electronic money collection envelope registered in an electronic money collection envelope database. FIG. 10 is a flowchart illustrating a procedure of a process executed by a bill collector terminal, a payer terminal, and a server device. 13 is a flowchart illustrating a procedure of a process executed by a payer terminal and a server device according to the second embodiment. FIG. 13 is a schematic diagram showing an example of a display screen showing the contents of a request. FIG. 13 is a schematic diagram showing an example of a payment screen. 13 is a flowchart illustrating a procedure of a process executed by a bill collector terminal and a server device according to the third embodiment. FIG. 13 is a schematic diagram showing an example of a payment status confirmation screen.

Hereinafter, the present invention will be described in detail with reference to the drawings showing embodiments thereof.
(Embodiment 1)
Fig. 1 is a schematic explanatory diagram illustrating a bill collection system according to embodiment 1. The bill collection system according to embodiment 1 includes a bill collector terminal 10 used by a bill collector, a payer terminal 20 used by a payer (a person to be collected), and a server device 30 that executes bill collection. The bill collector terminal 10, the payer terminal 20, and the server device 30 are connected to each other so as to be able to communicate with each other via a network N such as the Internet or a dedicated line.

In this embodiment, for example, if it is assumed that a school teacher collects various fees such as school lunch fees, PTA membership fees, and photo fees from the parents of students, the person who collects the fees is the school teacher, and the person who pays the collected amount is the parents of the students. Furthermore, the collection process is carried out by a financial institution such as a bank. For this reason, the server device 30 is installed in a financial institution. Note that the collector does not need to be a specific person, and can be any organization such as a school.

When a collection event occurs to collect various fees, the server device 30 generates an electronic collection envelope. For example, when collecting photo fees, the server device 30 may generate an electronic collection envelope in response to a request from the collector. In addition, when collecting fees periodically, such as when collecting school lunch fees or PTA membership fees, the server device 30 may automatically generate an electronic collection envelope at regular intervals, such as once a month. The electronic collection envelope generated by the server device 30 is a temporary virtual account generated for each collection item and each payer, and includes an identifier (hereinafter referred to as an envelope ID), collection information including information on the payer, the amount collected, and the collection date, processing information indicating the processing status of the collection process, and authority information defining various authorities.

When the server device 30 generates an electronic collection envelope, it references the collection information in the electronic collection envelope and notifies the notification destination associated with the payer of information regarding the collection amount and collection date. Here, the notification destination associated with the payer is, for example, an email address used by the payer. The collection information notified by the server device 30 is displayed on the payer terminal 20.

When the payer is notified of information regarding the amount to be collected and the collection date by the server device 30, the payer deposits the amount into the electronic collection envelope. The electronic collection envelope is prepared as a virtual account at a financial institution, so the payer can deposit the amount into the electronic collection envelope by transferring the amount to be collected into this virtual account. The amount to be collected may also be deposited into the electronic collection envelope by automatic deduction from the payer's own account to the virtual account.

When the collected amount is deposited in the electronic collection envelope, the server device 30 executes a settlement process. The server device 30 may execute the settlement process on the collection due date, or may execute the settlement process without waiting for the collection due date. Through the settlement process of the server device 30, the collected amount collected using the electronic collection envelope is transferred from the electronic collection envelope to the collector's designated account.

Figure 2 is a block diagram explaining the internal configuration of the bill collector terminal 10. The bill collector terminal 10 is a terminal device such as a personal computer, and includes a control unit 11, a memory unit 12, a communication unit 13, an operation unit 14, and a display unit 15.

The control unit 11 includes, for example, a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), etc. The CPU of the control unit 11 controls the operation of the various hardware components described above by expanding into the RAM and executing various programs that are pre-stored in the ROM or the storage unit 12.

The control unit 11 is not limited to the above configuration, and may be any processing circuit including one or more CPUs, multi-core CPUs, microcomputers, etc. The control unit 11 may also have functions such as a clock that outputs date and time information, a timer that measures the elapsed time from when an instruction to start measurement is given to when an instruction to end measurement is given, and a counter that counts numbers.

The memory unit 12 includes a storage device using a flash memory, a hard disk, etc. The memory unit 12 stores various computer programs executed by the control unit 11, and data necessary for executing the computer programs. The computer programs stored in the memory unit 12 include an operating system, which is a program for controlling the overall operation of the bill collector terminal 10, and application programs for accepting input of various data from bill collectors.

The programs stored in the memory unit 12 may be provided by a non-transitory recording medium on which the programs are recorded in a readable manner. The recording medium is, for example, a portable memory such as a CD-ROM, a USB memory, a Secure Digital (SD) card, a micro SD card, or a CompactFlash (registered trademark). In this case, the control unit 11 can read the various programs from the recording medium using a reading device (not shown) and install the various programs that have been read into the memory unit 12. The programs stored in the memory unit 12 may also be provided by communication via the communication unit 13. In this case, the control unit 11 can obtain the various programs through the communication unit 13 and install the obtained various programs into the memory unit 12.

The communication unit 13 has a connection interface for connecting to the network N. When the communication unit 13 receives information transmitted from the server device 30 or the like via the network N, it outputs the received information to the control unit 11. The control unit 11 executes appropriate processing based on the information received via the communication unit 13. Furthermore, when the communication unit 13 obtains information to be transmitted to the server device 30 or the like from the control unit 11, it transmits the information to the server device 30 or the like via the network N.

The operation unit 14 has an input interface such as a keyboard and a mouse, and accepts operations by the bill collector. The display unit 15 has an LCD display device and the like, and displays information to be notified to the bill collector.

Figure 3 is a block diagram explaining the internal configuration of the payer terminal 20. The payer terminal 20 is a terminal device such as a smartphone or a personal computer, and includes a control unit 21, a memory unit 22, a communication unit 23, an operation unit 24, and a display unit 25.

The control unit 21 includes, for example, a CPU, a ROM, a RAM, etc. The CPU of the control unit 21 controls the operation of the various hardware components described above by expanding into the RAM and executing various programs that are pre-stored in the ROM or the storage unit 22.

The control unit 21 is not limited to the above configuration, and may be any processing circuit including one or more CPUs, multi-core CPUs, microcomputers, etc. The control unit 21 may also have functions such as a clock that outputs date and time information, a timer that measures the elapsed time from when an instruction to start measurement is given to when an instruction to end measurement is given, and a counter that counts numbers.

The memory unit 22 includes a storage device using a flash memory, a hard disk, etc. The memory unit 22 stores various computer programs executed by the control unit 21, and data necessary for executing the computer programs. The computer programs stored in the memory unit 22 include an operating system, which is a program for controlling the overall operation of the payer terminal 20, and application programs for accepting input of various data from the payer.

The programs stored in the memory unit 22 may be provided by a non-transitory recording medium on which the programs are recorded in a readable manner. The recording medium is, for example, a portable memory such as a CD-ROM, a USB memory, an SD card, a micro SD card, or a compact flash. In this case, the control unit 21 can read the various programs from the recording medium using a reading device (not shown) and install the various programs that have been read into the memory unit 22. The programs stored in the memory unit 22 may also be provided by communication via the communication unit 23. In this case, the control unit 21 can obtain the various programs through the communication unit 23 and install the obtained various programs into the memory unit 22.

The communication unit 23 has a connection interface for connecting to the network N. When the communication unit 23 receives information transmitted from the server device 30 or the like via the network N, it outputs the received information to the control unit 21. The control unit 21 executes appropriate processing based on the information received via the communication unit 23. Furthermore, when the communication unit 23 obtains information to be transmitted to the server device 30 or the like from the control unit 21, it transmits the information to the server device 30 or the like via the network N.

The operation unit 24 is equipped with an input interface such as a keyboard and a mouse, and accepts operations by the payer. The display unit 25 is equipped with a liquid crystal display device, etc., and displays information to be notified to the payer.

Figure 4 is a block diagram illustrating the internal configuration of the server device 30. The server device 30 includes, for example, a control unit 31, a memory unit 32, a communication unit 33, an operation unit 34, and a display unit 35.

The control unit 31 includes, for example, a CPU, a ROM, a RAM, etc. The CPU of the control unit 31 controls the operation of the various hardware components described above by expanding into the RAM various programs pre-stored in the ROM or the storage unit 32 and executing them, causing the entire device to function as the money collection processing device of the present application.

The control unit 31 may also have functions such as a clock that outputs date and time information, a timer that measures the elapsed time from when an instruction to start measurement is given to when an instruction to end measurement is given, and a counter that counts numbers.

The memory unit 32 includes a storage device using a flash memory, a hard disk, etc. The memory unit 32 stores various computer programs executed by the control unit 31 and various data.

The computer programs stored in the memory unit 32 include an operating system, which is a computer program for controlling the overall operation of the server device 30, as well as a collection processing program 320. This collection processing program 320 is a computer program for causing the server device 30 to execute processes such as generating an electronic collection envelope in response to a collection event, and notifying the collection target of the collection amount and collection date.

The program stored in the storage unit 32 may be provided by a non-transitory recording medium M on which the program is readably recorded. The recording medium M may be, for example, a CD-ROM.
, a portable memory such as a USB memory, an SD card, a micro SD card, or a compact flash. In this case, the control unit 31 can read the various programs from the recording medium M using a reading device (not shown) and install the read various programs in the storage unit 32. The programs stored in the storage unit 32 may be provided by communication via the communication unit 33. In this case, the control unit 31 can obtain the various programs through the communication unit 33 and install the obtained various programs in the storage unit 32.

The memory unit 32 also has a collector table 321 in which information about collectors is registered, a payer table 322 in which information about payers is registered, and an electronic collection envelope database 323 in which data on electronic collection envelopes is registered. The collector table 321, payer table 322, and electronic collection envelope database 323 will be described in detail later.

The communication unit 33 has a connection interface for connecting to the network N. When the communication unit 33 receives information transmitted from the bill collector terminal 10, the payer terminal 20, etc., via the network N, it outputs the received information to the control unit 31. The control unit 31 executes appropriate processing based on the information received via the communication unit 33. In addition, when the communication unit 33 obtains information to be transmitted to the bill collector terminal 10, the payer terminal 20, etc. from the control unit 31, it transmits the information to the bill collector terminal 10, the payer terminal 20, etc. via the network N.

The operation unit 34 has an input interface such as a keyboard and a mouse, and accepts operations by employees. The display unit 35 has an LCD display device or the like, and displays information to be notified to employees. Note that in this embodiment, the server device 30 is configured to have the operation unit 34 and the display unit 35, but the operation unit 34 and the display unit 35 are not essential, and the server device 30 may be configured to accept operations via an externally connected computer and output information to be notified to the external computer.

In this embodiment, for the sake of simplicity, the server device 30 is described as a single device, but it may be configured with multiple processing devices, or may be configured with one or more virtual machines.

Figure 5 is a conceptual diagram showing an example of the collector table 321. Information about collectors is registered in the collector table 321. Information registered in the collector table 321 includes, for example, the collector ID, the collector's name, the collector's affiliation, the email address used by the collector, and information about the account designated by the collector.

Figure 6 is a conceptual diagram showing an example of the payer table 322. Information about the payer is registered in the payer table 322. Information registered in the payer table 322 includes, for example, the payer ID, payer name, student name, school name, grade, class, attendance number, email address used by the payer, account information specified by the payer, etc.

Figure 7 is a conceptual diagram showing an example of the data structure of an electronic collection envelope registered in the electronic collection envelope database 323. The electronic collection envelope has a field in which the envelope ID is registered, a field in which collection information is registered, a field in which processing information is registered, and a field in which authority information is registered. The envelope ID is an identifier that identifies each electronic collection envelope. Collection information includes information on the payer, the amount collected, and the collection due date. Collection information may further include information on the name of the collection and the collector. Processing information includes information on status such as unpaid, paid, and settlement completed, and processing dates such as the deposit date and settlement completion date. Authority information is information on processing authority including deposit authority, withdrawal authority, and reference authority.

In response to a request from a collector, the server device 30 generates an electronic collection envelope having the above-mentioned fields and registers the necessary information in each field. The electronic collection envelope is used in the collection process by the server device 30. Here, the collection process by the server device 30 includes a process of referencing the collection information each time an electronic collection envelope is generated, notifying the notification destination associated with the payer of information regarding the collection amount and collection date, a process of updating the processing information when a deposit process that satisfies the deposit authority or a withdrawal process that satisfies the withdrawal authority is received, and a process of reading and outputting at least one of the collection information and the processing information in response to a reference request that satisfies the reference authority.

The electronic collection envelope illustrated in FIG. 7 has an envelope ID of "#123", indicating that it is an electronic collection envelope generated to collect "photo fees" from a payer (Mr. A) identified by a payer ID of "P001". It also indicates that the collector of this electronic collection envelope is a collector (Mr. X) identified by a collector ID of "C001". In response to the generation of this electronic collection envelope, the server device 30 notifies the payer of the collected amount (e.g., 525 yen) and the collection date (November 20, 2018). After the information on the collected amount and collection date is notified, the deposit process into the electronic collection envelope, the withdrawal process from the electronic collection envelope, and the settlement process are performed. Note that these processes are performed by a person who has the set processing authority. When the deposit process, withdrawal process, or settlement process is performed, the processing information (status and processing date) of the electronic collection envelope is updated. For example, when a deposit process is performed for an electronic money collection bag with a bag ID of "#123", the status is updated from "Not Deposited" to "Deposited", and the processing date is updated to the date when the deposit is completed (for example, November 10, 2018). Also, when the payment process is completed by the server device 30, the status is updated from "Deposited" to "Payment Completed", and the processing date is updated to the date when the payment is completed.

The operation of the bill collection system according to this embodiment will be described below.
8 is a flow chart for explaining the procedure of the process executed by the collector terminal 10, the payer terminal 20, and the server device 30. The control unit 11 of the collector terminal 10 accepts collection information including information on the payer, the collection amount, and the collection date through the operation unit 14 (step S101). The control unit 11 may accept, as the information on the payer, for example, the name of the payer, the e-mail address used by the payer, the account information of the payer, etc. In addition, if the information on the payer has already been registered in the payer table 322 of the server device 30, the control unit 11 may accept the payer ID as the information on the payer. Furthermore, the control unit 11 may accept a group ID specifying multiple payers, and accept information on the collection amount to be collected and the collection date from each of the multiple payers belonging to the group.

Next, the control unit 11 of the collector terminal 10 transmits a collection request including information such as the payer, the amount to be collected, and the amount to be collected to the server device 30 via the communication unit 13 (step S102).

When the control unit 31 of the server device 30 receives a collection request transmitted from the collector terminal 10 via the communication unit 33 (step S103), it generates an electronic collection envelope (step S104). At this time, the control unit 31 issues an envelope ID to be assigned to the electronic collection envelope, and generates an electronic collection envelope including the issued envelope ID, collection information, processing information, and authority information. The envelope ID, collection information, processing information, and authority information are entered into the above-mentioned fields, and are registered in the electronic collection envelope database 323 as an electronic collection envelope. The deposit authority included in the authority information is granted to the payer, the withdrawal authority is granted to the financial institution (server device 30), and the reference authority is granted to the payer and the collector.

When the control unit 31 generates an electronic collection envelope, it refers to the collection information and notifies the payer of the collection amount and collection date (step S105). At this time, the control unit 31 sends an email containing the collection amount and collection date information from the communication unit 33 and addressed to the payer's email address. The payer's email address is associated with the payer ID and registered in the payer table 322.

The control unit 21 of the payer terminal 20 receives a notification including information on the amount collected and the collection due date from the server device 30 via the communication unit 23 (step S106), and displays the information on the amount collected and the collection due date included in the notification on the display unit 25 (step S107).

After transmitting information on the amount to be collected and the collection date, the control unit 31 of the server device 30 waits for a deposit to be made into the electronic collection bag. When accepting a deposit process, the control unit 31 may confirm the deposit authority of the depositor. For example, the control unit 31 can confirm the deposit authority by performing user authentication using a user ID and password, etc., and determining whether the user identified by the user authentication is the same as the authorized person set in the authority information (deposit authority) of the electronic collection bag. When a deposit is made into the electronic collection bag, the control unit 31 updates the processing information (status and processing date) in the electronic collection bag (step S108).

The deposit into the electronic collection envelope is carried out in a manner similar to the general transfer process at financial institutions. The server device 30 may also accept the payer's selection of the method for depositing money into the electronic collection envelope. For example, the server device 30 may display a selection screen on the display unit 25 of the payer terminal 20 that allows the payer to select credit card payment, electronic money payment, virtual currency payment, payment with valuable points, etc., and accept the deposit into the electronic collection envelope using the payment method selected by the payer.

Furthermore, in cases where the amount to be collected is relatively large, the server device 30 may accept the deposit into the electronic money collection envelope in multiple installments.

Next, the control unit 31 executes the settlement process at an appropriate timing (step S109). The control unit 31 executes the settlement process by withdrawing the collected amount from the electronic collection envelope and depositing it into the account specified by the collector. The control unit 31 may execute the settlement process on the day of the collection due date, or may execute the settlement process without waiting for the collection due date. Furthermore, if the collected amount is relatively high and deposits are accepted into the electronic collection envelope in multiple installments, the control unit 31 may execute the settlement process when the total amount deposited reaches the collected amount. After executing the settlement process, the control unit 31 updates the processing information (status and processing date) in the electronic collection envelope (step S110). When the settlement process is completed, the control unit 31 transmits a notification that the settlement has been completed to the collector terminal 10 via the communication unit 33 (step S111).

The control unit 11 of the collector terminal 10 receives a notification that the payment has been completed from the server device 30 via the communication unit 13 (step S112), and displays the received notification on the display unit 15 (step S113).

As described above, the server device 30 according to this embodiment generates an electronic collection envelope for each collection item and each payer, and executes the collection process using the electronic collection envelope, so that the collection process can be executed without using an actual collection envelope. This eliminates the need to worry about letting children carry cash, and eliminates the need to prepare coins each time a payment is collected to avoid receiving change.

(Embodiment 2)
In the second embodiment, a configuration will be described in which the server device 30 notifies the payer terminal 20 of the billing details to the payer in response to a viewing request from the payer terminal 20.

Figure 9 is a flowchart explaining the procedure of the process executed by the payer terminal 20 and the server device 30 according to the second embodiment. When the control unit 21 of the payer terminal 20 receives a request to view the contents of the bill to the payer via the operation unit 24 (step S201), the control unit 21 transmits the request to view including the payer ID to the server device 30 via the communication unit 23 (step S202).

When the control unit 31 of the server device 30 receives a request to view the billing details through the communication unit 33 (step S203), it searches the electronic collection envelope database 323 for electronic collection envelopes with a status of "unpaid" using the payer ID included in the view request as a search key (step S204). At this time, the control unit 31 may check the viewing authority. For example, the control unit 31 can check the viewing authority by performing user authentication using a user ID and password, etc., and determining whether the user identified by the user authentication is the same as the authorized person set in the authority information (viewing authority) of the electronic collection envelope. When a search result is obtained, the control unit 31 returns the search result to the payer terminal 20 through the communication unit 33 (step S205).

The control unit 21 of the payer terminal 20 receives the search results transmitted from the server device 30 via the communication unit 23 (step S206). The control unit 21 generates a display screen showing the contents of the claim based on the search results of the server device 30, and displays the generated display screen on the display unit 25 (step S207).

Figure 10 is a schematic diagram showing an example of a display screen showing the contents of a claim. The claim screen 250 shown in Figure 10 shows the contents of a claim to a specific payer (for example, a payer with a payer ID of "P001"). In this example, a claim made using an electronic collection bag with a bag ID of "#123" and a claim made using an electronic collection bag with a bag ID of "#456" are shown. Payment buttons 251 and 252 are assigned to each claim. The payment buttons 251 and 252 are software buttons that can be operated using the operation unit 24. When the payment buttons 251 and 252 are operated, the control unit 21 transitions the display on the display unit 25 to a payment screen 260 (see Figure 11). In addition, a close button 253 is arranged on the claim screen 250 shown in Figure 10 to accept an operation to close the screen without making a payment.

11 is a schematic diagram showing an example of a payment screen 260. The payment screen 260 shown in FIG. 11 shows an example of a display screen displayed on the display unit 25 when the payment button 251 is operated on the billing screen 250 described above. The payment screen 260 has a start button 261 for starting payment and a close button 262 for closing the screen without starting payment. The start button 261 and the close button 262 are software buttons that can be operated using the operation unit 24. When the start button 261 is operated, the control unit 21 transmits a payment start instruction specifying the bag ID "#123" to the server device 30 through the communication unit 23. The server device 30 that has received the payment start instruction refers to the payer's account information registered in the payer table 322, and deposits the collected amount from the payer's account into the electronic collection bag with the bag ID "#123". On the other hand, when the close button 262 is operated, the control unit 21 executes a process of closing the payment screen 260 without executing the payment process.

As described above, in this embodiment, the billing details can be displayed on the display unit 25 of the payer terminal 20 in response to a viewing request from the payer.

(Embodiment 3)
In the third embodiment, a configuration will be described in which the server device 30 notifies the bill collector terminal 10 of the payment status in response to a viewing request from the bill collector terminal 10.

Figure 12 is a flowchart explaining the procedure of the process executed by the collector terminal 10 and server device 30 according to the third embodiment. When the control unit 11 of the collector terminal 10 receives a request to view the deposit status via the operation unit 14 (step S301), the control unit 11 transmits the request to view including the collector ID to the server device 30 via the communication unit 23 (step S302).

When the control unit 31 of the server device 30 receives a request to view the deposit status through the communication unit 33 (step S303), it searches the electronic collection envelope database 323 for an electronic collection envelope associated with the collector ID using the collector ID included in the view request as a search key (step S304). At this time, the control unit 31 may check the viewing authority. For example, the control unit 31 can check the viewing authority by performing user authentication using a user ID and password, etc., and determining whether the user identified by the user authentication is the same as the authorized person set in the authority information (viewing authority) of the electronic collection envelope. When a search result is obtained, the control unit 31 returns the search result to the collector terminal 10 through the communication unit 33 (step S305).

The control unit 11 of the bill collector terminal 10 receives the search results returned from the server device 30 via the communication unit 13 (step S306). The control unit 11 generates a display screen showing the deposit status based on the search results of the server device 30, and displays the generated display screen on the display unit 15 (step S307).

Figure 13 is a schematic diagram showing an example of a payment status confirmation screen. The payment status confirmation screen shown in Figure 13 displays the payment status of each payer in a list. The total collected amount may be calculated in the collector terminal 10 or the server device 30, and the calculation result may also be displayed. In addition, the payment status for each collection item may be displayed in a list.

As described above, in this embodiment, the deposit status can be displayed on the display unit 15 of the bill collector terminal 10 in response to a viewing request from the bill collector.

The embodiments disclosed herein are to be considered in all respects as illustrative and not restrictive. The scope of the present invention is indicated by the claims, not by the above meaning, and is intended to include all modifications within the meaning and scope of the claims.

REFERENCE SIGNS LIST 10 collector terminal 20 payer terminal 30 server device 11, 21, 31 control unit 12, 22, 32 storage unit 13, 23, 33 communication unit 14, 24, 34 operation unit 15, 25, 35 display unit 320 collection processing program 321 collector table 322 payer table 323 electronic collection envelope database

Claims (7)

An electronic collection envelope system that generates an electronic collection envelope on a server device accessible from a collector terminal and a collection target terminal, and performs collection processing using the electronic collection envelope by accepting deposit processing and withdrawal processing for the generated electronic collection envelope,
The server device includes:
For each collection transaction, an electronic collection envelope is generated that includes collection information including information on the collection target, the collection amount, and the collection date, as well as processing information indicating the processing status of the collection transaction, and is identified by an identifier;
When the electronic collection envelope is generated, information regarding the amount of money collected by the electronic collection envelope and the collection date is notified to the collection target terminal;
When a deposit into the electronic money bag or a withdrawal from the electronic money bag is accepted, the processing information is updated;
The electronic bill collection system notifies the bill collector terminal of the updated processing information. The server device includes:
The electronic collection envelope system according to claim 1 , further comprising: a storage unit that stores a processing history of one or more electronic collection envelopes generated for said collection target in association with an identifier of said collection target. The server device includes:
The electronic collection envelope system according to claim 1 or 2, wherein deposits into the electronic collection envelope are accepted up to the collection due date, and a settlement process is executed on the collection due date. The server device includes:
The electronic money collection envelope system according to claim 1 or 2, wherein, when a deposit is received into the electronic money collection envelope, a settlement process is executed without waiting for the collection date. The said collection target terminal is
Transmitting a request to view the electronic money-collection envelope generated by the server device;
receiving a search result including information on unpaid electronic collection envelopes from the server device in response to the viewing request;
Based on the information on the unpaid electronic collection envelopes included in the received search results, a display screen is displayed on which a payment button is arranged for each unpaid electronic collection envelope;
5. The electronic money collection bag system according to claim 1, further comprising: a payment button for executing a payment to the electronic money collection bag selected by the payment button. The bill collector terminal is
Transmitting a request to view the electronic money-collection envelope generated by the server device;
receiving a search result including a processing status of each electronic collection envelope of each collection target from the server device in response to the viewing request;
6. The electronic collection envelope system according to claim 1, further comprising: displaying a list of processing statuses for each electronic collection envelope of each collection target based on the received search results. A bill collection processing device capable of communicating with a bill collector terminal and a bill collection target terminal, and performing bill collection processing using an electronic bill collection bag,
For each collection transaction, an electronic collection envelope is generated that includes collection information including information on the collection target, the collection amount, and the collection date, as well as processing information indicating the processing status of the collection transaction, and is identified by an identifier;
When the electronic collection envelope is generated, information regarding the amount of money collected by the electronic collection envelope and the collection date is notified to the collection target terminal;
When a deposit into the electronic money bag or a withdrawal from the electronic money bag is accepted, the processing information is updated;
The bill collection processing device notifies the bill collector terminal of the updated processing information.

Images