Intuit Intuit HomeIntuit Products
Intuit Financial Institutions
Welcome Visitor
Home
Highlights
2009 Product Launches
Connectivity Methods
Connectivity Demos
Connectivity Comp
How to Get Started
FAQs
QuickLinks
FI Call / Newsletter
Sign Up for Site Tour
FFIEC Guidance (MFA)
Express Web Connect
Marketing Tiers
Become a FI Partner
OFX providers
401(k) Connectivity
Download
QuickBooks Software
Quicken Software
Tools
Support
OFX Money
Contact FI Support
Support Roadmap
Training Videos
Training Calendar
Cheat Sheet
OL KnowledgeBase
Web Connect Implementation Steps
1. Prepare test accounts with transaction data.
 
  • Supply no more than 5 accounts to be used for testing.

  • One of each OFX account type (ACCTTYPE) you plan to support must be present (Checking, Savings, Line of Credit, Money Market, Credit Card, Investment, and/or 401k).

  • Each transaction type (TRNTYPE) you plan to support must be present.

  • One account must have at least 100 transactions.

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.
2. Complete the FIAT Web Connect Questionnaire.
  Download and complete the FIAT Web Connect Questionnaire. Please ensure the following items are completed and included in your FIAT Questionnaire responses:

  • Transaction & Account Types
    All supported transaction types and account types are represented.

  • Comparison Data
    For each test account provided, a means of verifying the transaction data is required. Direct access to the financial institution's web site is our preferred method for obtaining comparison data; however alternate methods such as a spreadsheet export from a backend production system are acceptable.

  • Production/End-to-End Processing
    All code and systems in use for FIAT must be production level and capable of full end-to-end processing. Simulated production regions or pre-production regions where human intervention is required do not conform to Intuit standards for FIAT.

  • Web Site Navigation
    If specific web site navigational instructions are needed to access the site, those should be provided as well.

You'll finalize the Web Connect FIAT Questionnaire and forward to your Implementation Manager once you've completed the next step, Prepare for Intuit testing.
3. Prepare for Intuit testing.
 
  1. Detect and correct these common problems:

    • Data Mapping
      Incorrect data mappings are frequent test blockers, so please ensure these problems are corrected during your testing. Make sure that your transactions are mapped to the correct OFX transaction types and that the signage is accurate.

      Incorrect signage for credit card and line of credit accounts is a frequent problem. Per the OFX specification, all liabilities are negative. Quicken and QuickBooks will make the appropriate adjustments to Balances and Credit Available values.

    • FITID's
      Another common problem is duplicate FITID's. FITID's must be completely unique and persistent within each account.

    • 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.

  2. Using the information on the completed FIAT questionnaire, perform an actual Web Connect download to validate connectivity and data transfer into the Quicken and/or QuickBooks software. Your test must be successful and error free for Intuit to begin testing. Verify the data accuracy against the comparison data.

  3. Download and save a Web Connect file to your computer. Open the file as a Response Script in the OFX Viewer application. Errors in the Response Error section must be addressed prior to Intuit beginning to test.

  4. Send the completed FIAT questionnaire to your Implementation Manager. We'll then do a quick connectivity test to ensure that we can complete a login and download session for each client, and then we'll forward on to the quality assurance team to begin FIAT testing.

    As you're preparing for Intuit testing, keep your Implementation Manager apprised of your progress. We'd like to know when you expect to be ready for us to test, but because of constantly changing schedules and QA team workload we do not "pre-schedule" FIAT.
4. Intuit performs QA review & validation.
  Once FIAT begins, you should expect first round results in 4-6 business days and will often receive them ahead of schedule. In rare circumstances, first round feedback may take as long as two weeks. Your Implementation Manager can give an estimated response time when you begin FIAT.

Once the QA team has completed their FIAT tests, a complete report of findings will be provided to you by your Implementation Manager. Results will be in the form of a MS Word document with all issues listed in order of severity - from 0-Inquiry and 1-Critical through 7-Informational.

If there are no test findings (which is extremely rare), validation is complete and approval is given for production launch. Where problems were found, you'll need to respond to each issue on the QA findings report. Additional cycles of FIAT review and validation may be required to close all issues. Prior to subsequent FIAT test rounds, each issue in the document must have a detailed written response in the "FI Response" section. Subsequent FIAT test rounds will begin upon the return of the above mentioned issues document with your responses. This cycle will continue until there are no Open Issues remaining, at which time the FIAT cycle is complete and approval is given for production launch.

Most banking and credit card implementations require 3-4 weeks for the complete FIAT cycle, while investment and 401(k) implementations normally require 4-6 weeks. Primary drivers of the testing schedule include (1) the number of issues found; (2) the length of time required to correct and respond to reported issues; and (3) the amount of regression testing required for subsequent FIAT cycles.
Privacy Legal Contact Us About Intuit Feedback