JP2002245211A - Recipient management method and system in welfare service - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a recipient management method, capable of coping with various welfare services of a municipality and suppressing the program maintenance cost caused by the revision of a regime. SOLUTION: A recipient management table 35 stores information on recipients. A service management item table 36 stores the names of ledger items included in the recipient management table 35. An AP(application program) 29 acquires the item names, corresponding to the services specified by the service management item table 36, transmits them to terminal equipment 1, and stores the data inputted in response to the item names in the recipient management table 35 for the individual recipients. The AP, a display screen, and tables are used in common for the registration of recipient information in the recipient management table 35, the registration of the household member information of recipients in a recipient household table 37, and the registration of supplied amounts in a calculation/supply reference amount management table 38.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method and system for managing a recipient in a welfare service implemented by a local government or the like, and more particularly to a method and system for managing a ledger management and a payment amount related to a money supply service.

[0002]

2. Description of the Related Art Conventional services in the municipal welfare sector include services for the elderly, the disabled, children and those in need of livelihood protection. They are broadly classified into those related to admission, those related to the payment of allowances and tools, and those related to personal qualification management, such as a notebook for the disabled. Of these services, the payment-related services, which are the work of paying money, are particularly unique because the conditions for receiving the income tax of the target person differ for each service and the municipalities can set up their own services. However, since the introduction of the system requires the development of a dedicated program for each of the corresponding services, a large amount of cost was required. In addition, even after these systems were developed, revisions to laws and ordinances of municipalities, etc., required programs to be modified for each service, so maintenance costs were likely to be large. .

For the purpose of suppressing development costs and maintenance costs for various services, a user can arbitrarily set service names and ledger items and share the same operation screen and table to manage the recipient ledger. Although systems that perform these functions have been developed, the functions of such systems are limited to ledger management, and are used for a series of administrative operations, from the calculation of payments to the creation of expenditure information, which is a feature of payment-related services. No system is available yet.

[0004]

SUMMARY OF THE INVENTION An object of the present invention is to provide a method for managing recipients that can respond to various services, calculate payment amounts and prepare expenditure information, and obtain information on payment-related services from application information. An object of the present invention is to provide a general-purpose recipient management method and system capable of managing information up to expenditure information.

[0005]

SUMMARY OF THE INVENTION The present invention provides a recipient information storage means for storing information about each recipient who receives each welfare service, and a data item included in the recipient information storage means for each welfare service. A service management item storage means for storing the item name of each recipient, wherein the service type is specified, and when the service type is specified, the service management item storage means is referred to and the corresponding service is specified. Get and display the item name to be
The data entered corresponding to the displayed item name is stored in the recipient information storage means together with the identifier of each recipient, and the information entered for the household members of the recipient is stored in correspondence with the service type and the recipient identifier. Stored in the recipient household storage means,
The present invention is characterized in that a payee management method of storing a payout calculated for a payee in a payout amount storage means in correspondence with a service type and a payer identifier. Also characterized is a system that operates according to this method.

[0006]

Embodiments of the present invention will be described below in detail with reference to the drawings.

FIG. 1 is a diagram showing the flow of clerical work in the case of using an information system in a supply service provided by a local government. In the case of managing the supply service, a service registration process is performed as an initial setting before starting normal business operation (step 10). The registration of the service is such that the user arbitrarily sets a service name to be managed, an item name managed in the ledger, a tax reference item at the time of calculating the income tax, and the like. The administrative processing of the normal supply system service is performed in the processing after the processing of the application reception (step 11). After receiving the service application from the residents, the local government registers the qualification information of the recipient, such as the application information and the payment decision information, by registering the qualification information of the recipient (step 12). The registration of the receiving qualification information will be described in detail with reference to FIG.

[0008] For data that has been registered in the process of registering recipient qualification information, a process of registering expenditure (transfer) information (step 13) is performed at monthly timing or the like. The registration of the expenditure (transfer) information is a process of creating actual expenditure information based on the payment reference amount for a target person who is eligible to receive the payment, and then outputting the transfer data and the like. The registration processing of the expenditure (transfer) information will be described in detail with reference to FIG.

FIG. 2 is a configuration diagram of a system for performing processing according to the present invention. The system includes an input device 21 such as a keyboard and a mouse, an output device 22 including a CRT display or a liquid crystal display, a printer, and the like.
Recording device 26 such as floppy (registered trademark) disk device and magnetic cartridge device, central processing unit (CPU)
25, a terminal device 1 comprising a communication control device 27, a control program 24 and an application program (AP) 23, a central processing unit (CPU) 33, a communication control device 2
8, a server 2 including a storage device 32, a control program 31, and an application program (AP) 29. The storage device 32 stores basic information such as name, date of birth, address, and gender for each personal identification number, a resident management table 34 for storing personal income and tax information, and qualification information for each service of the recipient. Recipient management table 35, service management item table 36 for storing ledger item names and reference items for income calculation for each service, recipient household table 37 for storing information on household members of recipients, Standard management table 38 for storing the standard payment amount, a hierarchical condition table 39 for storing a standard table for the standard amount of payment for each income range of services having different standard amounts depending on the income tax amount of the household, a transferee account of the recipient An account information table 40 for storing information and an expenditure table 41 for storing a determined payment amount are stored.

Normally, the terminal device 1 is installed at a window for performing welfare affairs, and the server 2 is installed at a place which has a role of a calculation center in a local government or a calculation center in a welfare section, and is connected by a LAN or a WAN, respectively. You.

[0011] In the case of the business operation of the supply service, after receiving an application from a resident, a command for registering / updating information such as an application and a payment decision, and a command for calculating a payment amount are input from the input device 21 of the terminal device 1. . The AP 23 receives the input data and issues a request to the server 2. The server 2 receives the issued request and executes an AP2 that executes a specific process.
9 to 34 to 41 on the storage device 32 as necessary.
It performs processing such as data search, registration, and update for the various tables up to. The processing result is stored in A of the terminal device 1.
The data is transmitted to P23, the screen is displayed on the output device 22, and the transfer data to the floppy disk of the recording device 26 is output.

FIG. 3 shows a record format of the service management item table 36. The service code 50 is a code for identifying the type of service, and a service name 51 is uniquely assigned to this code. Ledger item 52
Stores a plurality of names of data items necessary for managing the recipient register of the service. The name of each ledger item may be different for each service, but the contents include item contents common to all services, such as “application date” and “decided date”. If the service to be registered is a supply service, the supply business flag 53
Is set to ON ("1"). In addition, as a rule for calculating the amount of payment for each service, a household sum flag 54 indicating whether or not the income tax amount should be summed by the household, a livelihood center flag 55 indicating whether or not to make a judgment based on the income of the livelihood leader, For items such as the municipal tax per capita rate, income per capita amount, and income tax, flags 56, 57, etc., which specify that the pertinent item is a tax item to be referred to, are stored. At the time of calculating the base amount at the time of calculating the payment base amount, the amount of the item whose flag is on (“1”) among the tax items is extracted from the resident management table 34, and the individual or the livelihood is used as the extraction base of the payment base amount. It is used to calculate the income tax of the central person or household members.

FIG. 4 shows a record format of the recipient management table 35. The service code 50 is a code for identifying the type of service. The personal identification number 59 is an identifier for identifying an individual registered as a service recipient. The supply start date 60 and the supply end date 61 store the start date and the end date of the supply, respectively.
The ledger information 62 is composed of a plurality of ledger items, and stores the values (numerical data, character data) of each ledger item according to the ledger item 52 set corresponding to the corresponding service code 50 in the service management item table 36. .

FIG. 5 shows the record format of the recipient household table 37. Each record corresponds to the service code 50 and the personal identification number 59, the household member personal identification number 65 of the household member belonging to the same household as the person, the relation code 66 indicating the relation with the person, and whether or not the living is the same. Or household member information 6 which is flag information for setting whether or not the person is a living person, whether or not the person is a dependent, whether or not the head of the household, and whether or not a welfare guardian.
7 is stored. In the welfare service, the members of the same household as the target person may be different depending on the service.
Each service can be managed as a separate household.

FIG. 6 shows a record format of the payment reference amount management table 38. Each record has a service code of 50
The pay amount 72 and the hierarchy code 73 are stored as the reference amount determined to be paid in correspondence with the personal identification number 59. Further, the start month 70 and the end month information 71 of the supply are stored. In addition, if there is a temporary suspension period, the reason and the period are defined as suspension reason 74, suspension period start 75, and suspension period end 76.
Stored as The information stored in this table can be set as an additional item in the recipient management table. However, in the present system, a distributed table is considered in consideration of a high possibility of managing services other than the supply system service. As a result, the storage area can be saved.

FIG. 7 shows a record format of the hierarchical condition table 39. This table is a hierarchical table that is a relative table between the tax amount range and the payment standard amount if the service is provided with a different base amount due to income tax, etc., for the target person, the main livelihood person, and all the household members of the target person. Store. For the income tax start 79 and the income tax end 80, which are the income tax amount ranges for the payment standard amount extraction corresponding to each service code 50,
The respective hierarchy codes 81 and the payment reference amount 82 are stored. In addition, the payment reference amount in the case of tax exemption is stored in a record in which the flag of the tax exemption category 78 is set to ON ("1").

FIG. 8 shows a record format of the account information table 40. Each record stores a bank code 85, a branch code 86, an account name 87, and an account number 88 of a transfer destination for bank transfer of the amount to be paid corresponding to the service code 50 and the personal identification number 59. Further, in the case of the subject data without this record, it is possible to regard the subject data as a cash payment target.

FIG. 9 shows the record format of the expenditure table 41. The record stored in this table is created as data of the amount actually spent based on the information stored in the payment reference amount management table 38, at any time, monthly or once every three months, in accordance with the payment timing. Is done. Each record is provided for each service code 50 and personal identification number 59. Municipal financial period becomes unique by the year and month 91, and the applicable target person's payment base amount management table 3
The payment 72 already set in 8 is registered in the payment 92 as the expenditure determination amount for the period.

In the AP 23 and the AP 29, when a system for performing financial accounting processing in the local government from the welfare system or a process for creating account transfer data to be sent to the outside such as a bank is performed, the execution result is notified to the notification output flag 93, It is stored in the supply completed flag 94 and is used as a check flag for preventing processing such as overlapping supply. The supply section code 95, the bank code 96, the branch code 97, and the account number 98 are extracted from the account information table 40, which is shared and managed in the system, as information at the time of data creation, and stored in this table. . Since the account information is general information, three main table items are described as examples.

FIG. 10 is a flowchart showing the flow of processing of the AP 23 and the AP 29 when registering qualification information. First, a personal search is performed, and the basic residents information is displayed on the output device 22 (step 110). When the AP 23 displays a personal search screen on the output device 22 and inputs a search key such as a kana name and a resident number via the input device 21, the AP 23 issues a personal search request to the AP 29 of the server 2. The AP 29 searches the resident management table 34 based on the received search key, and transmits the obtained resident basic information to the terminal device 1. The AP 23 displays a ledger registration screen on the output device 22 and displays basic resident information on the screen.

FIG. 11 is a diagram showing an example of a ledger registration screen. The ledger registration screen includes a basic resident information display frame 130, a service name input field 131, a ledger information display frame 132, a household registration button 133, a payment calculation button 134, an execution button 135, a notice print button 136, and a return button 137.
Having. The resident basic information display frame 130 is an area for displaying resident basic information. As shown in FIG. 12, the resident basic information display frame 130 displays a kanji name, a resident classification, a personal identification number, a personal resident registry number, and an address. The service name input field 131 is an area for inputting a service name for which qualification information is registered, and displays the service name 51 as a menu. The ledger information display frame 132 displays the name of the ledger item corresponding to the service displayed in the service name input column 131, and displays the data input column and the input data corresponding to the item name.
The payment amount calculation button 134 is displayed only when the payment operation flag 53 corresponding to the selected service is turned on.

Returning to FIG. 10, when any service name displayed in the service name input field 131 is designated via the input device 21 (step 111), input processing of recipient ledger information is performed (step 112). ). AP23,
The service code and the personal identification number corresponding to the designated service name are transmitted to the server 2 to request recipient register information. The AP 29 searches the service management item table 36 to obtain all ledger items 52 corresponding to the specified service code, and then searches the recipient management table 35 using the service code 50 and the personal identification number 59 as keys. If the ledger information 62 is registered, it is acquired. Next, when the acquired ledger item 52 or ledger information 62 is registered, the AP 29 transmits the ledger information 62 corresponding to the ledger item 52 to the terminal device 1. AP23
Displays the acquired information in the ledger information display frame 132.
Next, the AP 23 receives the input of the application information into the data input field of the ledger information display frame 132 via the input device 21. The data entered in the data entry fields are the application date,
In addition to common items such as the date of decision, application-specific application data such as detailed classification for each service is included.
Data is input to the data input fields corresponding to the displayed item names.

In the operation from the reception of an application for a welfare service to the determination of supply, there may be a case where a survey or a waiting time for submitting a document occurs during the operation. Unless the payment is promptly decided upon registration of the application information, the process is completed without inputting the payment determination date stored in the ledger information 62 of the recipient ledger management table 35 as ledger information. When making a payment decision,
After the data of the determined date in the ledger information display frame 132 is input, the processing is terminated. When a payment is determined for data that has been processed once, the process is executed again from the individual search process in step 110, and the process is terminated after the determined date is input.

When the payment is determined, if the execution button 135 is pressed in step 113, the process proceeds to step 120.
When the return button 137 is pressed, the process ends. When the household registration button 133 is pressed, the AP 23 displays a household registration screen and performs input processing of household member information (step 114).

FIG. 13 is a diagram showing an example of a household registration screen. The household member name 153 and the relationship 154 are the name of each household member and the relationship of the household member as seen from the person. Livelihood same 15
5. Livelihood center 156, support obligation 157, and welfare (life insurance) 158 store the corresponding status. Check box 152 is designated when a household member is selected. The add button 159 is a button for instructing addition of a household member. When pressed, the screen transitions to an individual search screen, and it becomes possible to add household information as a result of the individual search. The delete button 160 is a button for instructing to delete information on the selected household member. The previous page button 162 and the next page button 163 are buttons for displaying the previous page and next page of household member information when the number of household members exceeds the number of display cases. The execute button 161 is a button for instructing registration of household member information, and the return button 164 is a button for instructing return to the ledger registration screen.

Referring back to FIG. 10, when the household registration button 133 is pressed, the AP 23 requests the AP 29 for household member information together with the service code 50, the personal identification number 59, and the personal resident registration number. AP 29 is the recipient household table 37
And obtains the corresponding household member information 67, if any. Next, the resident management table 3 based on the personal resident registry number
4 to obtain information on household members belonging to the same household as the target person. Next, the acquired household member information is transmitted to the terminal device 1. The AP 23 displays the household registration screen and displays the received household member information. When the input and deletion of the household member information are accepted via the input device 21 and the execution button 161 is pressed (step 115, execution), the AP 23 temporarily stores the input household member information in the storage device (step 11).
6), a ledger registration screen is displayed, and the process returns to step 112.
When the return button 164 is pressed (step 115, return), a ledger registration screen is displayed, and the process returns to step 112.

In step 113, the payment amount calculation button 134
Is pressed, the AP 23 displays the payment amount determination screen and calculates the payment reference amount (step 117) if the service is a payment-related service with the payment business flag turned on.
I do.

FIG. 14 is a diagram showing an example of a payment reference amount determination screen. The payment amount calculation button 172 is a button for instructing automatic calculation of the payment amount based on the hierarchical condition. The hierarchy 173 is a column for displaying the income tax hierarchy, and the reference monthly amount 174 is a column for displaying the payment reference monthly amount corresponding to the hierarchy. The account registration button 175 is a button for instructing an account registration process to transfer the payment.
The supply period 176 is a column for inputting a start date and an end date of the supply period. The suspension period 177 is a column for inputting a temporary suspension period during the payment period,
The stop reason 178 is a column for inputting the stop reason.
The execute button 179 is a button for instructing registration of information set such as a payment reference amount, and the return button 180 is a button for instructing return to the ledger registration screen.

FIG. 15 is a flowchart showing the flow of processing of the AP 23 and the AP 29 when setting the supply reference amount and the like. The AP 23 reads from the memory the information taken over from the ledger registration screen as the basic resident information display frame 130 and the service name input field 131 (step 190),
It is displayed on the payment reference amount determination screen (step 191).

When the payment amount calculation button 172 is pressed (step 192 YES), the income tax amount is extracted (step 193), and the payment reference amount is automatically calculated (step 194).
I do. The AP 23 requests the server 2 to calculate the payment reference amount along with the service code 50 and the personal resident registration number.
The AP 29 includes a household sum flag 54 corresponding to the designated service code 50 in the service management item table 36,
With reference to the livelihood center flag 55, the municipal tax per capita amount 56, the municipal tax income percentage 57, etc., based on the condition that the flag is on, the designated individual resident registration number in the resident management table 34 Information such as income tax amount is extracted based on the information and calculated as the income tax amount of the corresponding household. If the calculation result is 0 yen, the record in which the flag of the tax exemption category 78 stored in the hierarchical condition table 39 is ON, and if not, the range of the income tax amount of the income tax start 79 and the income tax end 80 is not 0 yen. Within the hierarchy code 8 of the record corresponding to the amount
1 and the payment reference amount 82 are extracted and transmitted to the terminal device 1. A
P23 receives these pieces of information, and respectively,
And the reference monthly amount 174.

When it is necessary to change the automatically calculated payment reference amount for some reason or when the payment reference amount is directly input without performing the above-mentioned automatic calculation, the AP 23 inputs (corrects) the payment reference amount. (Step 195), and the direct input of the hierarchy and the numerical value to the hierarchy 173 and the reference monthly amount 174 is received.

When the account registration button 175 is pressed (step 196 YES), the AP 23 displays an account registration screen and accepts input of information on a transfer account for payment. As for the payment period, input of a start date and an end date is received in the payment period 176 (step 19).
8). If there is a period of temporary suspension, an input of the period and the reason for the suspension period 177 and the reason for suspension 178 is accepted (step 199).

Returning to FIG. 10, when the execution button 179 is pressed (step 118, execution), the AP 23 temporarily stores the input data such as the payment reference amount and account information in the storage device (step 119). Display the ledger registration screen,
Return to step 112. When the return button 180 is pressed (step 118, return), a ledger registration screen is displayed,
Return to step 112.

When the execution button 135 is pressed on the ledger registration screen (step 113, execution), the AP 23 stores the ledger information, household member information, payment reference amount and other data and account information into the server. Requesting the AP 29 to register or update the table in the second table, and register or update the data received by the AP 29 in the recipient management table 35, the recipient household table 37, the payment reference amount management table 38, and the account information table 40. (Step 120).

When the notice print button 136 on the ledger registration screen is subsequently pressed, the AP 23 edits the registered data and prints out the notice for the recipient on the output device 22.

FIG. 16 shows the AP when monthly (periodically) payment (transfer) information is created for each service after the payment amount is determined.
It is a flowchart of 23 and AP29. This processing is
The process is performed asynchronously with the ledger registration, and when the payment process is selected on the menu screen of the business process, the screen transits to a screen for performing the process. The supply processing is divided into processing on an individual basis and processing on a service basis. In the case of processing by individual, via the personal search screen, and in the case of processing by service,
The screen directly transitions to a service selection screen, and a process of selecting a provided service is performed (step 210). After making the selection here, the service code of the selected service is taken over, and the screen transitions to a payment screen for performing expenditure. In the case of processing in individual units, the screen transitions to a supply screen (for each individual), and in the case of processing for each service, the screen transitions to a supply screen (for each service).

FIG. 17 is a diagram showing an example of a supply screen (for each individual). The year 232 is a column for inputting a target year of data to be extracted. The term 234, the payment amount 235, the payment completed flag 236, and the section in charge 237 are fields for inputting data read from the table or data from the input device 21. The notification print button 240 is a button for instructing printing of a payment notice and a payment statement. F
The D creation button 241 is a button for instructing creation of account transfer data on an FD (floppy disk). The list print 242 is a button for giving an instruction to create an account transfer list. The correction button 233 is
A button for instructing correction of the selected line data. The previous page 238 and the next page 239 are buttons for instructing to refer to the screen of the previous page or the next page when the line data covers a plurality of screens. The return button 243 is a button for instructing to interrupt processing and return to the original screen.

FIG. 18 is a diagram showing an example of a supply screen (service unit). The target date 251 is a column for inputting the target supply date. The confirm button 252 is a button for instructing to confirm supply of the selected line data (personal record). The all-selection button 259 is a button for instructing to determine payment for all records. Personal reference number 254, Kanji name 2
55, the payment amount 256, and the payment completed flag 257 are fields for inputting data read from the table or data from the input device 21.

Returning to FIG. 16, the flow of processing will be described below mainly for a case where payment is determined for each service. First, at the request of the AP 23, the AP 29 reads the personal reference number 59 and the payment amount 72 of the target date designated for the specific service from the payment reference amount management table 38, transmits them to the terminal device 1, and displays them on the payment screen ( Step 21
1). However, the same service code 50, personal identification number 5
9 and the data of the year 91 are already in the expenditure table 4
1 if it is stored in the corresponding record 92
And the supplied flag 94 are read and displayed. Then AP
29 reads the recipient's account information from the account information table 40 or the expenditure table 41 for the read service code 50 and personal identification number 59, and reads the terminal device 1
(Step 212). Next, the charge section information is read from the correspondence table between the service code and the charge section (not shown) and displayed on the supply screen (step 21).
3). Necessary data is input or corrected through the payment screen, and the confirm button 252 is selected for the selected record.
Alternatively, when the select all button 259 is pressed, a record of the payment table 41 is created for the record for which payment has been confirmed and registered in the payment table 41, or an existing record is updated (step 214). At this time, the paid flag is set to 1. In the case of a service to be paid in units of three months, the payment amounts for three months are combined into one payment amount.

When the notice print button 240 is pressed (YES in step 215), a payment notice is created and output to the output device 22 (step 216), and a payment statement is created and output to the output device 22 (step 216). Step 217).
At this time, the notification output flag 93 of the corresponding record in the expenditure table 41 is set to 1. FD creation button 241
Is pressed (YES in step 218), a process of creating account transfer data is performed (step 219), and the bank transfer data is output to the FD or magnetic tape on the recording device 26. In addition, an account transfer request form is created and output (step 220). When the list print button 242 is pressed, an account transfer list is created and output based on the processing result (step 221). Transfer details and transfer F created in this way
D is sent to the financial department of the bank or municipality, and the actual amount is paid (transferred) to the target person. Steps 215 and 21
When the return button 243 is pressed in step 8 or the like, the process ends.

The above-mentioned processing is carried out for the individual recipient even when the payment is determined on an individual basis. This is applied when creating payment data for each individual or re-paying.

[0042]

As described above, according to the present invention, the management table of the item names of the data items required for the recipient management for each service is provided separately from the recipient management table, and the item name for each service is provided. In addition to registering service-specific data item values in the ledger, application programs, display screens, tables, and the like are common regardless of the type of service, such as payment calculation and expenditure management. Therefore, it is possible to cope with various services that are different for each local government, and it is possible to suppress the maintenance costs of programs, display screens, and tables accompanying the addition of new services and the revision of the system.

[Brief description of the drawings]

FIG. 1 is a flowchart showing the affairs of supply from the reception of an application for a welfare service to the determination of supply according to the present invention.

FIG. 2 is a system configuration diagram of the embodiment.

FIG. 3 is a diagram illustrating a record format of a service management item table according to the embodiment.

FIG. 4 is a diagram showing a record format of a recipient register table 35 of the embodiment.

FIG. 5 is a diagram showing a record format of a recipient household table 37 of the embodiment.

FIG. 6 is a diagram showing a record format of a payment reference amount management table 38 according to the embodiment.

FIG. 7 is a diagram illustrating a record format of a hierarchical condition table 39 according to the embodiment.

FIG. 8 is a diagram showing a record format of an account information table 40 according to the embodiment.

FIG. 9 is a diagram illustrating a record format of an expenditure amount table 41 according to the embodiment.

FIG. 10 is a diagram showing a flow of processing relating to registration of receiving qualification information of the embodiment.

FIG. 11 is a diagram showing an example of a ledger registration screen.

FIG. 12 is a diagram showing an example of a basic resident information display frame 130.

FIG. 13 is a diagram illustrating an example of a household registration screen.

FIG. 14 is a diagram showing an example of a payment reference amount determination screen.

FIG. 15 is a flowchart of a process relating to a process of creating a supply reference amount according to the embodiment.

FIG. 16 is a flowchart illustrating processing for creating expenditure (transfer) information according to the embodiment.

FIG. 17 is an example of a personalized payment screen used in a process of creating expenditure (transfer) information according to the embodiment.

FIG. 18 is an example of a supply screen for each service used in a process of creating expenditure (transfer) information according to the embodiment.

[Explanation of symbols]

1: terminal device, 2: server, 23: application program, 29: application program, 34:
Resident management table, 35: Recipient management table, 36:
Service management item table, 37: beneficiary household table, 38: payment reference amount management table, 39: hierarchy condition table, 40: account information table, 41: expenditure amount table

Continued on the front page (72) Inventor Hideyuki Kawamura 5-2-1, Omika-cho, Hitachi City, Ibaraki Prefecture Inside the Information Control Systems Division, Hitachi, Ltd. (72) Inventor Fumi Morishita 1-6-1 Shinsuna, Koto-ku, Tokyo No. 27 Hitachi Public Works Division

Claims (5)

[Claims] 1. A receiver information storing means for storing information about each recipient who receives each welfare service, and a service for storing an item name of a data item included in the receiver information storing means for each welfare service. A method of managing each recipient with respect to a system having a management item storage means, wherein when a service type is specified, the item name corresponding to the specified service is referred to by referring to the service management item storage means. Acquired and displayed, the data entered corresponding to the displayed item name is stored in the recipient information storage means together with the identifier of each recipient, and the information entered for the household members of the recipient is classified by service type. Is stored in the recipient household storage means in accordance with the recipient identifier and the payment amount calculated for the recipient is supplied in accordance with the service type and the recipient identifier. Beneficiaries management method characterized by storing in the storage means. 2. An income tax amount of a corresponding household is calculated by referring to a flag indicating the treatment of income tax set on a storage means corresponding to the service type, and the payment amount is calculated based on the calculated income tax. 2. The recipient managing method according to claim 1, wherein the calculating is performed. 3. When further determining the expenditure of the payment amount,
2. The recipient management method according to claim 1, wherein the determined payment amount is stored in an expenditure storage means in correspondence with the service type and the recipient identifier. 4. A recipient management system having a server computer and a terminal device, wherein the server computer stores recipient information storing means for each recipient who receives each welfare service; A service management item storage means for storing an item name of a data item included in the recipient information storage means, a recipient household storage means for storing household member information corresponding to a service type and a recipient identifier, Payment amount information storage means for storing the payment amount corresponding to the type and the recipient identifier; and a welfare service designated by a request from the terminal device, which is inputted in correspondence with the item name of the service management item storage means. Means for storing the received data together with the identifier of each recipient in the recipient information storage means, and the household of the recipient in response to a request from the terminal device. The information entered about the employee is stored in the recipient household storage means,
Means for storing the amount of payment calculated for the recipient in the amount-of-payment information storage means, wherein the terminal device displays the received item name and inputs the item name corresponding to the displayed item name And a means for transmitting the input data to the server computer, and a means for transmitting data input about a household member of the receiver to the server computer. 5. A recipient management method executed by the server computer in a recipient management system having a server computer and a terminal device, wherein the recipient stores information on each recipient who receives each welfare service. A method of managing each recipient by a server computer having user information storage means and a service management item storage means for storing an item name of a data item included in the recipient information storage means for each welfare service,
When a service type is designated by the terminal device,
Obtain the item name corresponding to the specified service with reference to the service management item storage means and transmit it to the terminal device, and input the data corresponding to the item name together with the identifier of each recipient. Received from the terminal device and stored in the recipient information storage means, the information input about the household member of the recipient is received from the terminal device in association with the service type and the recipient identifier to the recipient household storage means A payee management method, comprising storing and storing a payout calculated for a payee in a payout amount storage means in association with a service type and a payee identifier.