QuickBooks to Salesforce Financial Visibility Provide visibility of invoices, payments, transaction history, and balances from QuickBooks to Salesforce. NOTHING to be transferred from Salesforce to QuickBooks. Requirements: 1) Synchronize QuickBooks (QB) customers with Salesforce Accounts a. Do Not sync inactive QB customers b. Initial sync will match exact customer name of QB with Salesforce. i. If the Salesforce account exists, it would store QB sync ID into Salesforce for that customers. ii. If the account does not exist in Salesforce, provide a list of QB customers not in Salesforce and give an option to create those in Salesforce. If selected the account would be created with the QB information and the syncID would be set. 2) Show outstanding invoices in Salesforce for the account. Invoices shall show all details of items, descriptions, sales tax, and total. 3) Show current payments for last 3 months in Salesforce for the account 4) Show transactions history of invoices (closed or paid) and payments in Salesforce for the account. Invoice history will show all details as in 2. 5) Show current balance for the Salesforce account. 6) All records synced from QB to Salesforce must use syncID so that if the record is updated in QB, it will update the record in Salesforce rather than create a new record. 7) QB SDK or QBWC (web connector) will be used for all sync between QB to Salesforce. All sync will be performed from the QB desktop user (rather than Salesforce user). 8) Transfers to Salesforce must follow the [url removed, login to view] best practices for data transfer including things like not transferring more than 2000 records at a time, etc. These best practices can be found at Salesforce. 9) Provide user documentation on use of the product. Should be one or two pages. NDA will be required for project.
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):
a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.
b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).
Windows OS (NT, 2000, XP) or Web App.