How do QuickBooks Companies/Customers work with Salesforce Accounts?

overview breadwinner requires that all quickbooks customers are directly associated with a salesforce account a quickbooks company which has an invoice associated with it is a ‘quickbooks customer' breadwinner contains a custom object in salesforce called "quickbooks company" this is a perfect copy of your quickbooks customer, (in the salesforce api this is called a bac or a breadwinner account connection) that sits below the salesforce account object as a child of the salesforce account you may see a related list on your salesforce account called "affiliated quickbooks company" these are the quickbooks companies associated with (or affiliated with) that salesforce account this approach allows you to have multiple quickbooks customers associated with a single salesforce account this is a powerful feature and comes in handy when a single salesforce account might have multiple departments or branches to be billed in quickbooks and, because a quickbooks company can be associated with any account, we know which salesforce account to put an invoice under when importing new quickbooks invoices even if the name or spelling is entirely different ( if you are a salesforce consultant or developer, and wish to see more information on this relationship, please go to the resources tab of our website https //breadwinner com/quickbooks salesforce/ , and look for technical details https //breadwinner com/quickbooks salesforce/technical resources developers/ to see the erd you may also be interested in the other option syncing and mapping https //breadwinner com/quickbooks salesforce/demo/ on that tab) initial sync of quickbooks customers to salesforce accounts every single quickbooks customer must be associated with a single salesforce account that's what our initial account sync does connects all your quickbooks customers to a salesforce account you can use our suggested match feature that's where we try to match a quickbooks customer based on the company name, or email, or phone, or address if we can't match a quickbooks customer to a salesforce account automatically, the relevant account might still be in salesforce if that's the case, use the manual match to connect the quickbooks customer to the correct salesforce account but if there is no corresponding salesforce account, go ahead and select create new account and we'll create a corresponding salesforce account (and create a bac as a child object) and populate it with quickbooks data if you are connecting quickbooks to a new, (mostly) empty salesforce org (such as when in a salesforce trial, or installing breadwinner in a sandbox), the initial sync is a great way to populate your salesforce database just click next on the bottom of the initial account sync pages to bring in quickbooks contacts, 100 per page ongoing sync of quickbooks customers when you change any value in quickbooks on the quickbooks customers (such as the name, or default days due), we'll update that in salesforce within the hour this won't update the salesforce account but will change the details of the bac below it you can optionally write triggers or other code to update the salesforce account based on this change, but be aware that a salesforce account might have no bac object, one, or many changing the association between quickbooks customers and salesforce accounts you may find that a quickbooks company is associated with the wrong salesforce account to fix this, please go this help article docid\ vylfgmmm4mxgfkgex0ruf creating a new quickbooks company from salesforce when you click new invoice in salesforce from the account or opportunity page, you are asked which quickbooks company you would like to connect it to if there are any quickbooks customers already associated with that account, you will see them displayed there this is also the time to create a new quickbooks company in quickbooks and connect it to the salesforce account by selecting the option "new quickbooks company" this will let you create a quickbooks company based on the details in the salesforce account once created, you continue on to the new invoice page if you want to create a new quickbooks company based on a salesforce account, but don't want to create a new quickbooks invoice, then just click the new invoice button on the relevant salesforce account, then select "new quickbooks company", create the quickbooks company, but once you arrive at the new invoice page, rather than creating an invoice simply abandon the process by going to any other salesforce tab new quickbooks customer found after initial sync you might find your business requires you to create quickbooks invoices in quickbooks manually, or through other systems rather than creating quickbooks invoices through breadwinner indeed, some of our customers use breadwinner only as a one way sync from quickbooks to salesforce to see their customer information held in quickbooks and never create an invoice in quickbooks through breadwinner and, credit notes can only be created in quickbooks, not via breadwinner (this is for financial security) there is no explicit problem with this approach, however, when we find a new quickbooks invoice attached to a quickbooks customer we have never seen before, we create a new salesforce account (and corresponding quickbooks contact child object) to represent that new quickbooks customer this can lead to duplicate salesforce accounts we mitigate this by first checking for an existing salesforce account with an identical spelling as the quickbooks customer if your third party system is creating quickbooks companies based on salesforce, this should prevent breadwinner from creating duplicate salesforce accounts additionally, if you upload a large number of quickbooks companies at one time, you can re run the account sync from the breadwinner tab immediately after uploading them, to control how they are matched there are other ways to configure this auto matching that occurs after the initial sync please file a case with support explaining your configuration, what additional apps you use, and what your ideal scenario is