| There are several significant Intuit requirements for the Client Testing phase that require advanced planning. These items are listed below: |
Establish your branding presence in our test environment (CQAT)
 |
 |
Complete the Branding Setup form and e-mail it to your Implementation Manager. |
|
|
Your Implementation Manager will inform you once your branding presence is available in our test environment and will also provide your branding identification (BID) number. |
|
|
You need to install our testing files to point Quicken or QuickBooks to our CQAT region. |
|
Internet Connectivity:
|
|
Direct Internet connectivity is required to allow Intuit to connect to your OFX System and execute the required test steps. |
|
Production/End to End Processing:
|
|
All code/systems/etc. in use at the Financial Institution must be Production level and capable of full End-to-End Processing.
|
 |
For example: transfers must execute and post to the accounts, payments must age and generate checks that are mailed out to be received/verified by Intuit, email must be routed to an appropriate customer service area and responses must be routed back through the OFX Server/System to the client. |
|
|
|
Simulated production regions or pre-production regions where human intervention (i.e. manually triggering batch operations, manually cutting/mailing payments, etc.) do not meet Intuit requirements for this testing phase. |
|
SSL Certificates:
|
|
Intuit products will establish a 128-bit connection with the Financial Institution's OFX server even if the server will allow a lesser connection from another client source. |
|
|
Intuit requires the VeriSign OFX CA Generation 2 certificate. Additional information on this is available at Financial SSL Certificates for OFX |
|
Test Accounts Requirements are below:
|
|
Supply no more than 5 accounts. |
|
|
One of each OFX account type (ACCTTYPE) you plan to support must be present. |
|
|
Each OFX transaction type (TRNTYPE) you plan to support must be present at least once. |
|
|
One account must have at least 100 transactions. |
|
Comparison Data:
|
|
For each populated test account provided, a means of verifying the data/transaction mapping must be provided. |
|
|
This Comparison Data must be from a non-OFX based interface. |
|
|
It could be an Excel spreadsheet which is exported from a backend system, a website that Intuit can log into and view account information/account details, etc. |
|
|
Website access is our preferred method for comparison data. |
|
Common FIAT Issues:
|
|
In an attempt to avoid any unnecessary delays, the issues in the Common FIAT Issues document provide insight into the most common problems encountered during the FIAT process. |
|
|
It is recommended that this document be reviewed prior to starting FIAT. |
|
Note
|
|
Intuit strongly discourages the use of Social Security numbers for any account related values. |
|
|
These may include, but are not limited to: Customer ID, Account Number, PIN, Password, or Challenge Phrase. |
|
|
Once Social Security number is used for an account related value and customers have established their online account within Quicken or QuickBooks, customer action will be required to change from their Social Security number to a new value. |
|
|
