70 likes | 176 Views
Planning for CountyCashier V3.0. CountyCashier 3.0. 100% 32 bit application SQL database backend Historical Reports should be much faster All historical records should be available for all reports. CountyCashier 3.0. Hardware requirements: Same as halFILE for the workstation
E N D
CountyCashier 3.0 • 100% 32 bit application • SQL database backend • Historical Reports should be much faster • All historical records should be available for all reports
CountyCashier 3.0 • Hardware requirements: • Same as halFILE for the workstation • SQL server for the databases (can share existing halFILE SQL server) • SSL web server if implementing Level 1 electronic recording
CountyCashier 3.0 • New features: • Configure/Offices/Official Records tab/Print instrument type description as second line on receipt? • Configure/Instrument Types/Inactive switch • Configure/Accounts/Carry Balances button • Verify date and time once per day per workstation when initially logging in
CountyCashier 3.0 • Potential new functions: • Electronic recording – Level 1 for Title Companies and other trusted accounts • Handling Fictitious Business Names (FBN) 100% within CountyCashier • Handling Marriage Licenses 100% within CountyCashier
CountyCashier 3.0 • Other new features: • Ability to un-void a receipt • Ability to un-void a payment • Ability to update an existing receipt and have it automatically correct any end of day reporting affected • Ability to have a detailed audit report of all adds, updates and deletions • Better handling of escrow accounts
CountyCashier 3.0 • Time frame • Beta in late Spring 2006, early summer • General release late summer, early fall