Several changes in this area relate to client-specific processes that are not included in this summary. Approximately half of the changes in AR for this HFS release are minor fixes to the software. The remainders of the changes are enhancements to the product. Listed below are many of the changes that are part of this HFS release:

Added additional HELP information to six questions in the AR report menu to better explain the proper use or possible uses of the question

Greatly improved the speed of the AR transaction conversion utility and added progress display messages and additional run time option to begin processing at a particular record within the file.

Removed 'CB' (Convert Batch) from the AR SP MB menu. When a batch file is opened, it will automatically be converted if necessary. Also fixed problem with converting AR/CR batch files prior to HFS 9902.

Corrected the situation where GL transactions had the incorrect reference if the POSTREF Common Code was not being used.

Added new directives to the ARICDVR (Interactive Cash Receipts driver) file to not allow the receipt number, Batch ID, and/or receipt date to be modified from their default values. This can be accomplished by adding any or all of the following lines to the ARICDVR file: >RECEIPT-LOCK >Y

>CR-DATE-LOCK >Y

>BATCH-ID-LOCK

>Y

There were situations when the credit card authorization field was clearing itself. This has been corrected.

Increased the course number field from 10 to 12 characters for SRN interactive billing, since SRN had already made the same change in their software.

In AR standard and ad hoc reports, changed the as-of-date, bill date, and bill due date to default to the current date instead of defaulting to "12/31/1999".

Corrected the 'Job Card' in Nucleus Job Dialog/Running Mgmt for the Accounts Receivable Standard Transaction report (AR RE SR TR).

The AP to AR interface (AR SP AP) was always using the 'Hierarchy Method' to determine how to build the Reference in AR, regardless of which method was chosen. This has been fixed.

The utility to selectively change the Billing and/or Due date (AR UT CS) has been corrected so that dates entered with a century are formatted and used correctly in the utility program.

For our MPE clients, the Reference Link Detail data sets have been added to the SYDBSIZE file, and CATSET has been modified in FKDRIVER to prevent DBIO errors when verifying the AR FASTKEY file.

A new utility has been created to correct various problems that can arise from

3rd party billing associations.

The Accounts Payable database (OHDB) was modified to facilitate the new Netsight screens (see details in database changes section). This change should be transparent to sites using batch file AP data entry. This change included expanding the size of the AP batch file (which is also used for SI and EN batches) to accommodate larger batch IDs and preparer IDs. Custom interfaces not supported by Bi-Tech may require changes to support this new file format.

PO security code checking has been added to AP when paying against a PO. In order for a user to be allowed to pay against a PO, that user must have at least read access to the security code entered on the PO. Note: this change will only effect users who have user records defined in POUPUS. If a user is not configured in POUPUS, the system will assume they have read access to all security codes.

A "global batch change" utility has been added as mask APOHUTGC. This new utility will allow the user to place a value into a field for all records within a batch file. For example, you can change all invoice dates within a batch to be "3/1/2000". This utility operates in the same way as the AR "global change" utility.

The majority of changes in the CK subsystem are new or modified client-specific interfaces.

An option has been added to the check update program to use the posting date as the check's reversal date. This can ease CK to GL reconciliation. See Common Code CKFG CK200C, Associated Code (3) for details.

A year-2000 defect was corrected in the CKUTSD utility. The calculation of the "as-of" date was changed to use the standard date manipulation routines. See the Technical Bulletin for more information.

ENREENTA can now display FQA (Fully Qualified Account) numbers on a second line if so desired.

The speed of ENUTPU and ENUTUN was increased.

A problem was corrected with invalid units on batches created by ENUTUN.

Attempts to post invalid data to EN are now blocked and error messages returned. A stand-alone program was released that sets blank JL ledger codes and Keys to appropriate defaults.

NOTE: This will disallow paying POs before they are encumbered. Adjust workflow to accommodate encumbering before paying.

SMARTDB FA no longer posts to GL if no posting code is defined.

Budget Batch-IDs are now stored on budget change records and available on budget change reports. There is a new Common Code (GLBU BATCHID) that allows the budget batch ID to be locked in.

New Common Codes were added to fiscal years and budget change dates on budget batches.

Transaction validation was tightened up on budget batches and the handling of WARN's and BLOCK's corrected in GLBUBATR. The new mask GLBUBAUX was added allowing only transfers between existing accounts such that no new associations can be created.

On GLBUUP, a problem was corrected on UNIX sites in which totals were wrong when there were more than nine Objects.

Summed budget versions now display correct values when referencing prior years.

Budget version security was corrected to eliminate memory errors in some situations. There was a change to GLUPKY that prevented a budget control key from pointing to itself. There was a change to tighten budget security within budget batches.

Annual budgets were merged with actual and encumbrances accumulators. This change will also be visible in the GLBUUP screen by reflecting all keys with associations on the annual budget screen whether they are with or without budgeted amounts.

The "beginning balance" and "no activity" features of transaction level reports were corrected to support date ranges that do not coincide with fiscal period boundaries. The "TR" inquiry was corrected to properly include/exclude EN totals and shows nine digit job numbers. Its speed was also increased. The "BA" report now calculates percentages properly. The "QU" inquiry now has some selection criteria.

The ledger code is now displayed when distributing multi- ledger JE batches, and used to check the data. Empty spool-files have been eliminated. The "replication of WOs" and "switching between text and JE views" problems were corrected in the JE batch editor. The JE batch proof was modified to correct double printing of offset lines and to print the report in wide format as needed to show the work order number.

The "MB" offsetting entry no longer requires all entries after the first to be credits.

A hierarchical approval system has now been added to JE batches similar to those in PO/AP.

RJE's now properly generate JE-ID seed values when using SYSTEMx or SYSTEMaax formats. They also no longer skip budgets on accounts where no actuals exist, allowing creation of new budgets. A defect when editing big screen selection criteria was corrected, along with a loophole in association required checking after trying to browse past either end of the record set.

GLJEUI and GLJEDI can now be used to create and distribute Inter-Fund JE batches while blocking manual inter-fund offsetting. Similarly, GLJEUN and GLJEDN can now be used to create and distribute Intra-Fund-Only JE batches while blocking manual inter-fund offsetting and requiring intra- fund balancing. Additional totals by fund are included.

The Preparer ID and Batch ID fields were expanded.

GLREFLTR now properly sorts account numbers longer than 16 characters and allows field reformatting (based on Common Code GLRE-FLTRSH) for the short format lines as already exists in the verbose format.

GLRESR08 and 15 now check for encumbrance amounts before skipping lines with zero amounts. GLRESR15 has a new optional question allowing TI and TO object types.

Audit reports were added to ledgers, keys, parts, objects, and groups showing before and after values of all fields, and information on who and when the change was made.

SACS reporting and file-streaming capability has been added to RDFs in support of California K-12 clients. This was extended to support F195/F196 reports and files for Washington State clients.

An option was added to Ad Hoc reports allowing an item to only be included in the first item encountered, even though other item ranges would have included it. Also, the total definition screens can now be ordered.

Freeform text is now enter-able for ledgers, keys, parts, groups, and objects, and can be printed on the corresponding file listings.

The system was modified to properly maintain FQA data when modified using GLUPKY.

Utilities

Several corrections were made to GL re-computes. Speed was improved. Prior year encumbrances are now correctly handled if the GL ledger has them and the paired JL ledger does not. A selected set of Keys can now be recomputed as long as there are no control keys. Invalid budget versions now result in warnings instead of stopping. An infinite loop is now detected and prevented when a key is set to have a control key of itself.

GLUTDIPB was corrected to require a single budget level when using FQAs.

GLUTDIPU was corrected to eliminate unnecessary EN and GL accumulator records.

GLUTDIVS was added to check validity of data in ledgers, keys, parts, objects, and groups. All clients should run this after installation of the 0003 HFS release.

GLUTRIFV was extended to display the contents of JE batch files.

GLUTSURS was extended to allow merging two keys by combining budgets, update information displayed on GLUPGN screens 2 & 3, and allow changing keys or objects to shorter lengths if padding is set to "N".

GLUTSUUN was change to issue a warning but continue if the undo encountered an invalid month in the audit accumulators. It was also changed to zero accumulated budget amounts and total budget changes in summed budget versions as these are system generated on the fly.

The work order number is now displayed in the GL250 posting report.

Special programs were added at posting time to support automatic allocation of expenses to funding sources and charge-backs between departments in an organization.

Corrections were done to expanding check numbers from 6 to 8 characters.

Bi-Tech Software Inc. 04/11/00 17 of 21 Management Summary - 0003 HFS