Dynamics 365 F&O–Salesforce Sync for CPG Sales and Finance Teams

What this looks like in consumer packaged goods

A national CPG brand sells to a distributor operating in multiple legal entities. Salesforce has a strategic parent account and regional opportunities. Finance maintains separate customer accounts with different terms and currencies. A parent-level CRM update must not overwrite every financial customer or expose one entity’s balance as a group-wide credit decision.

Records, ownership, and update rules

Work through the process

1. 01
   Identify the legal boundary

   Enumerate the legal entities and customer IDs that belong to each strategic account. A customer number may only be meaningful inside its entity, so include both in mapping and reconciliation.
2. 02
   Agree on writable fields

   Separate sales-owned relationship fields from finance-owned terms and legal details. A change request can travel to finance without granting every Salesforce editor permission to change the accepted customer record.
3. 03
   Label financial context precisely

   Choose useful status fields and explain their scope. A regional balance should remain labeled by entity and currency; avoid combining amounts that require a deliberate finance conversion policy.
4. 04
   Exercise account changes

   Test a new branch, a renamed distributor, and a moved account owner. Confirm that these relationship changes preserve the legal customer key and the history of accepted orders.
5. 05
   Load one customer number from two F&O entities into Salesforce

   Choose a distributor whose customer number exists in two Dynamics 365 F&O legal entities, both linked to the Salesforce strategic account. On the Salesforce account, each financial status field must display its legal entity, currency and effective timestamp; two entries with the same number and different entities must stay separate, not merge into one balance. Then reassign the account owner in Salesforce and re-read the F&O customers: payment terms, legal name and subsidiary must be unchanged. Stop the rollout if a status field arrives without an entity label, if the two customers collapse into one Salesforce record, or if the ownership change touched a finance-owned field in F&O.

Handle the exceptions explicitly

Same customer number in two entities

Use the composite legal-entity key and prevent accidental cross-entity joins.

Account is merged in Salesforce

Review every finance mapping before applying the merge; preserve references needed by existing transactions.

Currency differs from opportunity

Present the source currency and let finance govern conversion rather than replacing the original amount.

What to verify before expanding

• Every financial status identifies its legal entity and currency.
• A sales ownership change does not alter finance-owned customer terms.
• The same customer number in two F&O legal entities produces two distinct financial relationships in Salesforce.
• A source balance retains its currency and effective timestamp when the opportunity uses another reporting currency.

Technical references

• Stacksync two-way sync quick start