Skip to content
ERP ⇄ Accounting and finance

Dynamics 365 Business Central to Ramp integration — real-time, two-way sync

Keep Dynamics 365 Business Central and Ramp in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Dynamics 365 Business Central and Ramp

Keep Ramp and Dynamics 365 Business Central agreeing on customers, invoices, and balances, whether they split the finance workload or one is replacing the other.

A dedicated finance tool and an ERP end up side by side for practical reasons: a subsidiary runs lighter software than headquarters, billing runs in a specialist system while the enterprise system holds the wider view, or the company is mid-migration and both are live. Whatever the split, the two systems describe overlapping customers and transactions, and that overlap drifts without a live connection.

Stacksync syncs Bills, Vendors, Funds (Spend Controls), General Ledger Accounts in Ramp with Sales Invoices, Purchase Orders, General Ledger Entries, Journals in Dynamics 365 Business Central in real time and in both directions. You decide which system wins on which field, and every change made in one is reflected in the other within seconds instead of at the next batch run.

Common use cases

  • 01 Read Reimbursements into a finance database for cross-entity expense reporting and reconciliation without manual CSV exports.
  • 02 Two-way sync Transactions and their accounting codings with a Postgres warehouse so finance analyzes spend in SQL and pushes GL categories and memos back to Ramp.
  • 03 Mirror items and inventory levels into external channels so stock data stays current outside the ERP.
  • 04 Replicate GL entries and dimensions into a SQL database for financial reporting without giving analysts ERP logins.

Common sync patterns

One customer and vendor master

Where both systems keep records of the same organizations, corrections made in either propagate to the other.

Subsidiary to headquarters

Where Ramp serves a business unit and Dynamics 365 Business Central is the group system, transactions and customer records roll up continuously, so consolidation starts from live data.

Where Ramp handles billing: invoices land in Dynamics 365 Business Central

Invoices and payment activity from the billing side post through to the enterprise system automatically.

What you can sync between Dynamics 365 Business Central and Ramp

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Dynamics 365 Business Central objects Ramp objects How this pairing syncs
Vendors Supplier master data synced with procurement and AP automation tools. Vendors Supplier records under the accounting namespace; uploaded and updated for AP matching and payments. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Customers Core master data synced with CRMs so sales and finance share one customer list. Transactions Card purchase records with merchant, amount, and state; read for spend/GL sync and written back via accounting codings and sync status. Customers is specific to Dynamics 365 Business Central and Transactions to Ramp — each maps to any object or custom field on the other side.
Items Product and inventory records aligned with e-commerce and warehouse systems. Cards Physical and virtual card records; created and managed through the API to provision or suspend cardholder spend. Items is specific to Dynamics 365 Business Central and Cards to Ramp — each maps to any object or custom field on the other side.
Sales Orders Order headers and lines created from external channels and read back for fulfillment status. Users Employee and cardholder records; invited, updated, and deactivated, commonly synced from an HRIS or identity provider. Sales Orders is specific to Dynamics 365 Business Central and Users to Ramp — each maps to any object or custom field on the other side.
Sales Invoices Billing documents synced to CRMs and payment platforms. Departments Org groupings for cost-center and GL allocation; pushed from an ERP/HRIS and referenced by cards and transactions. Sales Invoices is specific to Dynamics 365 Business Central and Departments to Ramp — each maps to any object or custom field on the other side.
Purchase Orders Procurement documents exchanged with supplier-facing systems. Reimbursements Out-of-pocket expense claims; read for reporting and marked ready-to-sync then synced to the ERP. Purchase Orders is specific to Dynamics 365 Business Central and Reimbursements to Ramp — each maps to any object or custom field on the other side.

How changes propagate between Dynamics 365 Business Central and Ramp

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Dynamics 365 Business Central Ramp Sub-second propagation

DetectionDynamics 365 Business Central notifies Stacksync of record changes through webhook events. API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime.

DeliveryEach detected change is written to Ramp through its API, with automatic retries and rate-limit backoff.

Ramp Dynamics 365 Business Central Sub-second propagation

DetectionRamp notifies Stacksync of record changes through webhook events. Signed webhooks (HMAC-SHA256 X-Ramp-Signature) for bill, transaction, reimbursement, vendor, and user events.

DeliveryEach detected change is written to Dynamics 365 Business Central through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Ramp: 200 requests per 10-second rolling window per source IP; exceeding it returns 429 Too Many Requests, and requests running over 60 seconds return 504. Results use keyset pagination (follow the page.next URL / start cursor); higher limits can be requested from support.
What ships with Dynamics 365 Business Central ⇄ Ramp

Connect Dynamics 365 Business Central and Ramp for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dynamics 365 Business Central–Ramp connection.

Real-time

Two-way sync

Changes in Dynamics 365 Business Central or Ramp instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Dynamics 365 Business Central or Ramp data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Dynamics 365 Business Central or Ramp record.

Observability

Monitoring

Track your Dynamics 365 Business Central ⇄ Ramp sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Dynamics 365 Business Central and Ramp.

How the Dynamics 365 Business Central and Ramp connectors work

Dynamics 365 Business Central

Integration surface
REST API built on OData v4 (standard API v2.0), extensible with custom API pages in AL
Authentication
OAuth 2.0 via Microsoft Entra ID
Change detection
API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime
Capabilities
read · write · webhooks

Ramp

Integration surface
REST API (Developer API v1)
Authentication
OAuth 2.0: exchange client_id/client_secret (HTTP Basic) at api.ramp.com/developer/v1/token for scoped bearer tokens; client_credentials grant for server-to-server and authorization_code for user-delegated access; scopes follow resource:permission (e.g. transactions:read, bills:write, accounting:write).
Change detection
Signed webhooks (HMAC-SHA256 X-Ramp-Signature) for bill, transaction, reimbursement, vendor, and user events; otherwise poll incrementally (synced_after on transactions, from_created_at on bills) with keyset pagination, or read the audit-logs/events feed.
Capabilities
read · write · webhooks
Rate limits
200 requests per 10-second rolling window per source IP; exceeding it returns 429 Too Many Requests, and requests running over 60 seconds return 504. Results use keyset pagination (follow the page.next URL / start cursor); higher limits can be requested from support.
Ramp setup guide
How it works

How to connect Dynamics 365 Business Central to Ramp — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Dynamics 365 Business Central and Ramp with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Dynamics 365 Business Central connected
    Ramp connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Dynamics 365 Business Central and Ramp objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Dynamics 365 Business Central ⇄ Ramp
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Dynamics 365 Business Central Ramp
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Dynamics 365 Business Central and Ramp integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 504 integrations available for Dynamics 365 Business Central and Ramp.

Popular · 8 of 504
All Dynamics 365 Business Central integrations All Ramp integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own