Skip to content
Accounting and finance

Navan to Pigment integration — real-time, two-way sync

Keep Navan and Pigment 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 Pigment

Keep the customer, invoice, and payment records that Navan and Pigment share consistent in real time, whether the two systems split your finance stack or one is replacing the other.

Two finance systems in one company usually means one of two setups. Either the systems divide the work, with one issuing invoices or serving a business unit while the other holds the books, or one is on its way out and both must stay accurate during the transition. In both cases, the customer, invoice, and payment records the two systems share start to drift the moment updates are keyed twice or moved by hand.

Stacksync syncs Manual Transactions, Bookings, Custom Fields, Receipts in Navan with Data imports, Users and permissions, Applications, Metrics in Pigment bi-directionally and in real time. A record created or corrected in either system appears in the other within seconds, with field-level mapping and conflict resolution in place of CSV exports and nightly batch jobs.

That matters most at close. When both systems agree on who was billed, what was paid, and what is outstanding, reconciliation stops being a hunt for which copy of the truth is current.

Common use cases

  • 01 Push coded expense transactions into an accounting system, then set their ERP sync status in Navan so the same records are not exported twice.
  • 02 Pull Bookings by date range into a database to reconcile travel reservations against Card Transactions and monitor travel-policy spend.
  • 03 Export approved budgets and forecasts back to a warehouse or Postgres for downstream reporting.
  • 04 Keep dimension lists such as departments and cost centers consistent with master data in the ERP.

Common sync patterns

Parallel run during a migration

When one system is replacing the other, keep both live and matching through the cutover, so no transaction falls between the last export and go-live.

One customer master

A customer's name, billing details, or payment terms corrected in either system update the other immediately, so the next invoice always uses current information.

Payment status everywhere

A payment applied in one system updates the matching invoice in the other, so no one chases a balance that was already settled.

What you can sync between Navan and Pigment

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 Pigment objects How this pairing syncs
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. Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model Bookings is specific to Navan and Data imports to Pigment — 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. Users and permissions Access controls governing which model areas a sync can touch Custom Fields is specific to Navan and Users and permissions to Pigment — 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. Applications Planning models organized by domain such as finance, sales, or workforce Receipts is specific to Navan and Applications to Pigment — each maps to any object or custom field on the other side.
Repayments, Fees, and Adjustments Money-movement records including repayments, FX and platform fees, and credit or debit memos; read-only for reconciliation ledgers. Metrics Multidimensional values holding plans and actuals; the main target for inbound data Repayments, Fees, and Adjustments is specific to Navan and Metrics to Pigment — each maps to any object or custom field on the other side.
Users Employee and cardholder records referenced by every transaction; usually provisioned from an HRIS and used to map spend to people and departments. Dimension lists Master data like accounts, products, or employees that metrics are sliced by Users is specific to Navan and Dimension lists to Pigment — 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. Tables Row-based transactional data loaded into models from source systems Card Transactions is specific to Navan and Tables to Pigment — each maps to any object or custom field on the other side.

How changes propagate between Navan and Pigment

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 Pigment 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 Pigment through its API, with automatic retries and rate-limit backoff.

Pigment Navan Interval-based propagation

DetectionStacksync polls Pigment for changes on an incremental schedule, reading only records changed since the previous pass. No change feed.

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.
  • Pigment: Subject to the platform's API rate limits.
What ships with Navan ⇄ Pigment

Connect Navan and Pigment for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Navan ⇄ Pigment 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 Pigment.

How the Navan and Pigment 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.

Pigment

Integration surface
REST-based import and export API
Authentication
API keys, issued separately for import and export
Change detection
no change feed; syncs run scheduled imports and exports
Capabilities
read · write
Rate limits
subject to the platform's API rate limits
How it works

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

    Choose tables

    Pick the Navan and Pigment 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 ⇄ Pigment
    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 Pigment
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Navan and Pigment 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 406 integrations available for Navan and Pigment.

Popular · 7 of 406
All Navan integrations All Pigment 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