Skip to content
Database / Accounting and finance · Two-way sync platform

PostgreSQL and Rillet integration — two-way sync

Keep supported PostgreSQL and Rillet records aligned with two-way sync. Give each team access to current data while controlling which system can update each field.

  • Field mappings and sync direction under your control
  • Inspect and resolve record errors in one dashboard
Two-way sync for supported objects
stacksync.com
PostgreSQL
Rillet
Explore record coverage

Built for teams where self-serve, reliability and scale matter

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

Example workflow

Customer reporting workflow

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

Starting eventA change involving the proposed customer table in PostgreSQL or Rillet Customer needs a defined result in the other system.

  1. Start with the proposed customer table in PostgreSQL and Rillet Customer. Use the record-matching and field-ownership rules from your mapping worksheet.

  2. Resolve person or company type, legal entity, business role, and any billing account before transactions.

  3. Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

What to verifyTest an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.

Review records and field ownership

Mapping essentials

Records and field ownership

Match records by stable IDs and assign an owner for each field. The record notes identify the coverage to check.

Download the mapping worksheet

CSV · No email required

Example record relationships between PostgreSQL and Rillet
PostgreSQL recordRillet recordRecord matchingField ownership
Proposed customer tableProposed table; choose its name and schema.Reporting datasetCustomerDocumented record: Incremental: ; historical: ; delete detection:Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient.Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company.
Proposed customer invoice tableProposed table; choose its name and schema.Reporting datasetInvoiceDocumented record: Incremental: ; historical: ; delete detection:Retain the invoice ID, issuer/legal entity, and original order reference; invoice numbers alone may overlap.The financial system owns posting and accounting treatment. A posted invoice may need a credit or adjustment process instead of an overwrite.
Proposed supplier bill tableProposed table; choose its name and schema.Reporting datasetBillDocumented record: Incremental: ; historical: ; delete detection:Retain the supplier-bill ID, supplier, legal entity, and document reference; distinguish it from a customer invoice.Accounts payable owns approval and posting; a supplier bill is not an accounts-receivable invoice.

Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.

Why teams connect PostgreSQL and Rillet

Put your PostgreSQL and Rillet data to work

Start with the work your team needs to complete: keep records up to date, make operational data available for reporting, or move data to a new system. Choose one PostgreSQL and Rillet workflow to test, define what success looks like, and decide who handles failed updates.

  • Expose SaaS objects (CRM contacts, ERP invoices, support tickets) as Postgres tables that internal tools can query and join

  • Let an application write to its own database and have those rows appear as records in business systems in near real time

  • 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.

What records can you sync?

Start with the records your workflow needs. Check each system’s read and write requirements before mapping fields.

PostgreSQL

Read and write support varies by record

Record types covered in the setup guide

Record typesCoverage and requirements
  • Tables
See connector requirements. Confirm field permissions and sync direction.

Read the PostgreSQL connector guide

Rillet

Read and write support varies by record

Record types covered in the setup guide

Record typesCoverage and requirements
  • Customer
  • Invoice
  • Vendor
  • Credit Memo
  • Bill
  • Journal Entry
  • Invoice Payment
  • Charge
  • Reimbursement
  • Custom Field
Incremental: ✅; historical: ✅; delete detection: ✅. Confirm field permissions and sync direction.
  • Account
Incremental: ✅; historical: ✅; delete detection: ✅ Every 1h. Confirm field permissions and sync direction.
  • Subsidiary
  • Tax Rate
  • Product
  • Contract
  • Bank Account
Incremental: ❌; historical: ✅; delete detection: ✅ Every 1h. Confirm field permissions and sync direction.
  • Bank Transaction
Incremental: ❌; historical: ✅; delete detection: ✅ Every 4h. Confirm field permissions and sync direction.

Read the Rillet connector guide

Connection essentials

Review how each system connects, detects changes, and permits access to your records.

View setup requirements and limits
Connection requirementPostgreSQLRillet
Integration interfaceSQL wire protocol (PostgreSQL frontend/backend protocol)REST API (OpenAPI-specified, with production and sandbox environments)
AuthenticationDatabase credentialsAPI key generated in Rillet
Change detectionThe Postgres connector uses logical replication.Historical and incremental syncs are documented by object.
Read accessAvailable for supported recordsAvailable for supported records
Write accessAvailable for supported recordsAvailable for supported records

Enterprise controls

Security and control for your integrations

Explore security controls

Compliance and data transfers

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
  • DPF US-EU-UK-CH

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:

Record-level recovery

Inspect sync errors and use retry and revert controls to resolve failed updates.

Read the recovery guide

Implementation

Technical reference

Review setup, record relationships, testing, and recovery for your implementation.

Authentication, permissions and API limits

Connection requirements and limits

PostgreSQL
Integration interface
SQL wire protocol (PostgreSQL frontend/backend protocol)
Authentication
Database credentials (connection string or parameters), with optional SSL root certificate upload and optional SSH tunnel (SSH user + host); a least-privilege DB user
Change detection
The Postgres connector uses logical replication. The separate Postgres Heroku connector uses database triggers when replication rights are unavailable.
Read access
Available for supported records
Write access
Available for supported records
Setup requirements
  • Use a single-column primary key with a database-generated default for every selected table; composite primary keys are not supported.
  • Give the connected database role the required ownership and replication rights. Logical replication requires wal_level=logical; check the hosted database procedure before changing it.
  • For PostgreSQL 12 and earlier, have the database administrator install the pgcrypto extension before starting the sync so tracking tables can use gen_random_uuid(). PostgreSQL 13 and later provide this function without the extension.
Limitations to check
  • Renaming a schema, table, or column requires updating the sync configuration.
  • Database views cannot be used as writable destinations in two-way sync; validate the selected connector and view support separately.
Technical documentation

Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.

PostgreSQL setup guide
Rillet
Integration interface
REST API (OpenAPI-specified, with production and sandbox environments)
Authentication
API key generated in Rillet (Organization Setting -> API Access); uncheck Read Only to enable writes for two-way sync; check Read Only to prevent write-back
Change detection
Historical and incremental syncs are documented by object. Some objects have only historical sync; delete detection intervals vary.
Read access
Available for supported records
Write access
Available for supported records
Setup requirements
  • Generate an API key in Rillet Organization Setting > API Access.
  • For two-way sync, clear the Read Only setting; use a read-only key when the integration only needs outbound data.
Limitations to check
  • Some objects have historical sync only; deletion checks for supported objects can run at different intervals.
Technical documentation

Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.

Rillet setup guide

Prepare PostgreSQL and Rillet access

Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.

PostgreSQL setup checklist
  • Use a single-column primary key with a database-generated default for every selected table; composite primary keys are not supported.
  • Give the connected database role the required ownership and replication rights. Logical replication requires wal_level=logical; check the hosted database procedure before changing it.
  • For PostgreSQL 12 and earlier, have the database administrator install the pgcrypto extension before starting the sync so tracking tables can use gen_random_uuid(). PostgreSQL 13 and later provide this function without the extension.

Setup guides: Authorize PostgresEnsuring Secure Cloud SQL Connections with SSL CertificateEnsuring Secure RDS Connections with SSL Certificate

Rillet setup checklist
  • Generate an API key in Rillet Organization Setting > API Access.
  • For two-way sync, clear the Read Only setting; use a read-only key when the integration only needs outbound data.

Setup guides: Authorize Rillet Connection

Prepare to go live

Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.

Use the PostgreSQL and Rillet planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.

See Stacksync in action · Review current pricing

Record identity and field ownership

Keep each record tied to its source ID. Use the references below to choose field owners and preserve relationships between records.

Download the mapping worksheet · CSV, no email required

Reporting dataset

Proposed customer table in PostgreSQL (choose its name) / Customer

Plan a customer dataset while preserving its source meaning.

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

PostgreSQL
Your database schema
Rillet
Documented record · Incremental: ✅; historical: ✅; delete detection: ✅
Record identity
Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient.
Field ownership
Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company.

Fields to include

  • Source customer ID
  • Person/company classification
  • Legal entity or business unit
  • Destination identity reference
Record dependencies
Resolve person or company type, legal entity, business role, and any billing account before transactions.
Validation
Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
Recovery
Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

References: Rillet: Customer documentation

Reporting dataset

Proposed customer invoice table in PostgreSQL (choose its name) / Invoice

Plan a customer invoice dataset while preserving its source meaning.

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

PostgreSQL
Your database schema
Rillet
Documented record · Incremental: ✅; historical: ✅; delete detection: ✅
Record identity
Retain the invoice ID, issuer/legal entity, and original order reference; invoice numbers alone may overlap.
Field ownership
The financial system owns posting and accounting treatment. A posted invoice may need a credit or adjustment process instead of an overwrite.

Fields to include

  • Source invoice ID
  • Customer or supplier reference
  • Line totals
  • Currency
  • Posting/payment status
Record dependencies
Resolve the customer or supplier, account codes, tax, currency, and accounting period before posting.
Validation
Test a posted invoice, a partial payment, tax rounding, and a closed accounting period. Compare financial totals within the same entity and currency.
Recovery
Determine whether a transaction posted before retrying. Follow the approved adjustment process for posted records.

References: Rillet: Invoice documentation

Reporting dataset

Proposed supplier bill table in PostgreSQL (choose its name) / Bill

Plan a supplier bill dataset while preserving its source meaning.

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

PostgreSQL
Your database schema
Rillet
Documented record · Incremental: ✅; historical: ✅; delete detection: ✅
Record identity
Retain the supplier-bill ID, supplier, legal entity, and document reference; distinguish it from a customer invoice.
Field ownership
Accounts payable owns approval and posting; a supplier bill is not an accounts-receivable invoice.

Fields to include

  • Source bill ID
  • Supplier reference
  • Entity
  • Line amounts and currency
  • Approval/posting state
Record dependencies
Resolve supplier, expense/account codes, entity, currency, and accounting period before bill lines.
Validation
Test a duplicate supplier document number in another entity, a partially paid bill, and a closed period.
Recovery
Verify whether the bill was approved or posted before retrying; use the approved adjustment process for posted bills.

References: Rillet: Bill documentation

Reporting dataset

Proposed payment or settlement table in PostgreSQL (choose its name) / Invoice Payment

Plan a payment or settlement dataset while preserving its source meaning.

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

PostgreSQL
Your database schema
Rillet
Documented record · Incremental: ✅; historical: ✅; delete detection: ✅
Record identity
Preserve transaction ID, provider/source, currency, and links to invoices; one payment may settle several documents.
Field ownership
Keep payment authorization, settlement, and accounting allocation distinct.

Fields to include

  • Source transaction ID
  • Invoice references
  • Amount and currency
  • Settlement status
  • Reversal reference
Record dependencies
Resolve the affected invoices and cash/account references before allocating the payment.
Validation
Test partial payment, one-to-many allocation, refund, and repeated delivery of the same transaction.
Recovery
Look up the original transaction before retrying to prevent duplicate allocation or charging.

References: Rillet: Invoice Payment documentation

Reporting dataset

Proposed supplier or vendor table in PostgreSQL (choose its name) / Vendor

Plan a supplier or vendor dataset while preserving its source meaning.

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

PostgreSQL
Your database schema
Rillet
Documented record · Incremental: ✅; historical: ✅; delete detection: ✅
Record identity
Use the supplier ID within its business entity; a supplier name may occur in several subsidiaries.
Field ownership
Assign responsibility for approved supplier details; restrict changes to payment instructions to the business approval process.

Fields to include

  • Source supplier ID
  • Legal name
  • Entity reference
  • Payment terms
  • Active status
Record dependencies
Resolve business-unit and payment-term references before purchasing transactions.
Validation
Test a supplier shared across subsidiaries and an inactive supplier referenced by an open bill.
Recovery
Review rejected supplier changes before retrying dependent bills; do not reactivate a supplier merely to make a write pass.

References: Rillet: Vendor documentation

Reporting dataset

Proposed journal or ledger entry table in PostgreSQL (choose its name) / Journal Entry

Plan a journal or ledger entry dataset while preserving its source meaning.

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

PostgreSQL
Your database schema
Rillet
Documented record · Incremental: ✅; historical: ✅; delete detection: ✅
Record identity
Retain journal ID and line IDs within the legal entity and accounting period.
Field ownership
The ledger owns posting approval and period controls; an integration should not treat a posted journal as an ordinary editable row.

Fields to include

  • Source journal ID
  • Account references
  • Debit/credit amounts
  • Entity
  • Accounting period
Record dependencies
Resolve chart-of-account, currency, entity, and dimension references before lines.
Validation
Verify balanced debits and credits, dimension requirements, and rejection for a closed period.
Recovery
Reconcile posting status and use the finance-approved reversal or adjustment process instead of replaying a posted entry.

References: Rillet: Journal Entry documentation

Compare integration approaches

Use PostgreSQL Proposed customer table in PostgreSQL (choose its name) and Rillet Customer for the first pilot. Verify its identity and permitted direction, then add dependent records only when the acceptance checks pass.

Stacksync managed sync

Best fit
Two-way sync for supported objects. Choose the records, writable fields, and permissions for your workflow.
Operating responsibility
Fits ongoing record synchronization when the required operations are supported. Add workflow steps for approvals or business actions that go beyond copying fields.
Before you choose
Check record matching: Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient. Verify field coverage, deletion handling, and how changes are detected.

Native vendor integration

Best fit
A vendor-built integration may fit if it supports your PostgreSQL and Rillet record types.
Operating responsibility
Can reduce setup for a supported workflow. You may need another method for records or business steps it does not cover.
Before you choose
First check whether either vendor offers this integration. If available, verify Proposed customer table in PostgreSQL (choose its name) / Customer, update direction, account tier, and related-record handling.

Custom API or workflow

Best fit
Consider when PostgreSQL and Rillet need a transformation, approval, or action outside a direct record sync.
Operating responsibility
Provides control over business steps; the team owns credentials, version changes, error queues, and reconciliation.
Before you choose
Verify endpoint permissions, pagination, quotas, duplicate detection, and failure recovery. Separate reading history from actions that send messages, grant access, or post transactions.

File or scheduled snapshot

Best fit
Consider for a one-time PostgreSQL / Rillet migration or a reporting need with an explicit freshness window.
Operating responsibility
Can simplify a bounded transfer; later changes and deletion history require another extraction or a separately designed incremental process.
Before you choose
Record the extraction cutoff, source IDs, encoding, date/number formats, and reconciliation totals.

Workflow scenarios and expected results

Customer reporting workflow

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

Starting event: A change to the selected Proposed customer table in PostgreSQL (choose its name) or Customer record needs a defined result in the other system.

  1. Start with PostgreSQL Proposed customer table in PostgreSQL (choose its name) and Rillet Customer. Use the record-matching and field-ownership rules from your mapping worksheet.
  2. Resolve person or company type, legal entity, business role, and any billing account before transactions.
  3. Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.

If it fails: Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

Customer invoice reporting workflow

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

Starting event: A change to the selected Proposed customer invoice table in PostgreSQL (choose its name) or Invoice record needs a defined result in the other system.

  1. Start with PostgreSQL Proposed customer invoice table in PostgreSQL (choose its name) and Rillet Invoice. Use the record-matching and field-ownership rules from your mapping worksheet.
  2. Resolve the customer or supplier, account codes, tax, currency, and accounting period before posting.
  3. Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test a posted invoice, a partial payment, tax rounding, and a closed accounting period. Compare financial totals within the same entity and currency.

If it fails: Determine whether a transaction posted before retrying. Follow the approved adjustment process for posted records.

Supplier bill reporting workflow

Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.

Starting event: A change to the selected Proposed supplier bill table in PostgreSQL (choose its name) or Bill record needs a defined result in the other system.

  1. Start with PostgreSQL Proposed supplier bill table in PostgreSQL (choose its name) and Rillet Bill. Use the record-matching and field-ownership rules from your mapping worksheet.
  2. Resolve supplier, expense/account codes, entity, currency, and accounting period before bill lines.
  3. Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test a duplicate supplier document number in another entity, a partially paid bill, and a closed period.

If it fails: Verify whether the bill was approved or posted before retrying; use the approved adjustment process for posted bills.

Reconcile Rillet business records with PostgreSQL

Validate the selected objects and operations even where connector-level direction is documented.

Starting event: A finance-owned record in Rillet needs operational visibility through a selected destination dataset.

  1. Select Customer or Vendor with the correct legal entity, period, and currency.
  2. Define a reporting relationship in PostgreSQL; do not equate customer records, ledger accounts, and posted transactions.
  3. Decide whether the process only reports a financial state or requests an approved accounting action, and maintain a separate transaction ID for each action.

Expected result: Totals reconcile within the same entity/currency/window; a repeated handoff creates no duplicate financial transaction.

If it fails: Verify posting and settlement state before retrying. Use the approved adjustment path for already-posted transactions.

Initial load and acceptance testing

Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.

Proposed customer table in PostgreSQL (choose its name) / Customer

Test case

Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.

Expected result

The expected customer relationship is preserved with no duplicate action or unintended write.

Proposed customer invoice table in PostgreSQL (choose its name) / Invoice

Test case

Test a posted invoice, a partial payment, tax rounding, and a closed accounting period. Compare financial totals within the same entity and currency.

Expected result

The expected customer invoice relationship is preserved with no duplicate action or unintended write.

Proposed supplier bill table in PostgreSQL (choose its name) / Bill

Test case

Test a duplicate supplier document number in another entity, a partially paid bill, and a closed period.

Expected result

The expected supplier bill relationship is preserved with no duplicate action or unintended write.

Proposed payment or settlement table in PostgreSQL (choose its name) / Invoice Payment

Test case

Test partial payment, one-to-many allocation, refund, and repeated delivery of the same transaction.

Expected result

The expected payment or settlement relationship is preserved with no duplicate action or unintended write.

Direction and permissions

Test case

Check that each connected account can read and write the chosen objects. Exercise both directions with a test record before enabling production changes.

Expected result

Only an approved, supported direction and permitted fields are written.

Freshness and reconciliation

Test case

Measure source and destination times for the selected records under normal load and a burst. Reconcile IDs and values using the same filters and cutoff.

Expected result

The process meets its agreed freshness target and reconciliation has no unexplained differences.

Failed updates, retries and recovery

Start with the failed record and the destination error, then inspect the source value, field requirements, and access.

Rejected or repeated customer change

Investigate

Inspect PostgreSQL Proposed customer table in PostgreSQL (choose its name) and Rillet Customer, their IDs, and the destination error.

Next action

Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

Rejected or repeated customer invoice change

Investigate

Inspect PostgreSQL Proposed customer invoice table in PostgreSQL (choose its name) and Rillet Invoice, their IDs, and the destination error.

Next action

Determine whether a transaction posted before retrying. Follow the approved adjustment process for posted records.

Rejected or repeated supplier bill change

Investigate

Inspect PostgreSQL Proposed supplier bill table in PostgreSQL (choose its name) and Rillet Bill, their IDs, and the destination error.

Next action

Verify whether the bill was approved or posted before retrying; use the approved adjustment process for posted bills.

A record type or update is unavailable

Investigate

Check the PostgreSQL and Rillet connector guides, account permissions, and any operations marked On Request.

Next action

Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.

Source and destination disagree after a retry

Investigate

Compare current source values, destination validation, identity mappings, and any side effects already completed.

Next action

Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.

Read the Stacksync issues dashboard guide for retry and revert behavior.

Change detection and update delivery

How updates move between PostgreSQL and Rillet

See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.

PostgreSQL Rillet Timing depends on the connected systems

Detect changesThe Postgres connector uses logical replication. The separate Postgres Heroku connector uses database triggers when replication rights are unavailable.

Apply updatesSelected writable fields update in Rillet. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.

Rillet PostgreSQL Timing depends on the connected systems

Detect changesHistorical and incremental syncs are documented by object. Some objects have only historical sync; delete detection intervals vary.

Apply updatesSelected writable fields update in PostgreSQL. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.

Update timing and record limits
  • Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
  • Some objects have historical sync only; deletion checks for supported objects can run at different intervals.
FAQ

PostgreSQL and Rillet integration FAQ

Further reading

Guides and resources

Next step

See your workflow in Stacksync

Walk through your PostgreSQL and Rillet records, field mappings, and requirements with an integration engineer.

See Stacksync in action Explore plans and pricing