Both:

Microsoft SQL Server Integration:
 - Major "under-the-hood" architecture change moves all customer and processor data into Microsoft SQL Server databases. No customer or processor data will reside in the web server thereby providing added protection for this data. Browser-based imports and exports are provided where necessary. The system supports SQL Server 2000 and the recently released SQL Server 2005.

ACH risk management reporting and processing:
To give you the tools you need to manage your ACH risk, we have developed an automated and integrated ACH risk managment sub-system. This functionality takes historical records of customer ACH activity including returns and originated items and captures them automatically in the system. This data is then examined during server processing and compared with the current activity, looking for deviations from "norms". Deviation percentages are configurable by customer for originated items as well as return items. A master switch controls whether or not any flagged deviations cause processing to be aborted. We recommend that processors leave this master switch turned off until 2-4 weeks of history has been accumulated. A Risk Management report can be produced on either the client or processor system showing return item rates and originated item rates by SEC code. The ACH Risk Management server-side processing report also provides daily limit checking by customer. Basically, the system will allow the the processor to detect abnormal customer activity at a glance and comply with NACHA audit requirments.

In addtion, the ACH Risk Management sub-system provides support for management of debit transaction authorizations. Processors can require clients to submit signed account authorizations by account number. Activation of checking for these authorized accounts is done customer by customer. Any unauthorized debits will be rejected. This feature helps financial institutions comply with the latest NACHA Operating Rules.

Faster grid loading:
Data files stored in SQL Server carry descriptive information about the file and therefore load much faster. Also, grid striping has been optimized to show "Loading grid" while it is performing this function and the body of the grid remains hidden until the entire grid has been formatted.

Removal of most cookies:
Some pieces of session information previously stored in "cookies" have been relocated to a SQL Server database. This greatly reduces data security risks.

Database error handling:
If a database error occurred prior to release 3.0, the error message(s) reporting the error showed certain secure pieces of data that an intruder could use to compromise the system. These errors are now logged to the database but the user sees nothing out of the ordinary and the system continues to process.

Database credentials now hidden in IIS's Metabase:
For added security, we have moved database credentials to the web server’s own database. This separates the credentials from the web site providing increased security.

Server:

Notification to client when an ACH file that was warehoused is finally released for processing:
If a client commits a file with an effective date too far in the future, the file can be warehoused on the processor system until such time that it should be released. At that time, the client will receive a log message indicating that the file has been released for processing.

No need to create folders or upload master files for new customers:
Adding a new customer is a breeze now, just add the new customer profile to your database and log in as the client.

New option to email processor when client sends any file(s):
For processors whose customers infrequently send files for processing, have the system email you a notification that a customer has committed one or more files.

Duplicate files committed by clients will be detected:
If a client commits a file that they already commited, the server system will detect this and prevent the file from being processed.

Digital certificate management:
Processors can now manage their own client certificates without having to contact SBT (achbusiness.com) or using MS Certificate Authority (if self-hosting). You can issue and deny certificate requests as well as revoke certicates and publish a new Certificate Revocation List (CRL).

Client:

Show files for n # of days:
Customers can now configure their application file grids to show a minimal number of files (3, 10, 36, or All days). This reduces the amount of data being shown which ultimately improves performance.

Amounts for ACH files:
ACH applications will now show the amounts for ACH files. If an ACH file is unbalanced, the higher of the DR/CR amounts will be shown.

Multiple file commits:
It’s here! Commit multiple files with a single click.

Faster OFAC searches:
As a part of the conversion to SQL Server databases, the OFAC SDN List now resides in a SQL Server table. Using the power of the Microsoft SQL Server database engine along with full-text SQL searches, OFAC search time is dramatically reduced.

Auto archive for all types of wires:
The auto-archive option has been expanded to handle not only outgoing wire transfers, but also incoming wire advices and wire confirmations.

New dollar limit for verifying wires:
Now have different limits for creating and verifying wire transfers.

Client can now generate an ACH reversal file from the ACH File Delivery application grid:
The Reverse button is now available on the ACH File Delivery application in case a file is double-posted to DDA.