Implement Quickbooks web connector support in a django web application

We'd like to add Quickbooks Web Connector support to an existing django application, to sync transactions from the online application with their quickbooks desktop application. The idea is that people will log into their account and download a Quickbooks Web Connector File that will contain all their connection credentials. They will be able to import that file into their Web Connector application and will be able to connect to our application that way. Multiple quickbooks company files can be connected to one online account. At the point of export/sync, the user will be asked to choose the company file to sync. Importing data: Once the connection is done, they should be able to: 1) Import their charts of accounts in quickbooks with the online application 2) Import customer, vendor and employee information from quickbooks to the online application - all these are stored as contacts in the online application 3) Map expense accounts in quickbooks to transaction types in the online application (these would be used to export transactions to quickbooks) Importing data will be done manually - an option should be there for this. The last import date should be stored and shown to the user. Exporting data: The user should be able to initiate a transaction export, choose a company file and also update/change the default mappings between transaction types and quickbooks accounts. They should have the option of combining transactions that occur in the same day based on the user, or on the transaction type. If they decide to combine transactions, then they have the option of exporting them as itemized transactions, or as just one transaction with the total figure. Exporting data will be done manually - an option should be there for this. The last export date should be stored and shown to the user. By default, they should be able to export data starting from that last export date, up to the current date (yesterday) Dates should be timezone sensitive, and display in the user's timezone, but be stored in UTC. The application should be coded with best practice coding, over 90% code coverage and availability of all source code. At the start of the project you will propose a list of third party applications that you will be using (if any), along with a design for the application - we will vet this list to ensure that these applications meet the criteria necessary for inclusion, and we will vet the design before we proceed. There is possibility for longer term engagement, and as such, we prefer individuals over teams. The candidates can be from anywhere, but must be able to work/meet during the US daytime at least once a day for the duration of this project. The candidates must be conversant with source control software. You will need to be familiar with source control systems (mercurial, git, bitbucket, github, etc)