How do BWP Customers work with Salesforce Accounts for the Breadwinner Payment App?

overview part of the breadwinner architecture is that certain records from the payment system are replicated into breadwinner custom salesforce objects one of these breadwinner custom salesforce objects is the “bwp customer” object, which contains the customer record from the payment system the breadwinner payment app requires that the bwp customers (payers/recipients of transactions) are directly associated with a salesforce account or contact this is typically done during the breadwinner setup one salesforce account or contact may have one or more bwp customers associated with it this is a powerful feature and comes in handy when a single salesforce account or contact might have multiple departments or branches making payments or receiving funds after a bwp customer is mapped to an account or contact, breadwinner creates a two related lists on your salesforce account or contact one is called transactions and contains the payment transactions associated with the account or contact the other is called “customers” these are the bwp customers associated with (or affiliated with) that salesforce account or contact payments or other transactions are associated with the bwp customer record therefore, if a bwp customer is associated with an account or contact, breadwinner knows which salesforce account or contact to link a payment or transaction to when importing new data—even if the name or spelling is entirely different (for salesforce consultants or developers, please refer to the resources tab of our website for technical details and an erd) initial mapping of bwp customers to perform the initial mapping, users can use our suggested match feature, which attempts to match bwp customers based on company name, email, phone, or address if breadwinner can't automatically match a bwp customer to a salesforce account or contact, the relevant account or contact might still exist in salesforce if that’s the case, use the manual match feature to connect the bwp customer to the correct salesforce account or contact if there is no corresponding salesforce account, select create new account , and breadwinner will create a corresponding salesforce account (and create a bpc as a child object) and populate it with bwp customer data if connecting the breadwinner payment app to a new (mostly) empty salesforce org (such as during a salesforce trial or when installing breadwinner in a sandbox), the initial sync is a great way to populate the salesforce account database clicking “next” at the bottom of the initial account sync pages brings in payment contacts, 100 per page ongoing sync of bwp customers when values in your payment app for bwp customers (such as the name or default payment terms) are changed, breadwinner will update these in salesforce within the hour this won't update the parent salesforce account but will change the details of the bwp customer to update the salesforce account based on this change, requires triggers or flows, which the user has to create based on their requirements changing the association of a bwp customer if a bwp customer is associated with the wrong salesforce account, it can be reparented this help article http //help xero breadwinner com/support/solutions/articles/44001664450 moving invoices and xero contacts to a different salesforce account explains how to move transactions and contacts to different salesforce accounts creating a new breadwinner payment customer from salesforce selecting new transaction in salesforce from the account or opportunity page prompts the user to select the payment contact you would like to connect it to if any bwp customers are already associated with that account, they will appear here this is also the time to create a new payment contact in your payment app and connect it to the salesforce account by selecting the “new payment contact” option this will let you create a bpc based on the details in the salesforce account once created, you continue on to the new transaction page to create a new payment contact based on a salesforce account, but without creating a new payment transaction, one can click the new transaction button on the relevant salesforce account, then select “new payment contact”, create the payment contact, and at that point terminate the operation new bwp customer found after initial sync you might find that your business requires you to create payment transactions in your payment app manually or through other systems—rather than creating them through the breadwinner payment app in salesforce indeed, some of our customers use the breadwinner payment app only as a one way sync to salesforce to see their customer and payment information there is no explicit problem with this approach; however, if breadwinner finds a new payment transaction attached to a bwp customer, it creates a new salesforce account (and corresponding payment contact child object) to represent that new bwp customer this can lead to duplicate salesforce accounts breadwinner mitigates this by first checking whether an existing salesforce account has the same spelling as the bwp customer if your third party system is creating bwp customers based on salesforce, this should prevent the breadwinner payment app from creating duplicate salesforce accounts additionally, if you upload a large number of bwp customers 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, which additional apps you use, and your desired scenario