Two-way sync
Changes in Navan or Sage 100 instantly reflect in both systems. No stale data, no manual imports.
Keep Navan and Sage 100 in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
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 Custom Fields, Receipts, Repayments, Fees, and Adjustments, Users in Navan with Customers, Vendors, Inventory Items, Sales Orders in Sage 100 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.
Where Navan serves a business unit and Sage 100 is the group system, transactions and customer records roll up continuously, so consolidation starts from live data.
Invoices and payment activity from the billing side post through to the enterprise system automatically.
When one system is replacing the other, run both in parallel with records matching until the switch is complete.
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 | Sage 100 objects | How this pairing syncs | |
|---|---|---|---|
| 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. | AR Invoices Billing documents synced outward for payment status and revenue reporting. | Card Transactions is specific to Navan and AR Invoices to Sage 100 — 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. | Purchase Orders Procurement documents read for spend and receiving workflows. | Connect Transactions is specific to Navan and Purchase Orders to Sage 100 — 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. | GL Accounts Chart of accounts read for mapping transactions in finance integrations. | Manual Transactions is specific to Navan and GL Accounts to Sage 100 — 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. | Journal Entries Posted GL activity replicated to warehouses for FP&A. | Bookings is specific to Navan and Journal Entries to Sage 100 — 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. | Customers AR customer master records synced to CRMs for account and credit visibility. | Custom Fields is specific to Navan and Customers to Sage 100 — each maps to any object or custom field on the other side. | |
| Receipts Receipt images tied to each transaction; fetched read-only through presigned URLs for archival in a warehouse or document store. | Vendors AP vendor master records synced with procurement and payment tools. | Receipts is specific to Navan and Vendors to Sage 100 — each maps to any object or custom field on the other side. |
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.
DetectionNavan notifies Stacksync of record changes through webhook events. Navan's Expense API supports webhooks for transaction and expense events.
DeliveryEach detected change is applied to Sage 100 as a row-level write, with types converted between the two schemas.
DetectionStacksync polls Sage 100 for changes on an incremental schedule, reading only records changed since the previous pass. Scheduled polling.
DeliveryEach detected change is written to Navan through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Navan–Sage 100 connection.
Changes in Navan or Sage 100 instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Navan or Sage 100 data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Navan or Sage 100 record.
Track your Navan ⇄ Sage 100 sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Navan and Sage 100.
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.
Authenticate Navan and Sage 100 with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Navan and Sage 100 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 502 integrations available for Navan and Sage 100.