JP7583392B2 - Hometown Tax Payment Support System - Google Patents

Description

The present invention relates to a hometown tax payment support system, and is primarily concerned with a hometown tax payment support system that supports local governments.

Donors who make hometown tax donations to a specific local government can usually receive a gift in return for their donation. The gift is usually sent by the gift provider (the gift seller) and delivered directly to the donor.

These shipping costs are not charged to the donor, but to the local government by the provider, so although the local government is neither the sender nor the recipient of the return gift, it needs to manage the shipping costs. However, as mentioned above, since the return gift is sent by the provider, the local government is unable to know the exact shipping costs and often just pays what the provider tells them to.

In addition, with the enactment of the Act amending the Local Tax Act (Act No. 2 of 2019), a designated system for hometown tax donations was created, and local governments must ensure that the return gift ratio is 30% or less and that solicitation expenses are 50% or less (for example, Non-Patent Document 1).

Internet: URL: http://www.soumu.go.jp/main_sosiki/jichi_zeisei/czaisei/czaisei_seido/furusato/file/report20190401_05.pdf

The present invention aims to support local governments in managing the shipping costs for gifts in return for hometown tax donations. It also aims to support the management of collection expenses.

In order to solve the above problem, the present invention includes a database that stores a delivery fee table that links the return gift shipping fee corresponding to the delivery destination of the return gift to the return gift identifier. The system also includes a processor that receives information on the donation amount corresponding to the donation, the return gift identifier, the delivery destination of the return gift, and the identifier of the donation recipient municipality from the reception site system that accepts the hometown tax donation, reads the return gift shipping fee corresponding to the return gift identifier and delivery destination from the delivery fee table, and records the return gift shipping fee in the database for each donation recipient municipality.

In another invention, the database further stores the expense amount (including the shipping cost of the return gift) or the expense rate for the donation amount for calculating the hometown tax donation collection expenses. The processor then calculates the collection expenses for each donation based on the expense amount or expense rate, and records the collection expenses for each donation in the database by linking them to the recipient municipality, the donation amount, and the donation date.

The present invention can assist local governments in managing shipping costs for gifts in return for hometown tax donations. It can also assist in managing collection expenses.

FIG. 1 is a configuration diagram of an entire system including a hometown tax payment support system according to an embodiment of the present invention. FIG. 2 is a structural diagram of a donation management record stored in the database of FIG. FIG. 3 is a structural diagram of a backyard rate table stored in the database of FIG. FIG. 4 is a structural diagram of a reception site rate table stored in the database of FIG. FIG. 5 is a structural diagram of a settlement rate table stored in the database of FIG. FIG. 6 is a structural diagram of a delivery fee table stored in the database of FIG. FIG. 7 is a structural diagram of a return gift value table stored in the database of FIG. FIG. 8 is a structural diagram of a delivery status table stored in the database of FIG. FIG. 9 is a structural diagram of a shipping rate table stored in the database of FIG. FIG. 10 is a configuration diagram showing a modified example of the embodiment of the present invention. FIG. 11 is a structural diagram of a personal information record stored in the database of FIG. FIG. 12 is a structural diagram of an item name record stored in the database of FIG.

Below, an embodiment of the present invention will be described with reference to the drawings. In FIG. 1, a hometown tax payment support system 10 is communicably connected to external computer devices via a computer network N such as the Internet. The external computer devices include a donor device 20, a reception site system 30, a local government device 40, a return gift provider device 50, and a delivery system 60.

The donor device 20 is a computer device operated by a donor making a hometown tax donation, and is not limited to a device owned by the donor, but may be a device installed on a floor used by an unspecified number of people. The reception site system 30 is a computer system that provides a reception site for accepting hometown tax donations, and includes providing a hometown tax donation portal site and a reception site unique to the local government. The local government device 40 is a computer device operated by the local government. The provider device 50 is a computer device operated by the provider of the return gift. The deliverer system 60 is a computer system operated by the deliverer.

Each of computers 20, 30, 40, 50, 60 has a processor, a storage device, an input device, an output device, and a communication device as the basic elements of a computer. The processor realizes the functions of each computer by executing a program. Information used by the processor for processing is read from the storage device. Information processed by the processor is stored in the storage device. The input device obtains information required for the processor's processing from an external source. The output device outputs information processed by the processor in a manner that appeals to the human five senses, such as sight. The communication device sends and receives information to and from an external computer via the computer network N. In the following explanation, descriptions of the basic operations of these computers may be omitted.

The hometown tax donation support system 10 is also a computer system, and is equipped with the basic elements of a computer, namely a processor, a storage device, an input device, an output device, and a communication device. The operation of each element is similar to that described above. In this embodiment, the hometown tax donation support system 10 is equipped with an expense management function and a shipping management function. The expense management function is a function that manages the status of hometown tax donation solicitation expenses in the local government. The shipping management function is a function that manages the shipping status of return gifts, and is also capable of disclosing the shipping status to the reception site system 30.

The storage device of the hometown tax payment support system 10 stores a database 11 of information necessary to execute each of the above functions. In this embodiment, the database 11 stores a donation management record, a backyard rate table, a reception site rate table, a payment rate table, a delivery fee table, a return gift value table, and a delivery status table, all of which are shown in Figures 2 to 8. The structure of the database 11 may be any structure that can link and manage the necessary information, and may be selected from hierarchical, network, relational, etc.

The donation management record has the structure shown in Figure 2. That is, for each donation ID, the donation date, local government ID, donation amount, card company ID, payment fee, gift ID, gift value, gift delivery address, gift shipping fee, reception site ID, reception site fee (site fee), back-office fee, other expenses included in collection expenses, total expenses, and delivery ID are linked.

The donation ID is assigned a unique value that does not overlap with other donations for each hometown tax donation. The donation date is the date on which the payment for the hometown tax donation was completed. The local government ID is assigned a unique value that indicates the local government to which the hometown tax donation was made. The donation amount is the amount for which the payment for the hometown tax donation was completed. The card company ID is assigned a unique value that indicates the company (credit card company, etc.) to which the hometown tax donation is paid. The payment fee is the fee paid to the company to which the payment is made when the hometown tax donation is paid. The return gift ID is assigned a unique value that indicates the return gift corresponding to the hometown tax donation. The return gift delivery address is the delivery address (address or part of it) specified by the donor. The return gift price is the amount borne by the local government as the price of the return gift. The return gift shipping fee is the amount borne by the local government as the shipping fee for the return gift. The return gift shipping fee may be included in the return gift price.

The reception site ID is assigned a unique value that indicates the reception site that accepted the hometown tax donation. The site fee is the amount of commission paid by the local government to the reception site for the hometown tax donation. The backyard fee is the commission paid to the company that provides the hometown tax donation support system. Other expenses are amounts not included in the solicitation expenses. The total expenses is the amount of solicitation expenses corresponding to one donation, and is represented by the sum H of B through G in Figure 2 for each donation management record. A unique value is assigned to the delivery ID for each delivery of a return gift.

As shown in Figure 3, the backyard fee table links the local government ID with the backyard fee rate. The backyard fee rate is preset for each local government.

The reception site rate table links reception site IDs with site rates. A site rate is preset for each reception site.

The payment fee table links the card company ID with the payment fee rate. The site rate is preset for each card company.

The shipping fee table links the reward item ID with the shipping fee. A shipping fee is preset for each reward item and delivery address.

The gift price table links the gift ID with the gift price. The price of each gift is preset.

The delivery status table links the delivery ID with delivery status information. The delivery status information indicates the delivery status of the package, such as whether it has been shipped, and is updated according to changes in the delivery status.

In the above, each rate indicates a percentage of the donation amount.

Next, we will explain the expense management function of this embodiment.

When a hometown tax payment application is made from the donor device 20 to the reception site system 30, the reception site system 30 stores in a storage device, each time a donation is received, a donation ID, a donation date, a municipality ID of the municipality to which the donation is made, a donation amount, a card company ID, a return gift ID, a return gift delivery address, and a reception site ID, in association with each other. The reception site system 30 transmits this association information to the hometown tax payment support system 10 at a predetermined timing.
In addition, if the donor device 20 itself has a hometown tax payment application function, when a hometown tax payment application is made, the donor device 20 links the donation ID, donation date, the municipality ID of the municipality to which the donation is made, the donation amount, the card company ID, the return gift ID, the return gift delivery address, and the reception site ID each time a donation is received, and transmits this linking information to the hometown tax payment support system 10.

The hometown tax payment support system 10 receives the above-mentioned linking information and executes the following processes (1) to (8) by a processor. Hereinafter, when the term "processor" is used, it refers to the processor of the hometown tax payment support system 10.

(1) Refer to the back-yard fee rate table to find the back-yard fee rate that corresponds to the local government ID, and multiply the donation amount by the back-yard fee rate to find the back-yard fee.

(2) Refer to the reception site rate table to find the site rate that corresponds to the reception site ID, and multiply the donation amount by the site rate to find the site fee.

(3) Refer to the payment fee table to find the payment fee rate that corresponds to the card company ID, and multiply the donation amount by the payment fee rate to find the payment fee.

(4) Refer to the shipping fee table to determine the shipping fee that corresponds to the gift ID and gift delivery address.

(5) Refer to the gift price table to determine the gift price that corresponds to the gift ID.

(6) Determine the amount of other expenses that fall under recruitment expenses.

(7) Then, add the donation amount, payment processing fee, value of the gift, shipping fee for the gift, site fee, back-office fee and other expenses to determine the total expenses.

(8) A donation management record linking the following is registered in database 11: donation ID, donation date, local government ID, donation amount, card company ID, payment fee, gift ID, gift delivery address, gift value, gift shipping fee, reception site ID, site fee, backyard fee, other expenses, and total expenses.

The processor repeats the above-described processes (1) to (8) for the linking information for each donation received from the reception site system 30.

When a local government official wishes to check the status of solicitation expenses, he or she operates the local government device 40 and logs into the hometown tax payment support system 10. The hometown tax payment system 10 acquires the local government ID of the logged-in local government. Next, when a request to check the status of solicitation expenses is received from the local government device 40, the donation management records to be processed are extracted from the database 11 according to the filtering conditions as follows.

(1) When a narrowing-down condition is not specified, the processor extracts from the database 11 multiple donation management records that have a matching local government ID and whose donation date falls within the current fiscal year.

(2) Narrowing down by specifying a reception site The processor receives the specification of a reception site from the local government device 40. The processor extracts from the database 11 a plurality of donation management records whose local government ID matches, whose reception site ID matches the specified reception site, and whose donation date falls within the current fiscal year.

(3) Narrowing down by specifying a card company The processor receives the specification of the card company from the local government device 40. The processor extracts from the database 11 a plurality of donation management records whose local government ID matches, whose specified card company ID matches, and whose donation date falls within the current fiscal year.

(4) Narrowing down by specifying a return gift The processor receives a specification of a return gift from the local government device 40. The processor extracts from the database 11 a plurality of donation management records whose local government ID matches, whose return gift ID matches the specified return gift, and whose donation date falls within the current fiscal year.

(5) When narrowing down by donation date period The processor receives a designation of the donation date period to be processed from the local government device 40. The processor extracts from the database 11 a plurality of donation management records that have a matching local government ID and whose donation dates fall within the designated period.

(6) When narrowing down by specifying multiple of the above elements The processor receives multiple specifications from the reception site, card company, return gift, or donation date period from the local government device 40. The processor extracts from the database 11 multiple donation management records that match the local government ID, match the IDs of the multiple specified elements, and have donation dates that fall within the current fiscal year or the specified period.

Next, the processor calculates the total donation amount for the multiple extracted donation management records, as well as the total expense amount. Furthermore, the processor calculates the ratio of the total expense amount to the donation amount (expense ratio) by dividing the total expense amount by the total donation amount.

The processor also reads out a preset expense ratio threshold (e.g., 50%) from the storage device and compares it with the expense ratio calculated above. If the expense ratio exceeds the threshold, it transmits notification data indicating that to the requesting municipal device 40. The processor also transmits the calculated expense ratio data to the municipal device 40 regardless of whether the threshold is exceeded. The municipal device 40 outputs the expense ratio status to an output device based on the received expense ratio data and notification data. For example, it is possible to display the expense ratio in a different color depending on whether the expense ratio exceeds the threshold. The threshold may be set in stages, and the expense ratio may be displayed in a different color depending on which stage it is at. For example, when the expense ratio exceeds a first threshold indicating that the expense ratio is approaching 50%, notification data may be generated that indicates the expense ratio, etc., in yellow, and when the expense ratio exceeds a second threshold indicating that the expense ratio has reached 50%, notification data may be generated that indicates the expense ratio, etc., in red.

The expense management function of this embodiment described above allows local governments, who are not the providers of the return gifts, to manage the shipping costs of the return gifts. Furthermore, information on the status of the solicitation expenses for return gifts, including the shipping costs of the return gifts, can be provided to local governments in real time. It is also possible to know the status of solicitation expenses for each site and each return gift, making it easy to review sites and return gifts that have high solicitation expenses, for example.

Here, the return gift shipping fee may be calculated based on the shipping rate (proportion to the donation amount) for each return gift. In this case, the database 11 stores the shipping rate table shown in FIG. 9. The shipping rate table links the return gift ID with the shipping rate. A shipping rate is set in advance for each return gift. The processor refers to the shipping rate table to find the shipping rate corresponding to the return gift ID, and multiplies the donation amount by the shipping rate to find the return gift shipping fee. The configuration is as follows. That is,
A database that stores a shipping rate table that links, for each gift, an identifier of a gift given according to the amount of the hometown tax donation and a shipping rate according to the amount of the gift;
A hometown tax donation support system comprising a processor that receives information on the donation amount corresponding to the donation, an identifier of a return gift, and an identifier of a local government to which the donation is to be made from a reception site system that accepts the hometown tax donation, reads out the shipping rate corresponding to the return gift identifier from the shipping rate table, multiplies the donation amount by the shipping rate to determine a shipping cost for the return gift, and records the shipping cost in a database for each local government to which the donation is to be made.

Next, we will explain the shipping management function of this embodiment.

Normally, the reception site accepts donations from the local government, but is not connected to the gift provider, and does not know whether the gift has actually been shipped, making it difficult for them to answer inquiries from donors about the status of the gift. However, this system is able to disclose the delivery status of gifts to the portal site system that acts as the reception site system, and to the local government's own hometown tax donation site system.

When a reception site wishes to know the delivery status of a return gift for which the company has received an application, the person in charge at the reception site operates a terminal included in the reception site system 30 and logs into the hometown tax payment support system 10. The hometown tax payment support system 10 obtains the reception site ID of the logged-in reception site. Next, when a request for checking the delivery status is received from the terminal along with a designated donation ID, the system reads out from the database 11 the delivery ID of the donation management record that matches the donation ID and the reception site ID. Furthermore, the system obtains current delivery status information corresponding to the read delivery ID from the delivery status table. The processor transmits the obtained delivery status information to the terminal that made the request. The terminal outputs the received delivery status information to a display device or the like.
Furthermore, when a user of a terminal in the hometown tax payment support system 10 wishes to know the delivery status of a return gift, the user operates the terminal and logs into the hometown tax payment support system 10. After authenticating the user, the hometown tax payment support system 10 receives a request from the terminal to check the delivery status, and extracts the delivery status information stored in the database 11 and transmits it to the requesting terminal. The terminal outputs the received delivery status information to a display device or the like.
Here, if the hometown tax payment support system 10 knows the reception site ID of the communication destination and a connection with the communication destination is established, the above login is not required. In addition, the hometown tax payment support system 10 may provide a list of multiple delivery status information corresponding to the reception site ID. In this case, the donation ID does not need to be specified.

This allows the reception site to know the delivery status of the return gifts that it has handled, and can respond to inquiries from donors regarding the delivery of return gifts, for example. On the other hand, since the delivery status of records that do not match the reception site ID cannot be viewed, access to unrelated delivery status information can be restricted.
In addition, users of terminals within the hometown tax payment support system 10 can also check the delivery status of the return gift on a management screen or the like.

Similar to the reception site, delivery status information may be made available to local governments, gift providers, or donors.

[Modification of the above embodiment: Return gift provision management function]
Next, a modified example of the above embodiment will be described with reference to Figures 10 to 12. In Figure 10, a return gift provider device 50 is connected to a computer network N. The return gift provider device 50 is a computer system used by a person who directly provides a return gift to a donor (a return gift provider), and includes a processor, a storage device, an input device, an output device, and a communication device as basic computer elements. The operation of each element is the same as in the above embodiment.

In this embodiment, the hometown tax donation support system 10 has a function for managing the provision of return gifts. The function for managing the provision of return gifts is a function that enables a store or other provider of return gifts to provide the return gifts directly to the donor on-site. A "return gift provider" refers to an entity that provides food, drink, lodging, entertainment, merchandise, etc., directly to the donor on-site as a return gift, such as a restaurant, accommodation facility, entertainment facility, or shop. Return gifts provided on-site are hereinafter referred to as "locally provided items."

The hometown tax payment support system 10 also stores the records shown in Figures 11 and 12 in a storage device in addition to the database of the above embodiment. Figure 11 is a personal information record (information unique to each donation) that links a donation ID with personal information such as the donor's address, name, and email address. Figure 12 is a product name record that links a return gift ID with the name of the return gift.

When a hometown tax donation application is made in which a locally provided product is used as a return gift, the hometown tax donation support system 10 records a donation management record (information unique to each donation) as follows, based on the linking information received from the donor device 20 or the reception site system 30.

When recording the donation ID, the link between the donation ID and the personal information of the donor is recorded in the personal information record of FIG. 11. When recording the return gift ID, the link between the return gift ID and the name of the return gift is recorded in the name record of FIG. 12. The return gift provider ID is recorded in the "return gift delivery address." The return gift shipping fee is recorded as 0 yen. The other configurations are the same as the previously described embodiment.

[Issuance of donation details information] When the hometown tax payment support system 10 accepts a donation from the donor device 20 in which a locally provided item is the return gift, it reads out the donation ID of the donation and part of the information in the donation management record, personal information record, or item name record linked to the donation ID as donation details information and transmits it to the donor device 20. The donor device 20 prints out the donation details information received from the hometown tax payment support system 10 from a pre-installed printing device and allows the donor to obtain it.

Alternatively, when the hometown tax payment support system 10 receives a donation from the donor device 20 or the reception site system 30 in which a locally provided product is provided as a return gift, it reads out the donation ID of the donation and part of the information of the donation management record, personal information record, or product name record linked to the donation ID as donation details information, and transmits it to the donor device 20. The transmission method may be on-demand or email transmission. The email address is read from the personal information record and used. The donor device 20 displays the donation details information received from the hometown tax payment support system 10 on the display device of the donor device 20. The donation details information may include a code such as a two-dimensional code that encrypts the donation details information. In addition, the donor may print out the donation details information displayed on the donor device 20 from a printing device connected to the donor device 20.

[Provider device management screen]
When providing the local item to the donor, the return item provider device 50 transmits a provider ID to the hometown tax payment support system 10. The provider ID may be the login ID of the donor or a unique identifier of the provider device 50. The hometown tax payment support system 10, which receives the provider ID from the provider device 50, reads one or more records in which the same provider ID as the received provider ID is registered as the return item delivery destination from the donation management record, and further reads the personal information of the donor and the name of the return item linked to the read donation ID from the personal information record and the name record. The hometown tax payment support system 10 then forms the read registration information into a list and transmits it to the provider device 50, and displays it on the management screen of the provider device 50. The displayed registration information includes the address, name, etc. of the donor who receives the local item. It may also include information corresponding to a two-dimensional code obtained by encrypting part of the registration information.

[Providing gifts: manual identity verification]
The provider of the local items will provide the local items to the donors after verifying their identity using the following method.
(1) The donor confirms the personal information of the visiting donor either verbally or by checking a printed copy or screen display of the donation details information brought by the donor, and if any of the registration information matches the registration information displayed on the management screen of the donor device 50, the donor confirms that the donor is the actual donor.
(2) The donor checks the personal information of the visiting donor using identification such as a driver's license brought by the donor, and if the registration information matches the registration information displayed on the management screen of the donor device 50, the donor confirms that the donor is the actual donor.

[Providing gifts: identity verification by computer]
In addition, the provider of the local item may provide the local item to the donor after verifying the identity of the visiting donor by the following method.
(3) The donor displays a two-dimensional code or other code on the screen by selecting a link contained in an email or other email containing donation details information displayed on the donor device 20. The donor of the local item operates the donor device 50 to read the code presented by the donor with a scanner. A two-dimensional code or other code displayed on a printed material brought by the donor may also be read with a scanner. The donor device 50 searches for registered information matching the code read with the scanner among the information displayed on the management screen of the donor device 50, and if matching registered information is found, it is determined that the donor is the actual donor.
(4) Alternatively, the donor device 50 inquires of the hometown tax payment support system 10 about registration information that matches the code read by the scanner. The hometown tax payment support system 10, upon receiving the inquiry, searches for matching registration information in the donation management record, personal information record, and item name record, and upon finding matching registration information, notifies the inquiring donor device 50 of the match. Upon receiving this notification of match from the hometown tax payment support system 10, the donor device 50 determines that the donor is the donor himself/herself.

[Providing gifts: Clearing process]
The donor device 50 associates the donation ID with the fact that the local donation has been "provided" for the record with matching registration information, and transmits it to the hometown tax payment support system 10. The hometown tax payment support system 10, which receives this, updates the value of the return gift delivery destination of the donation management record with the matching donation ID to "provided". This prevents the same record from being resent to the donor device 50.
Alternatively, when the hometown tax donation support system 10 receives an inquiry about the above-mentioned registered information from the donor device 50, it may update the value of the return gift delivery destination in the donation management record that has been confirmed to match the registered information to "already provided."

According to the modified example described above, it becomes possible to provide gifts in return for hometown tax donations directly on-site, and it becomes possible for donors to receive their gifts on the same day they make their donation. For example, it becomes possible to make a donation at a restaurant and then immediately eat and drink at the restaurant as a gift in return, to make a donation at a lodging facility and then immediately stay at the lodging facility as a gift in return, to make a donation at an entertainment facility and then immediately use the entertainment facility, or to receive the gift in return directly at a store. There are no shipping costs for the gifts, which also leads to a reduction in the costs of collecting gifts.

Here, the scope of the present invention is the scope of the invention described in the claims, and is not limited to the above-mentioned embodiment.

For example, in the above-mentioned embodiment, the donation application screen (search screen or viewing screen for return gifts) provided by the reception site system 30 to the donor device 20 can be narrowed down to only return gifts from specific cities, wards, towns, and villages. On the other hand, it is also possible to jump to another page (a page where return gifts from other cities, wards, towns, and villages can be viewed) from there using a link such as a banner. However, specific cities, wards, towns, and villages do not usually want their return gifts to be viewed. Therefore, the content of the page on which only return gifts from a specific city, ward, town, or village can be viewed can be configured so that it is not possible to jump to a page where return gifts from other cities, wards, towns, and villages can be viewed.

10 Hometown tax payment support system 11 Database 20 Donor device 30 Reception site system 40 Local government device 50 Return gift provider device 60 Delivery system N Computer network

Claims (8)

A database storing a shipping fee table in which a shipping fee for a gift according to a delivery destination of the gift is linked to a gift identifier;
A hometown tax donation support system comprising a processor that receives information on the donation amount corresponding to the donation, a gift identifier, a gift delivery address, and an identifier of the local government to which the donation is made from a reception site system that accepts the hometown tax donation, reads out the gift delivery fee corresponding to the gift identifier and delivery address from the delivery fee table, and records the gift delivery fee in a database for each local government to which the donation is made. In claim 1,
The database stores the amount of expenses (including the shipping cost of the gift) or the expense rate for the donation amount for calculating the expenses for hometown tax donations,
A hometown tax donation support system in which the processor calculates the solicitation expenses for each donation based on the expense amount or the expense rate, and records the solicitation expenses for each donation in the database by linking them to the recipient local government, the donation amount, and the donation date. In claim 2,
Furthermore, when the processor is requested by a local government device to provide information on solicitation expenses, it reads out from the database multiple donation amounts and solicitation expenses for each donation whose donation date linked to the requesting local government falls within a specified period and adds them up, and if the ratio of solicitation expenses to the total donation amount exceeds a preset threshold, it sends notification information to that effect to the requesting local government device. In claim 3,
The processor records the collection expenses for each donation in the database by linking the collection expenses to the donation reception site that received the donation,
Furthermore, when the processor is requested by the local government device to provide information on solicitation expenses along with the designation of the reception site, it reads out from the database multiple donation amounts and solicitation expenses for each donation that is linked to the requesting local government and the designated reception site and whose donation date is within a specified period, and adds them up, and if the ratio of solicitation expenses to the total donation amount exceeds a preset threshold, it sends notification information to that effect to the requesting local government device. In claim 3,
The processor links the solicitation expenses for each donation to a return gift corresponding to the donation and records the same in the database;
Furthermore, when the processor is requested by the local government device to provide information on solicitation expenses along with the designation of a return gift, it reads out from the database multiple donation amounts and solicitation expenses for each donation that is linked to the requesting local government and the designated return gift and whose donation date is within a specified period, and adds them up; if the ratio of solicitation expenses to the total donation amount exceeds a preset threshold, it sends notification information to that effect to the requesting local government device. In claim 3,
The processor links the collection expenses for each donation to the card company to which the donation is settled and records the collection expenses in the database;
Furthermore, when the processor is requested by the local government device to provide information on solicitation expenses along with the designation of a card company, it reads out from the database multiple donation amounts and solicitation expenses for each donation that is linked to the requesting local government and the designated card company and whose donation date is within a specified period, and adds them up, and if the ratio of solicitation expenses to the total donation amount exceeds a preset threshold, it sends notification information to that effect to the requesting local government device. In claim 3,
The processor records the fundraising expenses for each donation in the database in association with the donation date;
Furthermore, when the processor is requested by the local government device to provide information on solicitation expenses along with a specified period, it reads out from the database multiple donation amounts and solicitation expenses for each donation linked to the requesting local government and the donation date within the specified period, and adds them up; if the ratio of solicitation expenses to the total donation amount exceeds a preset threshold, it sends notification information to that effect to the requesting local government device. In claim 3,
The database stores current delivery status information regarding the delivery of gifts in response to donations received by the reception site, in association with the reception site;
In this hometown tax payment support system, when a request for delivery status information is made by a reception site system, the processor reads out delivery status information linked to the requesting reception site from the database and transmits it to the requesting reception site system.

Images