How customers, released products, sales quotations, sales orders, invoices and receivables across several legal entities in Microsoft Dynamics 365 Finance and Supply Chain Management can reach HubSpot, and how won deals flow back into the ERP.
Finance and Supply Chain Management is Microsoft's ERP for large and multinational companies. It runs customers, products, quotations, orders, invoicing and receivables across many legal entities, with financial dimensions on almost every record. HubSpot holds the people, the pipeline and the conversations.
Public documentation. The client's own admin issues credentials, with no vendor approval needed.
Open API. OData entities are documented publicly. The client's administrator registers a Microsoft Entra application and maps it to a user.
Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.
Every record a seller needs is exposed as a data entity, so HubSpot can carry the full quote-to-cash picture across legal entities.
Campaign Creators assessment
Microsoft exposes Finance and Supply Chain Management through OData data entities, the Data management package REST API for bulk and incremental loads, business events for change notifications, and custom services for logic the entities do not cover. All of them authenticate through Microsoft Entra ID. There is no codeless HubSpot app for this ERP, so the integration is a custom build. Its size comes from the ERP itself: several legal entities, financial dimensions, global address book parties, and enterprise data volumes.
Ratings are CC judgments from Microsoft's public documentation. Entity names, extensions and enabled business events are confirmed against the client's environment in discovery.
Customers (CustomersV3), released products V2, sales quotation headers, sales order headers and sales invoice headers are documented entities that can be read and written through OData, and exported in bulk through data management.
Each customer, order and invoice belongs to one legal entity (dataAreaId) and carries financial dimensions. HubSpot needs a clear rule for how one company that buys from several legal entities appears in the CRM.
An administrator registers a Microsoft Entra application and maps it to a user in Finance and Supply Chain Management. Any new entity, field or business event goes through the client's own release process.
Seven surfaces matter to a HubSpot build. Three carry the data, three move or trigger it, and one is a scope decision made at the start.
Customer accounts with organization name, customer group, currency, payment terms, credit limit, on-hold status, responsible employee and default financial dimensions.
Products released to each legal entity, with item number, search name, product group, sales unit and base sales price. Customer-specific prices live in trade agreements.
Sales quotations (including for prospects), sales orders with lines, posted sales invoices and free-text invoices, each in one legal entity and currency.
Moves data in and out as packages through a data project. With change tracking on, exports return only records created or changed since the last run.
Notifications when a business process runs, activated per legal entity in the business event catalog. Custom events can be added through an extension.
Service operations written in X++ for logic the data entities do not expose, such as a single call that returns a customer's open balance across legal entities.
A buyer can be a customer in several legal entities with a different account number in each. The team decides whether HubSpot shows one company with child records per legal entity, or one company per account.
A CC-built integration layer reads Finance and Supply Chain Management through OData and data management exports, listens for business events, matches records to HubSpot and writes in batches. Won deals travel the other way as sales quotations or sales orders in the right legal entity.
HubSpot owns contacts, marketing and pipeline. Finance and Supply Chain Management owns customer accounts, prices, credit, orders, invoices and receivables. Neither overwrites the other's fields.
Every ERP record written to HubSpot carries its legal entity code, and every document HubSpot sends names the legal entity it belongs to.
Large loads and nightly deltas go through data management packages. Business events and targeted OData reads handle what changes during the day.
Each phase ends on a gate the client signs off before the next begins. Legal entities are delivered in waves, so the first is live while the next is being configured.
List the legal entities, customer groups, financial dimensions, extensions and sales processes in scope. Agree the legal entity model in HubSpot and which system owns each field.
Register the Microsoft Entra application, map it to a least-privilege user in Finance and Supply Chain Management, and confirm a sandbox environment with representative data.
Confirm the entities to use, create data projects with change tracking, activate the business events needed per legal entity, and specify any custom entity or service for the client's developers.
Create the fscm_ properties, company hierarchy or association labels, deal stages that trigger ERP documents, and order and invoice properties in a HubSpot sandbox.
Build the event receiver, delta reader, entity resolver, document builder and batch writer, with idempotent writes, retry on 429, and an error replay queue.
Load customers, contacts, released products and an agreed window of orders and invoices per legal entity through package exports.
Run live for two weeks with outbound document creation in review mode, then switch on and add remaining legal entities in waves.
Entity and field names come from Microsoft's data entity documentation. Where a name is marked for confirmation, it is checked against the client's OData metadata in discovery, because extensions and versions can change entities.
| Finance & SCM field | HubSpot property | Object | Direction | Notes |
|---|---|---|---|---|
| Customers & contacts · CustomersV3 | ||||
| CustomerAccount | fscm_customer_account | Company | ↔ Both | Key, together with legal entity. Written to HubSpot on create. |
| dataAreaId | fscm_legal_entity | Company | ↔ Both | Legal entity code. Required on every write. |
| PartyNumber | fscm_party_number | Company | F&SCM → HS | Same organization across legal entities. |
| OrganizationName | name | Company | ↔ Both | HubSpot creates; ERP keeps its own on later edits. |
| AddressCity, AddressState, AddressCountryRegionId | city, state, country | Company | ↔ Both | Fill blanks only after create. |
| CustomerGroupId | fscm_customer_group | Company | F&SCM → HS | |
| SalesCurrencyCode | fscm_currency | Company | F&SCM → HS | |
| CreditLimit | fscm_credit_limit | Company | F&SCM → HS | Read-only in HubSpot. |
| OnHoldStatus | fscm_on_hold | Company | F&SCM → HS | Drives a credit-hold flag for sellers. |
| EmployeeResponsibleNumber | hubspot_owner_id | Company | F&SCM → HS | Mapped through a worker-to-owner table. |
| DefaultDimensionDisplayValue | fscm_default_dimensions | Company | F&SCM → HS | Financial dimensions as one display string. |
| PrimaryContactEmail / contact persons | email, firstname, lastname | Contact | ↔ Both | Associated to the company. Contact person entity confirmed in discovery. |
| Released products · Released products V2 entity | ||||
| ItemNumber | hs_sku | Product | F&SCM → HS | Shared key for products and line items. |
| SearchName | name | Product | F&SCM → HS | Confirm the display name field in discovery. |
| SalesPrice | price | Product | F&SCM → HS | Base price. Customer prices stay in trade agreements. |
| ProductGroupId | fscm_product_group | Product | F&SCM → HS | |
| Quotations & orders | ||||
| Deal (closed won) + line items | Sales quotation or sales order | Deal | HS → F&SCM | Header first, then lines, in the deal's legal entity. |
| SalesQuotationNumber, SalesQuotationStatus | fscm_quotation_number, fscm_quotation_status | Deal | F&SCM → HS | Quotations can also be raised for prospects (ProspectId). |
| SalesQuotationExpiryDate | fscm_quotation_expiry | Deal | F&SCM → HS | |
| SalesOrderNumber | fscm_sales_order_number | Order | F&SCM → HS | Order associated to the deal and company. |
| Sales order status | fscm_order_status | Order | F&SCM → HS | Open, delivered, invoiced. Confirm field name in discovery. |
| Sales order lines | Line items | Order | F&SCM → HS | Item number, quantity, price, from the sales order lines entity. |
| Invoices & receivables | ||||
| InvoiceNumber | fscm_invoice_number | Invoice | F&SCM → HS | Posted sales invoices; free-text invoices included if in scope. |
| InvoiceDate | fscm_invoice_date | Invoice | F&SCM → HS | |
| TotalInvoiceAmount, TotalTaxAmount | fscm_invoice_total, fscm_tax_total | Invoice | F&SCM → HS | In invoice currency. |
| SalesOrderNumber (on invoice) | Association to Order | Invoice | F&SCM → HS | Links invoice to its order. |
| Open amount and due date | fscm_open_amount, fscm_due_date | Invoice | F&SCM → HS | From open customer transactions. Entity confirmed in discovery. |
| Customer balance (all legal entities) | fscm_open_balance | Company | F&SCM → HS | Summed in the integration layer or a custom service. |
Finance and Supply Chain Management uses Microsoft Entra ID for service access. Throttling values are from Microsoft's service protection documentation for online environments.
| Topic | Finance & SCM | HubSpot |
|---|---|---|
| Interfaces | OData v4 at {environment}/data/ for public data entities; Data management package REST API for bulk import and export; custom services (JSON and SOAP) for X++ logic. | REST APIs: CRM objects, commerce objects, associations, imports. |
| Authentication | OAuth 2.0 client credentials through a Microsoft Entra application. The client ID is added under System administration › Setup › Microsoft Entra applications and mapped to a user whose roles set what it can read and write. | Private app access token or OAuth 2.0 public app, scoped per object. |
| Legal entities | OData returns the user's default company unless cross-company=true is added; filter on dataAreaId for one legal entity. Package exports take a legal entity ID. | One portal. Legal entity stored as a property on every ERP record. |
| Change notifications | Business events to HTTPS, Azure Service Bus or Azure Event Grid endpoints, activated per legal entity. Payload includes a control number; order is not guaranteed. | HubSpot webhooks for outbound triggers on deals and companies. |
| Paging & batching | Server-driven paging up to 10,000 records per page. Batch requests with atomic changesets. $expand one level deep. | Batch endpoints up to 100 records per call. |
| Throttling | Resource-based throttling returns HTTP 429 with Retry-After when the environment is under load. Data management and recurring integrations are exempt. Exact thresholds are not published; confirm with Microsoft. | Per-10-second burst and daily limits by subscription tier. |
| Change control | New entities, fields, events or services are X++ extensions deployed through the client's release process. | Custom properties on every paid tier. Custom objects need an Enterprise hub. |
Severity reflects impact on the SOW, not technical difficulty alone.
The same organization can hold a different customer account in each legal entity. Without an agreed model, HubSpot shows duplicate companies or mixes balances. Decide the model in discovery and key on party number plus legal entity.
Contact persons, open balances or custom fields may need a custom entity or service. That work sits in the client's ERP codebase and release cycle, so it is a dated dependency in the SOW.
Enterprise order and invoice history is large. Backfill runs through package exports by legal entity and date window, and HubSpot receives only the history the team will use.
Dimensions are configured per client and can be many. HubSpot receives the few that drive reporting as separate properties, and the full string for reference.
Business events are kept small and can arrive out of order. The integration treats each event as a prompt to read the current record, and a nightly delta export catches anything missed.
Each legal entity has its own currency and tax setup. HubSpot multi-currency is set up before backfill, and totals are shown as the ERP reports them.
Sellers see credit limit, on-hold status and open balance before they quote, so no one promises an order finance will block.
Closing a deal creates the quotation or sales order in the right legal entity, with the right customer account and items, without re-keying.
A parent company in HubSpot shows orders, invoices and balances from every legal entity the customer buys from.
Posted invoices and order lines let HubSpot report actual revenue by product, owner, region and dimension beside forecast.
Quotations raised for prospects appear on the HubSpot deal, so marketing and sales see quote activity before the account exists in the ERP.
Service tickets show recent orders, delivery status and open invoices on the same company record.
Each step happens in the system that owns it, and the other system sees the result. HubSpot runs the sale; Finance and Supply Chain Management runs fulfillment and finance in the right legal entity.
All custom properties use the fscm_ prefix in a Finance & SCM property group. Finance fields are read-only for HubSpot users.
| Internal name | Label | Object | Type | Source / logic |
|---|---|---|---|---|
| fscm_customer_account | Customer Account | Company | Single-line text | CustomerAccount; unique with legal entity |
| fscm_legal_entity | Legal Entity | Company | Dropdown | dataAreaId |
| fscm_party_number | Party Number | Company | Single-line text | PartyNumber; cross-entity key |
| fscm_customer_group | Customer Group | Company | Dropdown | CustomerGroupId |
| fscm_credit_limit | Credit Limit | Company | Number (currency) | CreditLimit |
| fscm_on_hold | On Hold | Company | Dropdown | OnHoldStatus |
| fscm_open_balance | Open Balance | Company | Number (currency) | Sum of open customer transactions |
| fscm_default_dimensions | Default Dimensions | Company | Single-line text | DefaultDimensionDisplayValue |
| fscm_quotation_number | Quotation No. | Deal | Single-line text | SalesQuotationNumber |
| fscm_sales_order_number | Sales Order No. | Order | Single-line text | SalesOrderNumber |
| fscm_invoice_number | Invoice No. | Invoice | Single-line text | InvoiceNumber |
| fscm_open_amount | Open Amount | Invoice | Number (currency) | Open customer transaction amount |
Choose the objects and fields for this engagement and the direction each one syncs. Required fields are the keys the integration cannot run without. Copy the summary into the SOW or a reply to the client.
Based on public documentation. Entity names, extensions and enabled business events are confirmed against the client's environment in discovery.
Yes, through a custom integration. There is no codeless HubSpot app for Finance and Supply Chain Management, so Campaign Creators builds on Microsoft's OData data entities, the Data management package REST API, business events and custom services, all authenticated through Microsoft Entra ID.
Customers, contacts and released products sync to HubSpot companies, contacts and products. Won HubSpot deals can create sales quotations or sales orders in the ERP. Orders, invoices, open balances and the financial dimensions that drive reporting are written back to HubSpot.
Every customer, order and invoice belongs to one legal entity and carries financial dimensions. The legal entity model is agreed in discovery, records are keyed on party number plus legal entity so balances never mix, and legal entities go live in waves.
Seven phases, each closed by a client sign-off: discovery and legal entities, access and environments, entity and event setup, the HubSpot data model, the build, backfill per legal entity, and a two-week parallel run before outbound document creation is switched on.
Timeline and cost depend on the legal entities, financial dimensions, extensions and history in scope, and on any custom entities the client's developers need to add. Campaign Creators confirms these in discovery and provides a fixed scope before the build starts.