Here's an overview of the processes and timeline that will get you up and running. We'll provide step-by-step support throughout the process.
API Server Setup
Steps to Set Up the API Server
- Determine if the technology will be hosted or outsourced
- Integrate the FDX or OFX server
- Create an interface for authenticating customers, or integrate with an existing interface
- Write software to map the data in your tax database onto the chosen specification
- Identify test accounts that meet the requirements stated in Test Requirements and Test Accounts. Provide authentication information and data printouts for these test accounts to your TurboTax import representative
- Execute a preliminary test for syntactic accuracy
- Complete server testing
- Complete End-To-End Integration
All tools and other supporting resources will be available to you once your institution is signed up as a TurboTax import partner, and you receive your credentials to access the password-protected areas of this partner portal.
Time Required for This Phase
The amount of time required to complete this phase varies depending on whether or not there is an API server already in place. We typically allocate two to four weeks for this phase.
API Server Testing
What is API Server Testing?
The purpose of the API server testing phase is to ensure that the API performs in compliance with the FDX or OFX specification.
At a high level, compliance testing includes:
- Tax form response syntax
- Error state coding
Time Required for This Phase
The amount of time required to complete this phase depends upon the number of errors found and your ability to quickly resolve issues. We typically allocate one to five days for this phase.
API Integration Testing
The purpose of end to end (E2E) testing is to verify that customer tax data is mapped correctly to the tags in the API response and that those data values have the correct format. This testing also validates that the TurboTax file does not return any missing or mismatched data that would impact any tax calculations. E2E testing is performed in your test environment and requires that you work directly with your implementation manager to complete the following steps:
- Stage mock data (no PII) in your test environment
- Create a W-2 or 1099/1098 document(s) with mock data
- Test the import in TurboTax and save a copy of the file
- Send PDF copies of the mock W-2 or 1099/1098 document(s) and the imported TurboTax file (*.taxYYYY) to your implementation manager
The amount of time required to complete this testing depends upon the number of errors found and your ability to quickly resolve issues. We typically allocate one day to two weeks for this phase.
Customizing your TurboTax Screen
As an OFX partner, you can make self-serve changes to your provider information, including your authentication screen. You can edit, update or remove the following:
- Company Logo (as specified below)
- Size: 64x64px or 150x31px
- File format: PNG
- Must have transparent background
- DPI: 72
- Field Label Names
- Paragraph One - explains what information the user needs to enter to log on and obtain their tax data
- Paragraph Two - tells the user what to do if they have questions or need assistance. You can also add a hyperlink that directs the user to your company’s support web page for additional help