How Oracle Fusion Cloud ERP customers, items, sales orders, receivables invoices and receipts can reach HubSpot, and how won HubSpot deals can become Oracle sales orders, using the REST APIs, SOAP services, file-based import and BI Publisher reports Oracle publishes.
Oracle Fusion Cloud ERP runs order-to-cash and the books. HubSpot runs the customer relationship and the sales pipeline. The integration lets each system do its job and puts the ERP facts sales needs on the HubSpot record.
Public documentation. The client's own admin issues credentials, with no vendor approval needed.
Open API. The REST APIs are documented publicly. The client's security administrator creates the integration user, job roles and data access.
Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.
Oracle publishes a REST resource for each object this integration needs, so HubSpot can see every account, order, invoice and receipt while Oracle stays the system of record for finance.
Campaign Creators assessment
Oracle documents REST APIs for Fusion Cloud Financials (receivables invoices, standard receipts, customer account activity) and for Order Management (sales orders through the order hub), plus Trading Community resources for customer data and the Items resource for the product master. SOAP services, file-based data import (FBDI) and BI Publisher reports cover bulk loads and large extracts. HubSpot does not publish its own Oracle ERP app, so this is a custom build on those APIs. Two things set the pace: Oracle's enterprise structures (business units, legal entities and ledgers, each with its own currency and security), and Trading Community's three layers of customer data (party, customer account and account site).
Ratings are CC judgments from Oracle's public documentation. The client's modules, business units, flexfields and limits are confirmed during discovery.
Sales orders, receivables invoices and receipts each have a REST resource with a published schema. Records carry a LastUpdateDate, so changes can be read in small batches.
Every order and invoice belongs to a business unit and a legal entity, and one customer can have several accounts and many bill-to and ship-to sites. HubSpot needs clear rules for which of these become companies.
The integration runs as an Oracle user with job roles and data access for each business unit in scope. The client's security administrator sets this up before any build.
Seven Oracle surfaces matter to HubSpot. Four carry the integration, two support it, and one is a scope decision the client makes early.
Oracle holds customers in three layers: the party (the organization), its customer accounts, and the account sites that carry bill-to and ship-to purposes.
hubOrganizations with Addresses, Contact Points and Source System References child resourcesPartyNumber identifies the organizationCreate and read sales orders with bill-to and ship-to customers, lines, holds and totals. The main path for won HubSpot deals.
SourceTransactionSystem, SourceTransactionNumber and BusinessUnitIdOrderNumber, StatusCode and LastUpdateDatebillToCustomer, shipToCustomer, lines, totalsInvoices, with bill-to customer, business unit, legal entity, currency, due date and balance.
TransactionNumber, DueDate, InvoiceBalanceAmountBillToCustomerNumber links each invoice to a customer accountThe item master, read from the master organization, with description, unit of measure and status.
ItemNumber, ItemDescription, PrimaryUOMValueItemStatusValue filters to active itemsPayments received against each customer account, used for payment history and open balance on the HubSpot company.
ReceiptNumber, ReceiptDate, Amount, UnappliedAmountFile-based data import loads large volumes through Oracle's import processes, and BI Publisher reports extract large data sets on a schedule.
importBulkData operationThe client decides which business units are in scope, how they appear in HubSpot, and which currency each one reports in.
HubSpot never calls Oracle directly. A CC-built integration layer reads changes from Oracle, matches them to HubSpot records, writes in batches, and sends won deals back as sales orders after validation.
HubSpot owns prospects, contacts, deals and pre-sale quotes. Oracle owns customer accounts once created, items, prices, orders, invoices and receipts.
HubSpot line item prices are a guide. Oracle prices the order with its own pricing setup, and the integration writes the Oracle total back to the deal.
HubSpot is registered as a source system, and the deal ID is the source order number, so each deal creates at most one Oracle order. Failures go to a queue a person can replay.
Each phase ends on a gate the client signs off before the next begins. Customer and item data goes live first, then orders, then receivables.
Confirm which Oracle modules the client runs (Receivables, Order Management, Pricing), the business units in scope, and which system owns each record type. Decide how new Oracle customers are created.
The client's security administrator creates the integration user, assigns job roles and business unit data access, and sets up OAuth in the identity domain if used.
Agree how parties and customer accounts match HubSpot companies, how bill-to and ship-to sites map, and which descriptive flexfields come across. Read each resource's metadata to confirm field names.
Create the properties, product library settings, order and invoice pipelines, association labels and property groups in a HubSpot sandbox.
Build customer and item sync, then order write-back with validation, then receivables reads. Test against the Oracle test environment, never production.
Load customers, items and an agreed history of orders, invoices and receipts, using BI Publisher extracts where volume is high, then compute rollups once.
Run order write-back alongside the current process for two weeks, then switch on.
Field names come from Oracle's published REST schemas. Where a name is described rather than quoted, the exact attribute and any flexfields are confirmed from the client's resource metadata during discovery.
| Oracle ERP field | HubSpot property | Object | Direction | Notes |
|---|---|---|---|---|
| Customers · Trading Community | ||||
| PartyNumber | ora_party_number | Company | ORA → HS | Primary match key for the organization. Unique. |
| Organization name (party) | name | Company | ↔ Both | Oracle name wins once the customer exists in Oracle. |
| Addresses (child resource) | address, city, zip, country | Company | ORA → HS | Identifying address of the party. |
| Customer account number | ora_account_number | Company | ORA → HS | Matches BillToCustomerNumber on invoices. Multiple accounts are stored as a list. |
| Bill-to and ship-to account sites | Child companies + association labels | Company | ORA → HS | Site purposes become labeled associations to the parent company. |
| Contact Points (email, phone) | email, phone | Contact | ↔ Both | Contacts match on email. HubSpot keeps the contacts it creates. |
| Source System References | HubSpot company record ID | Company | HS → ORA | Stored in Oracle so each system can find the other's record. |
| Items & prices | ||||
| ItemNumber | hs_sku | Product | ORA → HS | Oracle item number as SKU. Unique. |
| ItemDescription | name, description | Product | ORA → HS | From the master organization. |
| PrimaryUOMValue | ora_uom | Product | ORA → HS | Unit of measure for line items. |
| ItemStatusValue | Sync filter | Product | ORA → HS | Only active, sellable items sync. |
| List price (price list) | price | Product | ORA → HS | From the client's price list. Confirm the pricing resource in discovery. |
| Deals → sales orders | ||||
| SourceTransactionSystem, SourceTransactionNumber, SourceTransactionId | Deal record ID | Deal | HS → ORA | HubSpot as a registered source system. Makes the write idempotent. |
| BusinessUnitId / BusinessUnitName | ora_business_unit | Deal | HS → ORA | Default per pipeline, overridable by the rep. |
| BuyingPartyNumber | ora_party_number (company) | Deal | HS → ORA | Taken from the associated company. |
| billToCustomer, shipToCustomer | Bill-to and ship-to association labels | Deal | HS → ORA | Sites selected on the deal; defaults from Oracle if blank. |
| TransactionalCurrencyCode | deal_currency_code | Deal | HS → ORA | Deal currency. |
| CustomerPONumber | ora_customer_po | Deal | HS → ORA | Customer PO captured in HubSpot. |
| lines (item, quantity, unit) | hs_sku, quantity | Line item | HS → ORA | One Oracle line per HubSpot line item. Line attribute names confirmed in discovery. |
| OrderNumber | ora_order_number | Deal | ORA → HS | Written back after Oracle accepts the order. |
| Orders, invoices & receipts | ||||
| Sales order header (OrderNumber, Status) | Order record, ora_order_status | Order | ORA → HS | All Oracle orders for synced customers, including those entered in Oracle. |
| totals (child resource) | Order total, amount | Order, Deal | ORA → HS | Oracle-priced total replaces the deal estimate. |
| TransactionNumber, TransactionDate, DueDate | Invoice record | Invoice | ORA → HS | Read-only copy of the Oracle invoice. |
| EnteredAmount, InvoiceBalanceAmount, InvoiceCurrencyCode | Invoice amount and balance | Invoice | ORA → HS | Balance drives collections follow-up. |
| InvoiceStatus, PaymentTerms | ora_invoice_status, payment terms | Invoice | ORA → HS | Status as Oracle reports it. |
| BusinessUnit, LegalEntityIdentifier | ora_business_unit, ora_legal_entity | Invoice | ORA → HS | For reporting by business unit and legal entity. |
| ReceiptNumber, ReceiptDate, Amount | ora_last_receipt_date | Company | ORA → HS | From standard receipts per customer account. |
| Open receivables | ora_open_ar | Company | ORA → HS | Sum of InvoiceBalanceAmount on open invoices, rolled up in the integration layer. |
| Billed revenue | ora_billed_ytd | Company | ORA → HS | Sum of invoice amounts in the fiscal year, in the reporting currency. |
Values Oracle does not publish are marked for confirmation. The client's security administrator controls what the integration user can see.
| Topic | Oracle ERP | HubSpot |
|---|---|---|
| Access model | An Oracle user for the integration, with job roles for each resource and data access for each business unit in scope. Set up by the client's security administrator. | Self-serve in the client portal. Custom objects need an Enterprise hub; orders and invoices are standard objects. |
| Interfaces | REST APIs for Financials and Order Management (fscmRestApi) and for Trading Community data (crmRestApi). SOAP services, FBDI imports and BI Publisher reports for bulk work. | REST APIs: CRM objects, associations, products, line items, orders, invoices, webhooks. |
| Authentication | Basic authentication over HTTPS, or OAuth 2.0 through the OCI IAM identity domain. Oracle lists JWT user assertion and authorization code grants for Fusion Applications. Confirm the client's standard. | Private app access token or OAuth 2.0 public app, scoped per object. |
| Change detection | Delta reads filtered on LastUpdateDate through the REST q parameter. Scheduled BI Publisher extracts for large sets. | Webhooks on deal stage change trigger order write-back. |
| Custom fields | Descriptive flexfields are exposed as child resources on REST objects (for example, invoice and invoice line flexfields). | Custom properties in a dedicated property group. |
| Rate limits | Not published. Confirm with Oracle. | Per-10-second burst and daily limits by subscription tier. |
| Environments | Write-back is built and tested against the client's Oracle test environment first. | HubSpot sandbox for build and test. |
Severity reflects impact on the SOW, not technical difficulty alone.
A party can hold several customer accounts, and each account many sites. Agree which layer becomes the HubSpot company and how sites appear before mapping starts.
Some Oracle ERP clients bill from Receivables or Projects without Order Management. Confirm the module list early: won deals then create a receivables invoice or a request to finance instead of a sales order.
An order cannot be created for a customer Oracle does not know. The client decides whether the integration creates the party, account and site, or routes a request to the team that owns customer data.
The integration user only sees data for the business units it is granted. Make role setup a client-owned dependency in the SOW, with the security administrator named.
HubSpot shows list prices. Oracle prices the order, and the Oracle total is written back to the deal after the order is created.
Invoice and receipt history can be large. HubSpot receives an agreed history window and rollups, loaded through BI Publisher extracts where REST paging is slow.
Reps stop re-keying orders. The deal carries the Oracle order number and the Oracle-priced total, and errors land in a queue someone owns.
Open balance, overdue invoices and last payment sit on the company record, so sales and service see the whole relationship before they call.
Overdue invoices create tasks for the account owner, so the customer hears from someone they know before the account goes on hold.
Customers who stop ordering, or order less than usual, enter HubSpot lists and tasks for the account owner.
HubSpot products match Oracle items, so quotes and line items use the same numbers the ERP does.
Pipeline and billed revenue meet in HubSpot dashboards, split by business unit and legal entity the way finance splits them.
HubSpot runs the pipeline up to the signed deal. Oracle runs fulfillment and finance from the sales order on. The integration hands over at close and reports back at every step after.
All custom properties use the ora_ prefix in an Oracle ERP property group. Rollups are calculated in the integration layer so every report agrees.
| Internal name | Label | Object | Type | Source / logic |
|---|---|---|---|---|
| ora_party_number | Oracle Party Number | Company | Single-line text | PartyNumber; unique |
| ora_account_number | Oracle Customer Account(s) | Company | Multi-line text | Customer account numbers for the party |
| ora_open_ar | Open Receivables | Company | Number (currency) | Sum of InvoiceBalanceAmount on open invoices |
| ora_billed_ytd | Billed This Fiscal Year | Company | Number (currency) | Sum of invoice amounts in the fiscal year |
| ora_last_receipt_date | Last Payment Received | Company | Date picker | Latest ReceiptDate |
| ora_uom | Oracle Unit of Measure | Product | Single-line text | PrimaryUOMValue |
| ora_business_unit | Oracle Business Unit | Deal | Dropdown | Default per pipeline; sent as BusinessUnitName |
| ora_customer_po | Customer PO | Deal | Single-line text | CustomerPONumber |
| ora_order_number | Oracle Sales Order | Deal | Single-line text | OrderNumber returned on create |
| ora_order_status | Oracle Order Status | Order | Dropdown | StatusCode |
| ora_invoice_status | Oracle Invoice Status | Invoice | Dropdown | InvoiceStatus |
| ora_legal_entity | Oracle Legal Entity | Invoice | Single-line text | LegalEntityIdentifier |
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.
Based on public documentation. Each item marked for confirmation is verified against the client's Oracle environment and with Oracle during discovery.
Yes, through a custom integration. HubSpot does not publish its own Oracle ERP app, so Campaign Creators builds on the REST APIs, SOAP services, file-based data import (FBDI) and BI Publisher reports that Oracle documents for Fusion Cloud Financials, Order Management and Trading Community customer data.
Oracle customers (parties, customer accounts and bill-to and ship-to sites) sync to HubSpot companies and contacts, and Oracle items sync to HubSpot products. Won HubSpot deals create Oracle sales orders. Order status, receivables invoices, receipts, open receivables and billed revenue are written back to HubSpot.
HubSpot owns the pipeline up to the signed deal. Oracle owns pricing, fulfillment, invoicing and the books from the sales order on. Oracle's customer name wins once a customer exists in Oracle, and the Oracle-priced order total replaces the deal estimate.
Seven phases, each closed by a client sign-off: modules and ownership, access and security (an integration user with job roles and business unit data access), matching and mapping rules, the HubSpot data model, build and test against Oracle's test environment, backfill, and a two-week parallel run before order write-back is switched on.
Timeline and cost depend on the Oracle modules, business units, customer structure and history in scope. Campaign Creators confirms these in discovery and provides a fixed scope before the build starts.