Skip to content
Accounting and finance ⇄ ERP

Navan to SAP Business ByDesign integration — real-time, two-way sync

Keep Navan and SAP Business ByDesign 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 Navan and SAP Business ByDesign

Keep Navan and SAP Business ByDesign 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 Receipts, Repayments, Fees, and Adjustments, Users, Card Transactions in Navan with Customer Invoices, Materials / Products, Purchase Orders, Opportunities in SAP Business ByDesign 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 Pull Bookings by date range into a database to reconcile travel reservations against Card Transactions and monitor travel-policy spend.
  • 02 Sync Users and department mappings from an HRIS into reporting tables so every transaction is attributed to a cost center and manager.
  • 03 Sync ByDesign accounts and contacts with an external CRM so sales works outside the ERP while finance keeps the master record.
  • 04 Create sales orders in ByDesign from e-commerce or CPQ systems and sync order and delivery status back.

Common sync patterns

Migration without a hard cutover

When one system is replacing the other, run both in parallel with records matching until the switch is complete.

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 Navan serves a business unit and SAP Business ByDesign is the group system, transactions and customer records roll up continuously, so consolidation starts from live data.

What you can sync between Navan and SAP Business ByDesign

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.

Navan objects SAP Business ByDesign objects How this pairing syncs
Users Employee and cardholder records referenced by every transaction; usually provisioned from an HRIS and used to map spend to people and departments. Contacts Person records linked to accounts, aligned with CRM contact objects. Users is specific to Navan and Contacts to SAP Business ByDesign — each maps to any object or custom field on the other side.
Card Transactions Navan physical and virtual card spend; read via GET, then GL codes, cost centers, and ERP sync status are written back per transaction through the transaction update endpoint. Sales Orders Order documents created from external channels and read for status. Card Transactions is specific to Navan and Sales Orders to SAP Business ByDesign — each maps to any object or custom field on the other side.
Connect Transactions External and personal card feed matched into Navan; retrieved read-only and coded with custom-field values through the transaction update endpoint. Customer Invoices Billing documents synced outward for collections and CRM visibility. Connect Transactions is specific to Navan and Customer Invoices to SAP Business ByDesign — each maps to any object or custom field on the other side.
Manual Transactions Out-of-pocket reimbursements and payroll submissions; synced for approval and reimbursement, then GL-coded back into Navan. Materials / Products Item master data aligned with e-commerce and inventory systems. Manual Transactions is specific to Navan and Materials / Products to SAP Business ByDesign — each maps to any object or custom field on the other side.
Bookings Flight, hotel, rail, and car reservations from the Booking API; pulled read-only by createdFrom/createdTo date range for trip and travel-spend reporting. Purchase Orders Procurement documents exchanged with supplier systems. Bookings is specific to Navan and Purchase Orders to SAP Business ByDesign — each maps to any object or custom field on the other side.
Custom Fields Company metadata such as cost centers and project codes; discovered via GET and their option lists created or updated via async POST. Opportunities Built-in CRM records synced with external sales tools when both are in use. Custom Fields is specific to Navan and Opportunities to SAP Business ByDesign — each maps to any object or custom field on the other side.

How changes propagate between Navan and SAP Business ByDesign

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.

Navan SAP Business ByDesign Sub-second propagation

DetectionNavan notifies Stacksync of record changes through webhook events. Navan's Expense API supports webhooks for transaction and expense events.

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

SAP Business ByDesign Navan Interval-based propagation

DetectionStacksync polls SAP Business ByDesign for changes on an incremental schedule, reading only records changed since the previous pass. Polling on last-changed timestamps.

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

Rate-limit considerations

  • Navan: Requests are throttled with HTTP 429 and Navan recommends retrying with exponential backoff; the Expense/Public API must first be enabled per account by Navan.
What ships with Navan ⇄ SAP Business ByDesign

Connect Navan and SAP Business ByDesign for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Navan–SAP Business ByDesign connection.

Real-time

Two-way sync

Changes in Navan or SAP Business ByDesign instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Navan or SAP Business ByDesign 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 Navan or SAP Business ByDesign record.

Observability

Monitoring

Track your Navan ⇄ SAP Business ByDesign sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Navan and SAP Business ByDesign.

How the Navan and SAP Business ByDesign connectors work

Navan

Integration surface
REST (Expense API and Booking API)
Authentication
OAuth 2.0 client-credentials flow; an admin creates a client_id and client_secret under Settings > Integrations and exchanges them at Navan's OAuth token endpoint for a short-lived bearer token that is refreshed on expiry (separate US and EU regional hosts)
Change detection
Navan's Expense API supports webhooks for transaction and expense events; sync engines also poll GET endpoints with date-range and updatedAt filters (createdFrom/createdTo for bookings) to backfill history and reconcile. There is no database-level CDC.
Capabilities
read · write · webhooks
Rate limits
Requests are throttled with HTTP 429 and Navan recommends retrying with exponential backoff; the Expense/Public API must first be enabled per account by Navan.

SAP Business ByDesign

Integration surface
SOAP web services plus OData services for analytical and custom data access
Authentication
Basic authentication over TLS for service users; OAuth-based options exist for certain scenarios
Change detection
Polling on last-changed timestamps; the platform does not offer a general webhook surface
Capabilities
read · write
How it works

How to connect Navan to SAP Business ByDesign — 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 Navan and SAP Business ByDesign 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
    Navan connected
    SAP Business ByDesign connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Navan and SAP Business ByDesign 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 · Navan ⇄ SAP Business ByDesign
    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
    Navan SAP Business ByDesign
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Navan and SAP Business ByDesign 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.

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:

Related integrations

Every pair below is a real-time, two-way sync. Search all 511 integrations available for Navan and SAP Business ByDesign.

Popular · 7 of 511
Coworkers laughing in front of a laptop in a casual office setting

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