Integration Products | Campaign Creators

SAP S/4HANA HubSpot Integration | Campaign Creators

Written by Campaign Creators | Nov 17, 2026, 2:41:04 PM
Integration Assessment
Integration Assessment · ERP

SAP S/4HANA × HubSpot

How SAP S/4HANA customer master, materials, prices, sales orders and billing documents can reach HubSpot, and how won HubSpot deals can become S/4HANA sales orders, using the OData and SOAP APIs SAP publishes for S/4HANA.

Business Partner APISales Order APIBilling Document APIProduct masterOData and SOAPCloud or on-premise
Platform ownerSAP
Integration typeCustom, built on SAP's published APIs
Primary directionS/4HANA → HubSpot, orders back
FeasibilityBuildable, well documented
API accessOpen API
01 — Summary

Does SAP S/4HANA integrate with HubSpot?

S/4HANA runs order-to-cash for the business. HubSpot runs the customer relationship and the sales pipeline. The integration lets each system do its job and gives sales the ERP facts it needs.

API access
Open APIOpen with conditionsGated API

Public documentation. The client's own admin issues credentials, with no vendor approval needed.

Open API. Services are catalogued publicly on the SAP Business Accelerator Hub. The client's SAP team sets up communication arrangements or activates the OData services.

Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.

S/4HANA publishes the APIs this integration needs, so HubSpot can see every account, order and invoice while SAP stays the system of record for finance.

Campaign Creators assessment

SAP catalogs released OData (v2 and v4) and SOAP APIs for S/4HANA on the SAP Business Accelerator Hub, including Business Partner, Sales Order, Sales Quotation, Billing Document and Product master. HubSpot does not publish its own SAP app, so this is a custom build on those APIs. Two things set the pace: how the client runs S/4HANA (Cloud Public Edition exposes APIs through communication arrangements; Private Edition and on-premise systems need the OData services activated and a secure network path), and the SAP sales structures (sales areas, partner functions and pricing procedures) that every customer and order carries.

Scorecard
Data richnessHigh
API coverageStrong
Connectivity setupVaries
Build complexityMod–High

Ratings are CC judgments from SAP's public documentation. The client's deployment, released services, custom fields and limits are confirmed during discovery.

Strength

Released, documented APIs

Business partners, sales orders, billing documents and products each have a released API with a published data model. Sales orders carry a LastChangeDateTime, so changes can be read in small batches.

Plan for

SAP sales structures

A customer in S/4HANA is set up per sales area (sales organization, distribution channel, division) with partner functions such as sold-to, ship-to, bill-to and payer. HubSpot needs clear rules for which of these become companies, and how orders find the right ones.

Gate

Access depends on the deployment

Cloud Public Edition needs a communication user and arrangements. On-premise and Private Edition need the services activated and a network path agreed with IT and Basis. Both come before any build.

02 — API modules

Which SAP S/4HANA APIs does the integration use?

Seven S/4HANA surfaces matter to HubSpot. Four carry the integration, two enrich it, and one is a scope decision the client makes early.

Core

Business Partner

API_BUSINESS_PARTNER · A_BusinessPartner

The customer master. One business partner holds the organization, its addresses, contact persons and the customer role with company code and sales area data.

  • to_Customer → to_CustomerSalesArea for sales org, channel, division
  • Addresses through to_BusinessPartnerAddress; partner functions in A_CustSalesPartnerFunc
  • Communication scenario SAP_COM_0008 in Cloud Public Edition
Core

Sales Order

API_SALES_ORDER_SRV · A_SalesOrder

Create and read sales orders with items, partners and pricing elements. The main path for won HubSpot deals.

  • Header: SoldToParty, SalesOrganization, TotalNetAmount
  • to_Item, to_Partner, to_PricingElement
  • Status fields for delivery, billing and credit check
Core

Billing Document

Billing Document API · A_BillingDocument

Invoices, credit memos and debit memos issued from S/4HANA, with partners (including payer) and items.

  • Read-only into HubSpot
  • Billing partners include payer and bill-to
  • Payment clearing status comes from finance; confirm the source in discovery
Core

Product master

API_PRODUCT_SRV · A_Product

Materials with descriptions, units and sales data per sales organization and distribution channel.

  • Feeds the HubSpot product library
  • Only products released for sale in the client's sales areas
  • Low change rate, daily sync
Enrichment

Pricing condition records

API_SLSPRICINGCONDITIONRECORD_SRV

Sales price conditions by condition type. Used to show list prices in HubSpot, not to recalculate SAP pricing.

  • List price per product and sales area
  • Customer-specific prices stay in SAP
  • The S/4HANA order is priced by its own pricing procedure
Enrichment

Sales Quotation

API_SALES_QUOTATION_SRV · A_SalesQuotation

SAP quotations for businesses whose official quote is issued from S/4HANA rather than from HubSpot.

  • Quote number and value on the HubSpot deal
  • Quotation-to-order reference
  • Off by default; choose one quoting system
Scope decision

Customer creation in SAP

Master data governance

When a HubSpot deal closes for a new company, someone must create the SAP customer. The client chooses whether the integration creates it through the API or sends a request to the master data team.

  • API creation needs grouping, role and sales area defaults
  • A request queue keeps SAP data governance in place
  • Decide before the build; it shapes the order flow
03 — Framework

How does the SAP S/4HANA HubSpot integration work?

HubSpot never calls S/4HANA directly. A CC-built integration layer reads changes from S/4HANA, matches them to HubSpot records, writes in batches, and sends won deals back as sales orders after validation.

SAP S/4HANA
Business Partner APIcustomers, addresses, sales areas
Product mastermaterials, sales data, list prices
Sales Order APIorders, items, partners, status
Billing Document APIinvoices and credit memos
CC integration layer
Secure connectioncommunication user or gateway path
Change readerdelta reads by last-change timestamp
Identity resolverBP number · domain · email
Order builderdeal → sales order, partner and sales area rules
HubSpot writerbatch upserts, error replay
HubSpot
Companies & contactsSAP customers and contact persons
Productsmaterials with SAP codes
Deals & line itemspipeline and order lines
Orders & invoicesSAP orders and billing documents
Lists, workflows & reportsaccount health, reorder, AR follow-up
S/4HANA → HubSpot (master data, orders, billing)HubSpot → S/4HANA (won deals as sales orders; new customer requests)
Principle

Each record has one owner

HubSpot owns prospects, contacts, deals and pre-sale quotes. S/4HANA owns the customer master once created, materials, prices, orders, billing and credit.

Principle

SAP prices the order

HubSpot line item prices are a guide. S/4HANA prices the order with its own pricing procedure, and the integration writes the SAP total back to the deal.

Principle

Write once, then confirm

Each HubSpot deal creates at most one SAP order. The SAP order number is stored on the deal, and any failure goes to a queue a person can replay.

04 — Process

What does SAP S/4HANA HubSpot integration setup involve?

Each phase ends on a gate the client signs off before the next begins. Master data goes live first, then orders, then billing.

1

Landscape & ownership

Confirm the deployment (Cloud Public, Private or on-premise), the sales areas in scope, and which system owns each record type. Decide how new SAP customers are created.

Gate to next phaseSigned ownership matrix and sales areas in scope
2

API access

Set up the communication user and arrangements in Cloud Public Edition, or activate the OData services and agree the network path with IT and Basis for other deployments.

Gate to next phaseTest calls succeed against the client's quality system
3

Matching & mapping rules

Agree how SAP business partners match HubSpot companies, how partner functions map, and which custom fields come across. Read the client's $metadata to confirm field names.

Gate to next phaseSigned mapping and match rules
4

HubSpot data model

Create the properties, product library settings, order and invoice pipelines, association labels and property groups in a HubSpot sandbox.

Gate to next phaseSchema approved and created in sandbox
5

Build & test

Build master data sync, then order write-back with validation, then billing reads. Test against the SAP quality system, never production.

Gate to next phaseTest orders created in SAP quality and visible in HubSpot
6

Backfill

Load customers, products and an agreed history of orders and invoices, then compute rollups once.

Gate to next phaseHubSpot totals reconcile to SAP reports within an agreed tolerance
7

Parallel run & launch

Run order write-back alongside the current process for two weeks, then switch on.

Gate to next phaseFive consecutive days with no unresolved sync errors
05 — Data mapping

What does the SAP S/4HANA HubSpot integration sync?

Field names come from SAP's published API data models. Custom fields (extension fields) and the exact services in the client's system are confirmed from its $metadata during discovery.

S/4HANA fieldHubSpot propertyObjectDirectionNotes
Business partner · customer master
BusinessPartners4_bp_numberCompanyS/4 → HSPrimary match key. Unique.
OrganizationBPName1nameCompany↔ BothSAP name wins once the customer exists in SAP.
Address (StreetName, CityName, PostalCode, Country)address, city, zip, countryCompanyS/4 → HSDefault address from to_BusinessPartnerAddress.
EmailAddress (contact person)emailContact↔ BothContact persons match on email. HubSpot keeps new contacts it creates.
SalesOrganization, DistributionChannel, Divisions4_sales_areaCompanyS/4 → HSFrom to_CustomerSalesArea. Multi-select if one customer has several.
Currency (sales area)s4_currencyCompanyS/4 → HSCustomer's order currency.
Customer payment termss4_payment_termsCompanyS/4 → HSFrom sales area data. Confirm field in discovery.
Ship-to / bill-to / payer partnersChild companies + association labelsCompanyS/4 → HSPartner functions become labeled associations to the sold-to company.
Products & prices
Producths_skuProductS/4 → HSSAP material number as SKU. Unique.
ProductDescriptionnameProductS/4 → HSDescription in the client's sales language.
BaseUnits4_base_unitProductS/4 → HSUnit of measure for line items.
ProductGroups4_product_groupProductS/4 → HSFor reporting and segments.
ConditionRateValue (list price)priceProductS/4 → HSFrom pricing condition records. Confirm condition type in discovery.
Deals → sales orders
SoldToPartys4_bp_number (company)DealHS → S/4Taken from the associated company.
SalesOrderType, SalesOrganization, DistributionChannel, OrganizationDivisions4_order_type, s4_sales_areaDealHS → S/4Defaults per pipeline, overridable by the rep.
PurchaseOrderByCustomers4_customer_poDealHS → S/4Customer PO number captured in HubSpot.
to_Item: Material, RequestedQuantityhs_sku, quantityLine itemHS → S/4One SAP item per HubSpot line item.
to_Partner: PartnerFunction ship-toShip-to association labelDealHS → S/4Ship-to selected on the deal; defaults from SAP if blank.
SalesOrders4_sales_orderDealS/4 → HSWritten back after SAP accepts the order.
TotalNetAmount, TransactionCurrencyamount, deal_currency_codeDealS/4 → HSSAP-priced total replaces the estimate.
Orders & billing
A_SalesOrder (header)Order recordOrderS/4 → HSAll SAP orders for synced customers, including those entered in SAP.
OverallDeliveryStatus, OverallOrdReltdBillgStatuss4_delivery_status, s4_billing_statusOrderS/4 → HSDrives service and follow-up workflows.
TotalCreditCheckStatuss4_credit_statusOrderS/4 → HSCredit blocks alert the account owner.
BillingDocument, BillingDocumentDateInvoice recordInvoiceS/4 → HSRead-only copy of SAP billing documents.
TotalNetAmount (billing)s4_billed_ytdCompanyS/4 → HSRolled up in the integration layer.
Open receivabless4_open_arCompanyS/4 → HSFrom finance data. Confirm the source API in discovery.
06 — Auth & API

How are authentication and API limits handled?

Values SAP does not publish are marked for confirmation. The client's deployment decides the connection method.

TopicS/4HANAHubSpot
Access modelCloud Public Edition: a communication system, communication user and one communication arrangement per scenario (Business Partner uses SAP_COM_0008). Private Edition and on-premise: OData services activated on the SAP Gateway.Self-serve in the client portal. Custom objects need an Enterprise hub; orders and invoices are standard objects.
InterfacesOData v2 and v4 REST services and SOAP services, catalogued on the SAP Business Accelerator Hub. Each system's $metadata lists its exact fields.REST APIs: CRM objects, associations, products, line items, orders, invoices, webhooks.
AuthenticationCommunication user with user and password or X.509 client certificate. OAuth 2.0 where the scenario supports it. Confirm in discovery.Private app access token or OAuth 2.0 public app, scoped per object.
NetworkCloud Public Edition is reachable over HTTPS. Private Edition and on-premise need a secure path agreed with IT (allowlisted connection or VPN).Public HTTPS endpoints.
Change detectionDelta reads by last-change timestamp (sales orders carry LastChangeDateTime). S/4HANA business events where the client's landscape publishes them.Webhooks on deal stage change trigger order write-back.
Rate limitsNot published. Confirm with SAP and the client's Basis team.Per-10-second burst and daily limits by subscription tier.
EnvironmentsWrite-back is built and tested against the SAP quality system first.HubSpot sandbox for build and test.
07 — Issues & opportunities

What should you plan for, and what does the integration unlock?

Severity reflects impact on the SOW, not technical difficulty alone.

Challenges to plan for

Connectivity differs by deploymentHigh

Cloud Public Edition, Private Edition and on-premise each connect differently. Make access a client-owned dependency in the SOW, with IT and Basis named.

Sales areas and partner functionsHigh

One SAP customer can sell through several sales areas and ship to many locations. Agree which sales areas are in scope and how ship-to, bill-to and payer appear in HubSpot before mapping starts.

New customer creationHigh

An order cannot be created for a customer SAP does not know. The client decides whether the integration creates business partners or routes a request to the master data team.

Pricing lives in SAPMedium

Condition-based pricing cannot be repeated in HubSpot. HubSpot shows list prices, and the SAP-priced total is written back to the deal after the order is created.

Custom fields and released APIsMedium

Client-specific fields must be added to the API as extension fields, and Cloud Public Edition exposes only released APIs. Budget a short discovery spike to read $metadata.

Volume and historyLow

Order and billing history can be large. HubSpot receives an agreed history window and rollups, not every line from every year.

Opportunities in HubSpot

Won deals become SAP ordersHigh value

Reps stop re-keying orders. The deal carries the SAP order number and the SAP-priced total, and errors land in a queue someone owns.

ERP facts on the accountHigh value

Orders, billed revenue and open receivables sit on the company record, so sales and service see the whole relationship in one place.

Reorder and lapse alertsHigh value

Customers who stop ordering, or order less than usual, enter HubSpot lists and tasks for the account owner.

Credit and delivery visibilityMedium value

Credit blocks and delivery status reach the account owner as tasks, so the customer hears from sales first.

Product library from SAPMedium value

HubSpot products match SAP materials, so quotes and line items use the same codes the ERP does.

Revenue reporting by sales areaMedium value

Pipeline and billed revenue meet in HubSpot dashboards, split the same way finance splits them.

Quote-to-cash flow

Who owns each step from quote to cash.

HubSpot runs the pipeline up to the signed deal. S/4HANA runs fulfillment and finance from the sales order on. The integration hands over at close and reports back at every step after.

  1. Quote in HubSpot with SAP products and list prices, or in S/4HANA when the client issues official quotes there.
  2. Deal won: the integration creates the SAP sales order for the sold-to customer and writes the order number back.
  3. S/4HANA prices, checks credit, delivers and bills. Status and billing documents flow to HubSpot.
  4. Billed revenue and open receivables roll up to the company for account reviews and renewals.
08 — Property schema

Which HubSpot properties does the integration create?

All custom properties use the s4_ prefix in an SAP S/4HANA property group. Rollups are calculated in the integration layer so every report agrees.

Internal nameLabelObjectTypeSource / logic
s4_bp_numberSAP Business PartnerCompanySingle-line textBusinessPartner; unique
s4_sales_areaSAP Sales AreaCompanyMultiple checkboxesSales org / channel / division combinations
s4_currencySAP Order CurrencyCompanySingle-line textSales area currency
s4_payment_termsSAP Payment TermsCompanyDropdownSales area payment terms
s4_billed_ytdBilled YTDCompanyNumber (currency)Sum of billing document net amounts
s4_open_arOpen ReceivablesCompanyNumber (currency)Open items from finance; source confirmed in discovery
s4_base_unitSAP Base UnitProductSingle-line textBaseUnit
s4_order_typeSAP Order TypeDealDropdownSalesOrderType default per pipeline
s4_customer_poCustomer PODealSingle-line textPurchaseOrderByCustomer
s4_sales_orderSAP Sales OrderDealSingle-line textSalesOrder returned on create
s4_delivery_statusSAP Delivery StatusOrderDropdownOverallDeliveryStatus
s4_credit_statusSAP Credit StatusOrderDropdownTotalCreditCheckStatus
09 — Scope builder

Interactive scope builder

Choose the modules 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.

Scope summary

0Fields
0Inbound
0Write-back
S/4HANA × HubSpot Integration Assessment · Designed by Campaign Creators, Elite HubSpot Solutions Partner

SAP S/4HANA HubSpot integration FAQ

Does SAP S/4HANA integrate with HubSpot?

Yes, through a custom integration. HubSpot does not publish its own SAP app, so Campaign Creators builds on the released OData and SOAP APIs that SAP catalogs for S/4HANA on the SAP Business Accelerator Hub, including Business Partner, Sales Order, Billing Document and Product master.

What data syncs between SAP S/4HANA and HubSpot?

S/4HANA business partners sync to HubSpot companies and contacts, and products with list prices sync to HubSpot products. Won HubSpot deals create S/4HANA sales orders. Order status, billing documents, billed revenue and open receivables are written back to HubSpot.

Does it work with S/4HANA Cloud and on-premise?

Yes, but access is set up differently. Cloud Public Edition exposes released APIs through a communication user and communication arrangements. Private Edition and on-premise systems need the OData services activated and a secure network path agreed with the client's IT and Basis teams.

What does setting up the SAP S/4HANA HubSpot integration involve?

Seven phases, each closed by a client sign-off: landscape and ownership, API access, matching and mapping rules, the HubSpot data model, build and test against the SAP quality system, backfill, and a two-week parallel run before order write-back is switched on.

How long does the integration take and what does it cost?

Timeline and cost depend on the S/4HANA deployment, the sales areas and partner functions in scope, custom fields and the history to load. Campaign Creators confirms these in discovery and provides a fixed scope before the build starts.