Salesforce and Microsoft Dynamics 365 integration

Closed deals become billing records in Dynamics 365 with the right product codes and dates, and billing status comes back to the account.

Both waysSalesforce and Microsoft Dynamics 365

What moves between them

  • Into SalesforceBilling and invoice status on the account, so account teams see who is billed, paused or overdue.
  • Out of SalesforceClosed contracts as billing records: products, billing codes, start and end dates, tiers and price increases.

How we build it

  • An audit of every billing codeEach Salesforce product checked against finance’s code list. A wrong code bills silently, which is worse than a missing one.
  • A written payload contractWhich field feeds which billing field, in which order codes are resolved, and who owns each value.
  • Date rules costed with financeMid-month starts, rounding and renewals decided with the cost of each option in front of finance.
  • Tested against the billing test environmentReal closed deals replayed before anything reaches production billing.

What goes wrong, and the fix

Problems we have found and fixed in production.

  • Several products carry the same billing codeCodes copied between products years ago. Each is traced to the right one, and the field gets an owner.
  • A credit or discount code on a recurring chargeEasy to miss in Salesforce and costly in billing. The audit flags codes used outside their type.
  • Product codes that are not uniqueA join on product code returns two products. Billing joins on the billing code field instead.

Questions

Salesforce Billing or the ERP?

If finance already runs Dynamics 365, billing usually stays there and Salesforce sends clean contracts. We do not add a second billing system.

Other Salesforce integrations

  • Salesforce and SnowflakeWarehouse metrics on every Salesforce account, Salesforce data in the warehouse for reporting, and one definition both sides agree on.
  • Salesforce and DocuSignAgreements go out from the deal with the right template and signers, and signed terms, dates and signers come back onto it every time.
  • Salesforce and Adobe Commerce (Magento)Customers, orders and catalogue kept in step between Salesforce and the storefront, with one ID both sides trust and a switch in front of every write.
  • Salesforce and commercetoolsA move to commercetools without splitting customers in two: the same account IDs on the new platform, orders from both platforms counted once, and the old platform retired in planned steps.
  • Salesforce and Apollo.ioProspects and enrichment from Apollo.io without blanked fields, wrong owners or “new” leads that are already customers.
  • Salesforce and IntercomSupport chats logged on the right contact and account, credited to the person who answered, and the account owner and region visible to the support team.

Talk to us about Salesforce and Microsoft Dynamics 365.

Tell us which systems are involved and what is going wrong. We reply within one business day, and new engagements begin in January 2027.

hello@feldtgroup.com