Oracle NetSuite and Ramp integration

What moves between them

The main flow runs from Ramp into Oracle NetSuite. When a bill is created or approved in Ramp, ml-connector reads the bill details and associated vendor information, maps cost centers and GL accounts to matching NetSuite dimensions, and posts a transaction into NetSuite's general ledger. Corporate card transactions cleared in Ramp also flow into NetSuite with the same GL mapping. Reference data such as GL accounts and departments are read from both systems to ensure valid mapping. Purchase orders can flow from NetSuite to Ramp as reference records. The sync runs on real-time webhooks from Ramp, with fallback polling if webhooks are missed.

How ml-connector handles it

ml-connector stores OAuth credentials encrypted for both systems. On the Ramp side it registers a webhook endpoint, validates incoming HMAC-SHA256 signatures before processing, and retrieves bill and transaction details via REST calls. It maps Ramp vendors to NetSuite vendor records, and maps Ramp cost centers and project codes to matching NetSuite dimensions using configuration rules. On the NetSuite side it uses OAuth 2.0 Client Credentials to obtain tokens (valid 60 minutes) and posts vendor bills as NetSuite transaction records with correct GL account and cost center associations. Ramp billId and transactionId are stored in NetSuite custom fields for deduplication and audit trail linkage. If a Ramp webhook is missed, ml-connector can poll NetSuite and Ramp separately to detect gaps. NetSuite Event Subscriptions require IP allowlist validation rather than HMAC, so ml-connector is registered with a static IP in NetSuite's webhook settings. Purchase orders created in NetSuite can be pushed to Ramp as reference records to prevent duplicate PO creation. Every record carries source IDs and timestamps for full audit trail and replay capability.

A real-world example

A mid-sized SaaS company runs Oracle NetSuite for consolidated accounting across three business units and uses Ramp for corporate spend management, including corporate cards, vendor bill pay, and travel reimbursements. Before the integration, the accounting team received daily bill and expense reports from Ramp and manually entered them into NetSuite, spending 4 to 6 hours per week on data entry. Because Ramp and NetSuite use different vendor master records, duplicate vendors would sometimes be created. With Oracle NetSuite and Ramp connected, approved bills and card transactions post directly into NetSuite's general ledger mapped to the correct cost center and GL account for each business unit. Vendors are resolved to the correct NetSuite records, duplicates are prevented, and month-end close starts with expenses already posted and reconciled.

What you can do

• •Sync Ramp bills and corporate card transactions into Oracle NetSuite's general ledger with automatic GL account and cost center mapping.
• •Map Ramp vendors to NetSuite vendor records and prevent duplicate vendor creation across both systems.
• •Validate Ramp webhook signatures with HMAC-SHA256 and post only verified transactions to NetSuite.
• •Use OAuth 2.0 on both sides to authenticate, with automatic token refresh and expiry management.
• •Track every bill and transaction with full audit trail, source IDs, and replay capability if a downstream call fails.

Questions

Which direction does data move between Oracle NetSuite and Ramp?

The main flow is from Ramp into Oracle NetSuite. Bills and corporate card transactions from Ramp post into NetSuite's general ledger mapped to the correct cost centers and GL accounts. Purchase orders can also flow from NetSuite to Ramp as reference records. GL accounts and departments are read-only in both directions to enable mapping without overwriting existing data.

How does ml-connector validate Ramp webhooks if NetSuite does not support HMAC?

ml-connector registers with Ramp and validates incoming webhook signatures using HMAC-SHA256 before processing any bill or transaction. On the NetSuite side, ml-connector is registered as a webhook consumer with a static IP address in NetSuite's event subscription settings to authenticate calls from ml-connector. Both validations happen before any data enters the accounting records.

What happens if a Ramp bill is created but the webhook is missed or delayed?

ml-connector tracks processed billIds and transactionIds in NetSuite custom fields to detect gaps. If a webhook is missed, ml-connector can poll both Ramp and NetSuite separately to identify unprocessed bills, retrieve their current state, and post them into NetSuite. Every record carries a timestamp and source ID so replay is safe and deduplication is enforced.