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

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a recipient management method and system in a welfare service implemented by a local government or the like, and more particularly, to a method and system for managing a ledger and a payment amount related to a money supply service.
[0002]
[Prior art]
Conventional services in the municipal welfare sector include services for elderly people, persons with disabilities, children, and those who require welfare protection, which provide services by hand, those related to entrance to facilities, and allowances. It is broadly classified into those related to the supply of tools and tools and those that manage the qualification of the person, such as a handbook for the disabled. Of these, in particular, with regard to the payment-related services, which are the operations of the payment of money, the uniqueness of each service is strong due to the fact that the conditions for receiving the income tax of the target person differ from service to service, and the municipalities can set up their own services. A large amount of money was required because it was necessary to develop a dedicated program for each of the corresponding services for the introduction of the system. In addition, after the development of these systems, as the laws and regulations of municipalities are revised, program modification work is required for each service, so maintenance costs are likely to be significant. .
[0003]
A system that allows users to arbitrarily set service names and ledger items and share the same operation screens and tables to manage the payee ledger in order to reduce development costs and maintenance costs for various services. Although it has been developed, the functions of such a system are limited to the ledger management, and it is a system that can handle a series of office operations up to the calculation of payment amount and creation of expenditure amount information, which is a feature of the supply system service Is not yet.
[0004]
[Problems to be solved by the invention]
An object of the present invention is to provide a recipient management method capable of dealing with various services, and also includes a calculation of payment amount and creation of expenditure amount information, and a general-purpose that can manage information from application information to payment service information. Is to provide an effective recipient management method and system.
[0005]
[Means for Solving the Problems]
The present invention relates to a recipient information storage means for storing information about each recipient who receives each welfare service, and a service management item for storing item names of data items included in the recipient information storage means for each welfare service. A method for managing each recipient with respect to a system having a storage means, and when a service type is designated, an item name corresponding to the designated service is obtained and displayed by referring to the service management item storage means. The data input corresponding to the displayed item name is stored in the receiver information storage means together with the identifier of each receiver, and the information input about the household member of the receiver corresponds to the service type and the receiver identifier. And the payment amount calculated for the recipient is stored in the payment amount storage means corresponding to the service type and the recipient identifier. And wherein the user management method. It also features a system that operates according to this method.
[0006]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
[0007]
FIG. 1 is a diagram showing a flow of office work when an information system is used in a supply service executed in a local government. When managing a supply service, a service registration process is performed as an initial setting before starting normal business operation (step 10). In the service registration, 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 income tax calculation, and the like. The usual paperwork service processing is implemented in the processing after the application acceptance (step 11) processing. In the local government, after receiving the service receipt application from the residents, the registration of the recipient qualification information such as the application information and the payment determination information is registered in the ledger that manages the recipient qualification information by the process of registration of the recipient qualification information (step 12). The registration of the receipt qualification information will be described in detail with reference to FIG.
[0008]
For data that has been registered in the process of registering the recipient qualification information, the process of registering the expenditure (transfer) information (step 13) is performed at a timing such as monthly. The registration of expenditure (transfer) information is a process of outputting transfer data and the like after creating actual expenditure information based on a payment reference amount for a subject eligible for receipt. The expenditure (transfer) information registration process will be described in detail with reference to FIG.
[0009]
FIG. 2 is a configuration diagram of a system that performs processing according to the present invention. This system includes an input device 21 such as a keyboard and a mouse, an output device 22 such as a CRT display or liquid crystal display, a printer, a recording device 26 such as a floppy disk device or a magnetic cartridge device, a central processing unit (CPU) 25, a communication. A terminal device 1 comprising a control device 27, a control program 24 and an application program (AP) 23, a central processing unit (CPU) 33, a communication control device 28, a storage device 32, a control program 31 and an application program (AP) 29 It has a server 2. The storage device 32 stores resident information such as name, date of birth, address, and gender for each personal reference number, a resident management table 34 that stores personal income and tax information, and qualification information for each service of the recipient. Recipient management table 35, service management item table 36 that stores the ledger item name for each service, reference items for income calculation, etc., recipient household table 37 that stores information on the household members of the recipient, Payment reference amount management table 38 for storing the payment reference amount of money, hierarchical condition table 39 for storing a condition table of the payment reference amount for each income range of the service whose reference amount differs depending on the income tax amount of the household, etc. An account information table 40 for storing information and a spending amount table 41 for storing a determined payment amount are stored.
[0010]
Normally, the terminal device 1 is installed at a window for welfare office work, and the server 2 is installed at a place having a role of a calculation center in a local government or a calculation center in a welfare department, and is connected by a LAN or WAN, respectively.
[0011]
In the case of paperwork for a supply service, after receiving an application from a resident, a registration / update command for information such as application and payment determination, a calculation command for the payment amount, and the like 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 performs data search, registration / update, etc. on various tables 34 to 41 on the storage device 32 as required by the AP 29 that executes specific processing. Process. The processing result is transmitted to the AP 23 of the terminal device 1 to display the screen on the output device 22 and output the transfer data to the floppy disk of the recording device 26.
[0012]
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. There are a plurality of ledger items 52, and the names of data items necessary for managing the recipient ledger of the service are stored. 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 “determination date”. If the service to be registered is a supply service, the supply work flag 53 is set to on (“1”). In addition, as a rule for calculating the amount of payment for each service, a household total flag 54 indicating whether or not the income tax amount is to be added to the household, a livelihood center flag 55 indicating whether or not to make a judgment based on the income of the livelihood center, and a tax in the local government Flags 56, 57, etc. that specify that the applicable item is a tax item to be referred to are stored for items such as the per capita municipal tax per capita amount, income per capita amount, and income tax. At the time of calculation of the basis amount at the time of calculating the base payment amount, the amount of the tax item whose flag is on (“1”) is extracted from the resident management table 34. It is used to calculate the income tax amount for central persons or household members.
[0013]
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 reference 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 date when the supply starts and the date when the supply ends. The ledger information 62 includes 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. .
[0014]
FIG. 5 shows a record format of the recipient household table 37. Each record corresponds to the service code 50 and the personal reference number 59, the household member personal reference number 65 of the household member belonging to the same household as the principal, the relationship code 66 indicating the relationship with the principal, and whether or not the living is the same It also stores household member information 67, which is flag information for setting whether it is a livelihood central person, whether it is a dependent person, whether it is a householder, whether it is a lifeguard. In the welfare service, the person who is a member of the same household as the target person may differ depending on the service, so even if it is a household of the same target person, it can be managed as a separate household for each service on this table .
[0015]
FIG. 6 shows a record format of the supply reference amount management table 38. Each record stores the payment amount 72 and the hierarchy code 73 corresponding to the service code 50 and the personal reference number 59 as reference amount information determined to be paid. Further, the supply start month 70 and end month information 71 are stored. If there is a temporary stop period, the reason and the period are stored as a stop reason 74, a stop period start 75 and a stop period end 76. The information stored in this table can be set as an additional item in the beneficiary management table, but this system is a distributed table considering that there is a high possibility of managing services other than the payment service As a result, the storage area can be saved.
[0016]
FIG. 7 shows a record format of the hierarchy condition table 39. This table shows a hierarchy table that is a relative table of the tax amount range and the payment standard amount when the payment standard amount is different due to income tax etc. for the target person, livelihood center, and all household members of the target person. Store. Corresponding to each service code 50, for each income tax start 79 and income tax end 80, which are the income tax range for extracting the payment reference amount, the hierarchical code 81 and the supply reference amount 82 are stored. In addition, the payment base amount in the case of income tax exemption is stored in a record in which the tax exemption section 78 flag is set to on (“1”).
[0017]
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 person name 87, and an account number 88 of a bank account to which the amount to be paid corresponding to the service code 50 and the personal reference number 59 is transferred. In addition, in the case of subject data without this record, it can also be regarded as a cash benefit subject.
[0018]
FIG. 9 shows a record format of the expenditure table 41. The records stored in this table are created as the amount of money actually spent based on the information stored in the payment reference amount management table 38, as needed, at monthly or once every three months. Is done. Each record is provided for each service code 50 and personal reference number 59. The payment amount 72 that has been set in the payment reference amount management table 38 of the corresponding target person is registered in the payment amount 92 as the determined payment amount for each period.
[0019]
In AP23 and AP29, when the system responsible for financial accounting processing within the local government from the welfare system or the creation processing of the account transfer data to be sent to the outside such as a bank, the execution result is displayed as a notification output flag 93, a paid flag 94, and used as a check flag for preventing processing such as duplicate supply. Further, the section code 95 in charge of supply, the bank code 96, the branch code 97, and the account number 98 are extracted from the account information table 40 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 an example.
[0020]
FIG. 10 is a flowchart showing the processing flow of the AP 23 and AP 29 when registering the receipt qualification information. First, a personal search is performed, and the basic resident 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 name of Kana 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 acquired 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.
[0021]
FIG. 11 is a diagram illustrating 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 notification print button 136, and a return button 137. Have. The basic resident information display frame 130 is an area for displaying basic resident information. As shown in FIG. 12, the basic character information display frame 130 displays a Chinese character name, a resident classification, a personal reference number, a personal residence number, and an address. The service name input field 131 is an area for inputting a service name for which the receipt 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 work flag 53 corresponding to the selected service is turned on.
[0022]
Returning to FIG. 10, when any service name displayed in the service name input field 131 is instructed via the input device 21 (step 111), the recipient ledger information is input (step 112). The AP 23 transmits a service code and a personal reference number corresponding to the instructed service name to the server 2 and requests recipient ledger 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 reference number 59 as keys. If the ledger information 62 is registered, it is acquired. Next, when the acquired ledger item 52 or the ledger information 62 is registered, the AP 29 transmits the ledger information 62 corresponding to the ledger item 52 to the terminal device 1. The AP 23 displays the acquired information in the ledger information display frame 132. Next, the AP 23 accepts input of application information to the data input field of the ledger information display frame 132 via the input device 21. The data entered in the data entry field includes application data specific to each service, such as detailed classification for each service, in addition to common items such as application date and decision date. Data is entered in the data entry field corresponding to each item name displayed.
[0023]
In the operation from acceptance of application for welfare services to payment decision, there may be a waiting time during the survey or submission of documents. The process is completed without inputting the payment decision date stored in the ledger information 62 of the recipient ledger management table 35 as ledger information, except when promptly determining the payment at the time of application information registration. In the case of determining payment, the processing is ended after inputting the date of determination in the ledger information display frame 132. Further, when the supply determination is made for the data that has been processed once, the process is executed again from the personal search process in step 110, and the process ends after inputting the determined date.
[0024]
When the supply is determined, if the execution button 135 is pressed in step 113, the process goes 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 household member information input processing (step 114).
[0025]
FIG. 13 is a diagram illustrating an example of a household registration screen. The household member name 153 and the relationship 154 are the relationship of the household member as seen from the name and the principal of each household member. The same livelihood 155, livelihood center 156, dependency obligation 157 and welfare (life insurance) 158 store the corresponding presence / absence. The check box 152 is instructed when selecting a household member. The add button 159 is a button for instructing addition of a household member. When the add button 159 is pressed, it is possible to add the household information as a result of the personal search by changing to the personal search screen. The delete button 160 is a button for instructing to delete information about the selected household member. The previous page button 162 and the next page button 163 are buttons for displaying the household member information on the previous page and the next page when the number of household members exceeds the display number. The execution button 161 is a button for instructing registration of household member information, and the return button 164 is a button for instructing to return to the ledger registration screen.
[0026]
Returning to FIG. 10, when the household registration button 133 is pressed, the AP 23 requests household member information from the AP 29 with the service code 50, the personal reference number 59, and the personal residence number. The AP 29 searches the beneficiary household table 37 and obtains the corresponding household member information 67 if it exists. Next, the resident management table 34 is searched based on the personal residence number, and information on household members belonging to the same household as the target person is acquired. Next, the acquired household member information is transmitted to the terminal device 1. The AP 23 displays a household registration screen and displays the received household member information. When the input / deletion of household member information is 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 116). ), Display the ledger registration screen, and return to step 112. When the return button 164 is pressed (step 115, return), the ledger registration screen is displayed and the process returns to step 112.
[0027]
When the payment amount calculation button 134 is pressed in step 113, the AP 23 displays a payment amount determination screen if the service is a supply service with the supply operation flag turned on, and calculates a payment reference amount (step 117). )I do.
[0028]
FIG. 14 is a diagram illustrating an example of a payment reference amount determination screen. The payment amount calculation button 172 is a button for instructing to automatically calculate the payment amount based on the hierarchical conditions. The hierarchy 173 is a column for displaying the income tax hierarchy, and the reference monthly amount 174 is a column for displaying the supply monthly basis corresponding to the hierarchy. The account registration button 175 is a button for instructing an account registration process for transferring the payment. The supply period 176 is a column for inputting the start date and end date of the supply period. The stop period 177 is a field for inputting the period when there is a temporary stop period during the supply period, and the stop reason 178 is a field for inputting the reason for the stop. The execution button 179 is a button for instructing registration of set information such as a payment reference amount, and the return button 180 is a button for instructing to return to the ledger registration screen.
[0029]
FIG. 15 is a flowchart showing the processing flow of AP 23 and AP 29 when setting the payment reference amount and the like. The AP 23 reads information inherited from the ledger registration screen as the resident basic information display frame 130 and the service name input field 131 from the memory (step 190), and displays it on the payment reference amount determination screen (step 191).
[0030]
When the payment calculation button 172 is pressed (YES in step 192), the income tax amount is extracted (step 193) and the payment standard amount is automatically calculated (step 194). The AP 23 requests the server 2 to calculate the payment reference amount with the service code 50 and the personal residence number. The AP 29 refers to the household total flag 54 corresponding to the specified service code 50 in the service management item table 36, the livelihood center flag 55, the municipal tax per capita amount 56, the civic tax income per capita 57, etc., and the flag is turned on. Based on the above conditions, information such as income tax amount is extracted based on the designated personal residence number in the resident management table 34, and calculated as the income tax amount of the corresponding household. If this calculation result is 0 yen, the record in which the tax exemption category 78 flag stored in the hierarchical condition table 39 is on, and if it is not 0 yen, the range of income tax amount of income tax start 79 and income tax end 80 The layer code 81 and the supply reference amount 82 of the record corresponding to the amount are extracted and transmitted to the terminal device 1. The AP 23 receives these pieces of information and displays them on the layer 173 and the base monthly amount 174, respectively.
[0031]
When it is necessary to change the automatically calculated supply standard amount for some reason, or when the supply standard amount is directly input without performing the above automatic calculation, the AP 23 inputs (corrects) the supply standard amount ( Step 195) is performed, and direct input of the hierarchy and numerical values to the hierarchy 173 and the base monthly amount 174 is accepted.
[0032]
When the account registration button 175 is pressed (YES in step 196), the AP 23 displays an account registration screen and accepts information input about the transfer account of the payment. For the payment period, input of the start date and end date is accepted in the supply period 176 (step 198). If there is a period of temporary suspension, the period and reason inputs to the suspension period 177 and the reason for suspension 178 are accepted (step 199).
[0033]
Returning to FIG. 10, when the execute button 179 is pressed (step 118, execute), the AP 23 temporarily stores the input data such as the payment reference amount and the account information in the storage device (step 119), and the ledger registration screen. Is displayed and the process returns to step 112. When the return button 180 is pressed (step 118, return), the ledger registration screen is displayed and the process returns to step 112.
[0034]
When the execution button 135 is pressed on the ledger registration screen (step 113, execution), the AP 23 stores the data and account information, such as ledger information, household member information, and supply reference amount, which have been input so far, in the table of the server 2. The AP 29 is requested to register or update the table, and the data received by the AP 29 is registered or updated in the receiver management table 35, the recipient household table 37, the payment reference amount management table 38, and the account information table 40 (step 120).
[0035]
When the notice print button 136 on the ledger registration screen is subsequently pressed, the AP 23 edits the registered data and prints out a notice for the recipient on the output device 22.
[0036]
FIG. 16 is a flowchart of AP23 and AP29 when creating expenditure (transfer) information monthly or periodically for each service after the payment amount is determined. This process is processed asynchronously with the ledger registration, and transitions to a screen for performing this process when the supply process is selected on the business process menu screen. The payment process is divided into an individual unit process and a service unit process. In the case of individual unit processing, the personal search screen is used, and in the case of service unit processing, the screen directly transits to the service selection screen to perform the supply service selection processing (step 210). After making the selection here, the service code of the selected service is taken over, and the screen changes to a supply screen for spending. In the case of individual unit processing, a transition is made to the supply screen (by individual), and in the case of service unit processing, the transition is made to the supply screen (by service).
[0037]
FIG. 17 is a diagram illustrating an example of a supply screen (by individual). The year 232 is a column for inputting the target year of the data to be extracted. The period 234, the payment amount 235, the paid flag 236, and the assigned section 237 are columns 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 supply notice and a supply statement. The FD creation button 241 is a button for instructing to create account transfer data on the FD (floppy disk). The list print 242 is a button for instructing to create an account transfer list. The correction button 233 is a button for instructing correction of the selected row 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 row data covers a plurality of screens. The return button 243 is a button for instructing to interrupt the process and return to the original screen.
[0038]
FIG. 18 is a diagram illustrating an example of a supply screen (service unit). The target date 251 is a column for inputting the target supply date. The confirmation button 252 is a button for instructing to confirm the supply of the selected row data (personal record). The all selection button 259 is a button for instructing to confirm supply for all records. The personal reference number 254, the kanji name 255, the paid amount 256, and the paid flag 257 are columns for inputting data read from the table or data from the input device 21.
[0039]
Returning to FIG. 16, the flow of processing will be described mainly in the case where payment is determined mainly for each service. First, in response to a request from the AP 23, the AP 29 reads the personal reference number 59 and the payment amount 72 of the target year designated for the specific service from the supply reference amount management table 38, transmits them to the terminal device 1, and displays them on the supply screen ( Step 211). However, if the data of the same service code 50, personal reference number 59, and year-by-month 91 are already stored in the expenditure table 41, the payment amount 92 and the paid flag 94 of the corresponding record are read and displayed. Next, the AP 29 reads the account information of the recipient from the account information table 40 or the expenditure table 41 for the read service code 50 and personal reference number 59 and transmits it to the terminal device 1 (step 212). Next, supply section information is read from a correspondence table of service codes and sections in charge (not shown) and displayed on the supply screen (step 213). When necessary data is input or corrected via the supply screen and the confirmation button 252 or the all selection button 259 is pressed for the selected record, a record of the expenditure amount table 41 is created for the record for which the supply has been confirmed. It registers in the expense table 41 or updates an existing record (step 214). At this time, the paid flag is set to 1. In the case of services that are paid in units of three months, the payment amounts for three months are combined into one payment amount.
[0040]
When the notification 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 217). . At this time, the notification output flag 93 of the corresponding record in the expenditure table 41 is set to 1. When the FD creation button 241 is pressed (YES in step 218), account transfer data creation processing is performed (step 219), and the bank transfer data is output to the FD or magnetic tape on the recording device 26. Also, 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). The transfer details and transfer FD created in this way are sent to a bank or municipal finance department, and the actual amount is paid (transferred) to the target person. When the return button 243 is pressed in steps 215, 218, etc., the process is terminated.
[0041]
The above processing is performed for individual recipients even when determining payments for individual units. This is applied when payment data is created or repaid for each individual.
[0042]
【The invention's effect】
As described above, according to the present invention, the management table of the item names of the data items necessary for the recipient management for each service is provided separately from the recipient management table, and the service-specific data according to the item names for each service. Item values are registered in the ledger, and application programs, display screens, tables, etc. are made common regardless of the type of service, such as payment calculation and expenditure management. For this reason, it is possible to cope with various services different for each local government, and it is possible to suppress maintenance costs for programs, display screens and tables associated with addition of new services and revision of the system.
[Brief description of the drawings]
BRIEF DESCRIPTION OF DRAWINGS FIG. 1 is a flowchart showing supply work from application reception of a welfare service according to the present invention to supply determination.
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 36 according to the embodiment.
FIG. 4 is a diagram illustrating a record format of a recipient ledger table 35 according to the embodiment.
FIG. 5 is a diagram illustrating a record format of a recipient household table 37 according to the embodiment.
FIG. 6 is a diagram illustrating a record format of a supply 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 illustrating a record format of an account information table 40 according to the embodiment.
FIG. 9 is a diagram illustrating a record format of an expense table 41 according to the embodiment.
FIG. 10 is a diagram illustrating a flow of processing relating to registration of receipt qualification information according to the embodiment.
FIG. 11 is a diagram illustrating an example of a ledger registration screen.
12 is a diagram showing an example of a basic resident information display frame 130. FIG.
FIG. 13 is a diagram illustrating an example of a household registration screen.
FIG. 14 is a diagram illustrating an example of a payment reference amount determination screen.
FIG. 15 is a flowchart of processing related to a supply reference amount creation process according to the embodiment;
FIG. 16 is a flowchart related to a creation process of expenditure (transfer) information according to the embodiment;
FIG. 17 is an example of an individual payment screen used in the process of creating expenditure (transfer) information according to the embodiment.
FIG. 18 is an example of a supply screen for each service used in the expenditure (transfer) information creation process of 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: Recipient household table, 38: Supply standard Amount management table, 39: Hierarchy condition table, 40: Account information table, 41: Expenditure table

Claims (4)

A resident management table for storing basic resident information for each individual reference number;
Corresponding to the first service code, a service management item table including a service name of the welfare service and a first data item name for managing a recipient ledger of the welfare service;
Corresponding to the second service code, the personal reference number that is the identifier of the recipient of the welfare service indicated by the second service code, and the reception of the welfare service received by the recipient identified by the personal reference number A receiver management method in a system having a receiver management table including a second data item name for managing a person ledger, the system comprising:
In response to an input of a key for searching for an individual, the resident management table is searched, the resident basic information corresponding to the individual of the key is acquired, and the acquired resident basic information is used as a service name of the welfare service. On the screen with the menu of
In response to the selection of the service name from the service name displayed in the menu, the service management item table is searched to obtain the first service code and the first data item name corresponding to the selected service name. And
Based on the acquired first service code, the receiver management table is searched, and when the second service code corresponding to the first service code exists, the second data item name is On the screen,
The receiver management method, wherein the first data item name is displayed on the screen when the second service code corresponding to the first service code does not exist. The service management item table includes a supply operation flag indicating whether or not the welfare service is a supply service corresponding to the first service code, and the system includes:
A payment amount calculation button for displaying a screen for determining a payment amount on the screen when the supply service flag corresponding to the selected service name indicates a supply service when searching the service management item table The receiver management method according to claim 1, wherein: An input device, and a terminal device including an output device having a screen;
A resident management table connected to the terminal device and storing basic resident information for each personal reference number,
A service management item table including a service name of a welfare service and a first data item name for managing a recipient ledger of the welfare service, corresponding to the first service code;
Corresponding to the second service code, the personal reference number that is the identifier of the recipient of the welfare service indicated by the second service code, and the reception of the welfare service received by the recipient identified by the personal reference number A beneficiary management table including a second data item name for managing the person ledger,
In response to receiving a key for searching for an individual input from the input device of the terminal device, the resident management table is searched, the basic information on the resident corresponding to the individual of the key is acquired, and the welfare is acquired. Means for transmitting the resident basic information acquired together with a service name menu of a service to the terminal device for displaying on the screen of the output device;
In response to receiving the service name selected from the service name displayed on the screen of the output device, the service management item table is searched, and the first service code and the first service code corresponding to the selected service name are searched. Acquisition means for acquiring one data item name, and
Based on the acquired first service code, the receiver management table is searched, and when the second service code corresponding to the first service code exists, the second data item name is When the second service code corresponding to the first service code does not exist, the first data item name is transmitted to the terminal device for display on the screen of the output device. A receiver management system comprising a server having transmission means for transmitting to the terminal device for display on a screen. The service management item table includes a supply work flag indicating whether or not the welfare service is a supply service, corresponding to the first service code,
When the acquisition means detects that the supply service flag corresponding to the selected service name indicates a supply service, the transmission means provides a supply for displaying a supply amount determination screen on the output device 4. The recipient management system according to claim 3, wherein display data of the amount calculation button is transmitted.

Images