Skip to content
Accounting and finance

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

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

Keep the customer, invoice, and payment records that Pigment and Rillet 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 Data imports, Users and permissions, Applications, Metrics in Pigment with Invoice Payment, Charge, Reimbursement, Custom Field in Rillet 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

  • Push CRM pipeline data (deals, stages, amounts) into Pigment for revenue and capacity planning.
  • Export approved budgets and forecasts back to a warehouse or Postgres for downstream reporting.
  • Keep customers and invoices aligned between Rillet and a CRM so finance and sales work from the same account records.
  • Mirror journal entries and contract revenue data into a warehouse for board and ARR reporting.

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 Pigment and Rillet

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.

Pigment objects Rillet objects
Dimension lists Master data like accounts, products, or employees that metrics are sliced by Vendor Synced with incremental and full sync per the Stacksync docs.
Tables Row-based transactional data loaded into models from source systems Invoice Synced with incremental and full sync per the Stacksync docs.
Scenarios Versions such as budget, forecast, and actuals that give exported figures their context Credit Memo Synced with incremental and full sync per the Stacksync docs.
Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model Bill Synced with incremental and full sync per the Stacksync docs.
Users and permissions Access controls governing which model areas a sync can touch Journal Entry Synced with incremental and full sync per the Stacksync docs.
Applications Planning models organized by domain such as finance, sales, or workforce Invoice Payment Synced with incremental and full sync per the Stacksync docs.
What ships with Pigment ⇄ Rillet

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Pigment ⇄ Rillet sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Pigment and Rillet.

How the Pigment and Rillet connectors work

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

Rillet

Integration surface
REST API (OpenAPI-specified, with production and sandbox environments)
Authentication
API key generated in Rillet (Organization Setting -> API Access); uncheck Read Only for bidirectional sync, check Read Only for one-way sync
Change detection
Near real-time updates via change tracking; incremental sync per object, with delete detection (some objects checked every 1h or 4h)
Capabilities
read · write · CDC · webhooks
Rate limits
Subject to the platform's API rate limits.
Rillet setup guide
How it works

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

    Choose tables

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

Pigment and Rillet integration FAQ

SECURITY

Security teams love 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 386 integrations available for Pigment and Rillet.

Popular · 8 of 386
Coworkers laughing in front of a laptop in a casual office setting

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