Relocation management and reporting system4700297Abstract A relocation management and reporting data processing system processes reimbursement requests for employees who have been transferred. The system includes a data base for storing and retrieving information characterizing, inter alia, the transferred employee, the types of expenses which will be reimbursed, the limits of reimbursement for each expense and/or employee category, the amount spent to date in each category and mortgage data relating to the transferred employee's old and new dwellings. Set up, data entry and reporting proceeds through a series of nested menus which may be individually and directly addressed. Upon entry of a request for reimbursement, the data and expense category are verified and the expense category limit and the amount spent to date are retrieved and processed to authorize or reject the underlying reimbursement request. The system also permits an allowance to be calculated for the reimbursement of increased mortgage interest paid on the new dwelling. The allowance is calculated in accordance with predefined reimbursement policies entered into the data base. Claims What is claimed is: Description BACKGROUND AND SUMMARY OF THE INVENTION
______________________________________
Variable Functional Description
______________________________________
NM, MN Transferred employee name
(NM) and move number (MN).
M# Move number which is a
unique transaction num-
ber for the system. The
unique move number is in-
ternally assigned by the
system by keeping track
of the previous move num-
ber assigned and incre-
menting that value by
one. A new move number
characterizes each move
for each employee. Each
unique set of NM and MN
gives rise to a distinct
M#.
JL Job level. Typically,
more generous reimburse-
ment benefits obtain
for more senior employ-
ment positions.
JL(M#) A singly indexed scale
variable identifying the
employee's job level for
the move transaction M#.
TL(M#) A temporary living
expense for the move
transaction M#. Here-
after, each variable in-
dexed by move number (M#)
will not be specifically
identified, such being
understood.
STD(TL,M#) The amount spent to date
for temporary living for
move number M#. This is
the form of a doubly in-
dexed variable.
LTD(TL,JL) A storage variable char-
acterizing the limit or
maximum which the plant
operator will reimburse
for temporary living for
an employee holding a job
level corresponding to
the contents of JL.
HL(M#) House locating expenses.
STD(HL,M#) The amount spent to date
for move M# on housing
locating expenses.
LTD(HL,JL) The maximum policy bound
for house locating ex-
penses for job level JL.
HS(M#) Home sale expenses.
STD(HS,M#) The amount spent to date
for home sale expenses
for move M#.
LTD(HS,JL) The home sale expense
bound.
TR(M#) Transportation expenses
attendant a move.
STD(TR,M#) The running accumulation
of transportation ex-
penses for a subject
move.
LTD(TR,JL) The maximum bound for
transportation expenses.
AMT The amount of a reim-
bursement request.
.phi.MRi(M#), .phi.MAi(M#)
The rate and amount
of the i-th mortgage
on an old home being
sold.
NMRj(M#),NMAj(M#)
The mortgage rate and
amount of the j-th
mortgage on a new home
being purchased.
DR The system proprietors
threshold differential
mortgage rate which the
moving employee will be
forced to absorb before
reimbursement.
DA The differential mortgage
amount between new and
old mortgages which the
transferee will absorb
before mortgage differ-
ential payment by the
employer.
PCT The percentage of differ-
ential interest expense
which will be reimbursed.
______________________________________
To facilitate system set up, entry of information into the data base and processing of relocation expenses, it is desirable to provide relatively simple data entry which may be performed by an unskilled operator without the need for substantial supervision. This simplified operation is effected by a series of nested, hierarchal menus corresponding to the specific data to be entered. Computer system operation utilizing a nested hierarchy of functional menus (enumerations of alternative functional tasks to be performed) is per se well known to those skilled in the art and will not be considered further. To speed data entry and processing, the data processing system of the instant invention permits the operator to transfer directly from any point in any menu to any other point in the same or a different menu without the need to return to and then proceed from the main menu. The data entry arrangement of the present invention thus provides a menu driven but individually addressable scheme for data entry and processing. FIG. 1 illustrates the hierarchical, tree-like menu arrangement of the present data relocation management and reporting system. It should be noted that the arrangement illustrated in the drawings is for illustrative overview purposes, and only a single menu at a time is displayed as via a cathode ray tube screen to the operator. It is further noted that each displayed line of the menus bears an individual address which may be used when it is desired to jump from any other point in data processing directly to that task. Test instructions (e.g., IF, .0.N, and the like) for accomplishing such direct functional branching are per se well known to those skilled in the art. Each address generally comprises a string of two letters arranged mnemonically and a four digit numeric code. Each menu or data entry point is addressed by entering an appropriate keystroke, such as "command" and the address desired (i.e., "RP 0000"). Thereafter the appropriate menu or entry line will be displayed. On the main menu A of FIG. 1 (MM 0000)--the default or start up state of the system, the operator may choose a first option (TM 0000) to enter information (TM 0000) characterizing the employee being transferred. Other options on the main menu provide for entry of data (ED 0000), generation of reports (RP 0000), setup or initialization of the program (SU 0000) for entry of the particular repayment program parameters, and exiting the program upon completion (D 0000). It is noted that no data entry or processing takes place at the main menu level which serves only as a routing point for the beginning of the hierarchal tree structure of nested subordinate menus. For example, upon selection of the transferee information menu K (TM 0000), the main menu will be replaced by the transferee information data entry menu (TM 0000). As Menue K indicates, the operator may then enter any of the respective data called for on the menu. Such information may include the employee's name (NM), the move number (M#), for that employee, i.e., the number of the subject move (if more than one) for the same employee during the monitored interval (each unique NM and MN being assigned a unique M#), and/or any other information that the employer wishes to utilize or retain regarding the move (e.g., old and new addresses, family size, years with the company, or positions held). Each item on transferee menu TM 0000 also bears an address such as TM 0100, TM 0200, TM 0300, . . . , to permit the operator to jump directly to that particular data entry sequence without passing through the main menu (MM 0000) and all other intermediate menus. Turning now to the initial setup or definition of the program (SU 0000), we see in Menus B through F that this setup involves a series of nested progressively subordinate menus for the various functions to be performed. The master setup menu B includes vendor identification (SU 0100 of Menu C), an MIDA ("Mortgage Interest Differential Allowance") calculation definition menu (SU 0200 of Menu E), and an entry of reimbursement policies menu (SU 0300 of Menu D, e.g., entry of expense category limits). The setup menu also includes a program customization option (SU 0400--Menu F) for adding, deleting or changing expense categories for which reimbursement will be paid to accommodate individual preferances of system users. Finally, the setup menu B includes an option for return to the main menu. Menu C of FIG. 1 is the vendor setup menu which is used to add a vendor (selection of SU 0110), delete a vendor (SU 0120), change vendor data (SU 0130), and return to the setup menu (SU 0140), These menus in turn would lead to further menus (not illustrated) for the entry of data with respect to a subject vendor. The provisions for vendor data entry permits payment of moving expenses directly to the provider of such services, such as moving companies or real estate agents, rather than in direct payment via the employee. This assures that the vendor will in fact receive the monies disbursed. Menu E of FIG. 1 is the submenu (SU 0200) for entering MIDA calculation parameters which is discussed in detail below. This submenu provides for the entry of the mortgage cost differential percentage (PCT) which will be paid by the employer; and the threshold differential interest (DR) and principle (DA) which the employee must absorb before reimbursement begins. Menu D of FIG. 1 is a submenu (SU 0300) for establishing reimbursement policy with respect to the types and maximum amounts (by expense category) of reimbursement to be paid to the transferee. In this submenu, the types and categories for which payment will be made and the limit amounts for each category, are entered and thus defined to accomomdate individual user preferances. As noted previously, the allowance for each of the categories of expenses that will be reimbursed may vary with the job level (JL(M#)) of the transferee. Accordingly, all of the maximum reimbursement values (LMT) are entered as doubly indexed program variables dependent upon expense type and job level (JL). The operator thus enters via the menu SU 0300 the dollar amounts of the maximum allowance for each expense category for each job level. The standard categories are maximum reimbursable transportation allowance (LMT(TR,JL)); temporary living expense allowance (LMT(TL,JL)); home sale expense allowance (LMT(HS,JL)), and new home locating allowance (LMT(HL,JL)). After limit data entry, an illustrative array of expense limits would be:
______________________________________
Job Level
(JL)
1 2 3
______________________________________
LMT(TR,JL) $1000 $1500 $2000
LMT(TL,JL) 2000 3000 4000
LMT(HS,JL) 1500 2500 3500
LMT(HL,JL) 750 1500 3000
______________________________________
If other types of expenses are to be added to (or to replace) the list of reimbursed expenses assumed above, this may be accomplished via the customization menu (SU 0400) shown in Menu F which provides for additions (SU 0410), deletions (SU 0420) or changes (SU 0430) of particular expense categories. Frequently, it is desired that that transferee be reimbursed, at least partially, for the interest rate differential between the mortgage(s) on a former dwelling and the mortage(s) on a new dwelling at the transferred situs. Due to the recent increases in mortgage rates it is likely that the interest rate(s) on the new dwelling will be higher than those of the old home thus increasing the transferee's basic cost of living with no increase in benefit. The recent introduction of "adjustable rate" mortgages serves to further complicate the calculation of appropriate mortgage reimbursement. Accordingly, it is desirable to provide a cash allowance to the transferee for an increase in interest rates between the old and new dwelling. However, where the transferee purchases a new dwelling which is more expensive than the old dwelling, the employer may or may not desire to reimburse the employee for resultant increased mortgage costs. Furthermore, the organization may require that the employee pay a certain portion of the differential interest expenses; or to abosrb threshold amounts of the increase in interest rates or equity amounts. The mortgage interest differential allowance (MIDA) aspect of the instant program provides a generalized formula for calculating a monthly allowance to be paid the transferee, taking into account the possibility of multiple mortgages on the older and newer dwellings, and as well as the considerations set forth in the preceding paragraph. The constants of the formula (DR, DA, PCT) are defined by the user via SU 0200 processing. The MIDA calculation may be effected as follows: ##EQU1## In calculating the MIDA formula, first the present effective interest rate on the new dwelling is calculated by summing the amounts and rates of the N-mortgages on the new dwelling [NMA1*NMR1)+(NMA2*NMR2)+ . . . +(NMAN*NMRN)] and dividing by the sum of the principle amounts (.SIGMA.NMA1, . . . , NMAN) to provide a weighted average of the present effective interest rate. Similarly, the weighted average of the rate on the previous home is calculated by adding the amounts and rates of the M-older dwelling mortgage(s) [(.0.MA1*.0.MR1)+(.0.MA2*.0.MR2)+ . . . +(.0.MAM*.0.MRM)] and dividing by the sum of the amounts (.SIGMA..0.MA1, . . . , .0.MAM). The effective interest rate for the older dwelling is then subtracted from the effective interest rate of the newer dwelling which provides the effective interest rate differential between the old and new mortgages. Subtracted from this differential is the variable DR (if non-zero) which is the value determined by the system user organization to be the rate differential threshold that the transferred employee must absorb. For example, the organization may desire to pay the transfer only if the difference in interest rates is greater than 2%. Thus, in this example, DR (previously entered via SU 0200 data entry) would equal 2%. Some employers will fully reimburse the transferee for the interest rate differential and thus DR in such event equals zero. After the interest rate differential is calculated, the sum of the amounts of the old mortgages is calculated (.SIGMA..0.MA1, . . . , .0.MAM). The employer may again wish to reimburse for a mortgage amount differential only over a certain predetermined threshold amount. In this event, the threshold amount (contents of program variable DA) is subtracted from the sum of the old mortgages. Again, this DA amount may equal zero if that is the user's policy. Thereafter, the rate calculation is multipled by the mortgage amount calculation, which provides a dollar amount of the reimbursable monthly differential interest payment. The dollar amount is multiplied by the interest percentage (PCT) which the employer will pay and this represents the Mortgage Differential Interest Allowance (MIDA) to be paid to the transferee. This percentage may be any percentage up to 100%. The result of the MIDA formula is a monthly allowance figure which the employee will receive for increaesd mortgage cost. It should be noted that the amount on which the allowance is based is calculated on the amount of the old mortgage (.SIGMA..0.MA1, . . . , .0.MAM), not the new mortgage. This means that any increased equity value on the new dwelling will be paid for by the transferee. In certain instances, the employer may desire to reimburse for the increased equity value in which case the new amount (.SIGMA.NMA1, . . . , NMAN) would be used rather than the old amount. A predetermined weighted or unweighted average of the old and new mortgage amounts may also be used. The data processing for applying the MIDA formulas proceeds as follows. The DR, DA and PCT variables, set by company policy, are entered in the Define MIDA Calculation menu E (SU 0200) which is accessed from the Set Up menu B of FIG. 1. In processing a request for an MIDA payment, the MIDA expense data entry menu ED 0100 (Menu H) is accessed from the Enter Data menu Ed 0000 (Menu J). MIDA entry menu ED 0100 (Menu H) permits the operator to enter the variables .0.MA1, .0.MA2, . . . , .0.MAM; .0.MR1, .0.MR2, . . . , .0.MRM; NMA1, NMA2, . . . , NMAN; NMR1, NMR2, . . . , NMRN, which are used in the MIDA calculation described above. After the variables have been entered the operative MIDA formula is run. The result is the monthly allowance to be paid the transferee. The data processing may then authorize the issue of payment to the transferee. A cumulative total of the MIDA payments made is stored for reporting purposes and limit evaluation. It is noted that in many instances the old and new mortgage rates and amounts may not vary from month to month and accordingly to facilitate data entry the previous mortgage data entered via MIDA entry menu ED 0100 may be stored in the data base and utilized as default values when accessing MIDA data entry menu ED 0100. FIG. 2 illustrates a schematic form a flow chart of representative data processing upon receipt of a request for payment for any expenses for entry and processing. Proceeding from the start at block 102, the operator enters data (functional block 104) through the series of data entry menus described previously. The data entry includes the name of the employee (MN), the move number (MN), the expense category (TL, HL, HS, TR, . . . ) and the amount of the expense (AMT). At block 106, the data entered at block 104 is verified to assure that the employee name, move number, and expense category are valid. If the data is not valid, the operator is returned to the start block 102 for entry of valid data. Assuming that the entered data is valid, the processing proceeds to block 108 which retrieves the operative expense limit (LMT(.sub.--,JL)) for the expense category and the cumulative category amount spend to date for the move (STD(.sub.--,M#) from the data base. The cumulative amount (STD) is then updated for the current AMT expense, as by STD(.sub.--,M#)=STD(.sub.--,M#)+AMT. The updated cumulative sum (STD) is next compared with the limit variable (LMT(.sub.--,JL)) at block 112. If at block 112, the limit (LMT) is not exceeded [STD(.sub.--,M#).ltoreq.LMT(.sub.--,JL)], a payment authorization message is generated (block 116). Processing flow then returns to start 102 for entry of further data. If the limit (LMT) is exceeded [STD(.sub.--,M#)>LMT(.sub.--,JL)], a message is supplied to the operator (block 118) informing the operator that the expense limit has been exceeded. The message will contain an inquiry as to whether the operator desires to override the limit in this particular instance. If at block 120 an override message is not received as via the system manual entry device (e.g., keyboard), a final rejection message is generated (including hardcopy if required) indicating that the amount spent to date plug the present amount exceeds the preset limit. The processing flow in either event returns to the start point 102 for further data entry. As desired, the employer (system user) may obtain reports of varying content on employee move expenses via Reports Menu (RP 0000) illustrated in FIG. 10 which is accessed from the Main Menu (MM 0000). Reports Menu J (RP 0000) may provide summaries of all expenditures (RP 0100), expenses per transferee move (RP 0200 which searches on M#-indexed variables); expenses per category (RP 0300 which searches on STD(.sub.--)); and so forth. The subject employee relocation supervising and accounting system has thus been shown to flexibly accommodate particular requirements of each system user operative from a common underlying program. The arrangement accepts and enters user criteria; and enters data characterizing transferred employees, vendors, and specific expense experiences. Running subtotals of expense categories are maintained on a per-move basis, and compared against operative limits to generate expense acceptance and reimbursement events. Moreover, it is observed that the program operates flexibly, permitting program jumps or transfer from any pont of operation to any other point of operation without proceeding upward through the hierarchy of menus to the main menu A (MM 0000), and then downward through the sub-menus. As just one example among many, an operator may, for example, be entering MIDA definitional information having selected menu point SU 0220 operation Menu E. When complete, he may proceed directly to any other point in FIG. 1. Thus, he may proceed directly from SU 0220 operation to the command point ED 0230 to enter a home sale expense without proceeding through the intervening menu points SU 0200, SU 0000, MM 0000 points if return or default keys are actuated--further proceeding through ED 0000, and ED 0200 to the desired point ED 0230. Similarly, direct transfer can occur from any point in any subordinate or main menu of FIG. 1 to any other functional point and shown directly without proceeding up or down any hierarchal menu tree. The above described arrangement is merely illustrative of the principles of the present invention. Numerous modifications and adaptations thereof will be readily apparent to those skilled in the art without departing from the spirit and scope of the present invention.
|
Same subclass Same class Consider this |
||||||||||
