Real-time
Two-way sync
Changes in Dynamics 365 F&O or Rillet instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Accounting and finance
Dynamics 365 F&O to Rillet integration — real-time, two-way sync
Keep Dynamics 365 F&O 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 Dynamics 365 F&O and Rillet
Keep Rillet and Dynamics 365 F&O agreeing on customers, invoices, and balances, whether they split the finance workload or one is replacing the other.
Teams connect Dynamics 365 F&O with Rillet to keep operational ERP activity and the accounting ledger in step. F&O Customers and Customer Invoices sync with Rillet Customer and Invoice records, so revenue and payables reflect the same transactions on both sides.
Stacksync syncs Bill, Journal Entry, Invoice Payment, Charge in Rillet with Sales Orders, Purchase Orders, Customer Invoices, Vendor Invoices in Dynamics 365 F&O 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 Close the books in Rillet on the same Invoice data F&O issued, without exports.
- 02 Map F&O transactions to the Rillet Account structure for accurate ledger posting.
- 03 Handle returns consistently by syncing credit activity between F&O and Rillet Credit Memos.
- 04 Mirror journal entries and contract revenue data into a warehouse for board and ARR reporting.
Common sync patterns
Customer and vendor master sync
F&O Customers and Vendors stay aligned with Rillet Customer and Vendor records.
Invoice flow to accounting
F&O Customer Invoices sync to Rillet Invoices, with adjustments captured as Credit Memos.
Payables alignment
F&O Purchase Orders match against Bills in Rillet for AP processing.
What you can sync between Dynamics 365 F&O 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.
| Dynamics 365 F&O objects | Rillet objects | How this pairing syncs | |
|---|---|---|---|
| Customers Customer master records; kept aligned with CRM accounts in two-way syncs. | Customer Synced with incremental and full sync per the Stacksync docs. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping. | |
| Vendors Supplier master records; synced with procurement and AP tools. | Vendor Synced with incremental and full sync per the Stacksync docs. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Customer Invoices AR billing documents; status synced back to CRM and customer success tools. | Bill Synced with incremental and full sync per the Stacksync docs. | Customer Invoices is specific to Dynamics 365 F&O and Bill to Rillet — each maps to any object or custom field on the other side. | |
| Vendor Invoices AP documents; synced with invoice automation systems. | Journal Entry Synced with incremental and full sync per the Stacksync docs. | Vendor Invoices is specific to Dynamics 365 F&O and Journal Entry to Rillet — each maps to any object or custom field on the other side. | |
| General Journal Entries GL postings; read-only extracts for consolidated finance reporting. | Invoice Payment Synced with incremental and full sync per the Stacksync docs. | General Journal Entries is specific to Dynamics 365 F&O and Invoice Payment to Rillet — each maps to any object or custom field on the other side. | |
| On-hand Inventory Stock positions; read out to storefronts and internal apps for availability. | Charge Synced with incremental and full sync per the Stacksync docs. | On-hand Inventory is specific to Dynamics 365 F&O and Charge to Rillet — each maps to any object or custom field on the other side. |
How changes propagate between Dynamics 365 F&O and Rillet
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.
Dynamics 365 F&O Rillet Sub-second propagation
DetectionDynamics 365 F&O pushes changes as they happen — webhook events backed by change data capture. Change data capture via the Dynamics 365 Change Tracking feature, enabled per entity.
DeliveryEach detected change is written to Rillet through its API, with automatic retries and rate-limit backoff.
Rillet Dynamics 365 F&O Sub-second propagation
DetectionRillet pushes changes as they happen — webhook events backed by change data capture. Near real-time updates via change tracking.
DeliveryEach detected change is written to Dynamics 365 F&O through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Dynamics 365 F&O: OData requests are subject to platform throttling; high-volume loads belong in the Data Management Framework.
- Rillet: Subject to the platform's API rate limits.
What ships with Dynamics 365 F&O ⇄ Rillet
Connect Dynamics 365 F&O and Rillet for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dynamics 365 F&O–Rillet connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Dynamics 365 F&O 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 Dynamics 365 F&O or Rillet record.
Observability
Monitoring
Track your Dynamics 365 F&O ⇄ Rillet sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Dynamics 365 F&O and Rillet.
How the Dynamics 365 F&O and Rillet connectors work
Dynamics 365 F&O
- Integration surface
- OData REST endpoint over data entities, plus the Data Management Framework for batch
- Authentication
- OAuth via Microsoft sign-in: provide the D365 F&O environment URL, sign in with Microsoft credentials, and grant the Stacksync app consent (admin consent may be required — "Need admin approval for this app")
- Change detection
- Change data capture via the Dynamics 365 Change Tracking feature, enabled per entity; falls back to periodic full-sync where change tracking is unavailable
- Capabilities
- read · write · CDC · webhooks
- Rate limits
- OData requests are subject to platform throttling; high-volume loads belong in the Data Management Framework.
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.
How it works
How to connect Dynamics 365 F&O 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.
- 01
Connect your apps
Authenticate Dynamics 365 F&O 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.
Dynamics 365 F&O
connected
Rillet
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Dynamics 365 F&O 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.
objects · Dynamics 365 F&O ⇄ RilletCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Dynamics 365 F&O RilletCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Dynamics 365 F&O and Rillet integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Dynamics 365 F&O and Rillet: authenticate both systems, choose the objects to sync (such as Dynamics 365 F&O's Customers and Vendors), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Change detection on Dynamics 365 F&O: Change data capture via the Dynamics 365 Change Tracking feature, enabled per entity; falls back to periodic full-sync where change tracking is unavailable. On Rillet: Near real-time updates via change tracking; incremental sync per object, with delete detection (some objects checked every 1h or 4h). Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Rillet side: Bill, Journal Entry, Invoice Payment, Charge, plus custom fields where Rillet exposes them. On the Dynamics 365 F&O side: Sales Orders, Purchase Orders, Customer Invoices, Vendor Invoices. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Dynamics 365 F&O and Rillet: Customer and vendor master sync; Invoice flow to accounting; Payables alignment. F&O Customers and Vendors stay aligned with Rillet Customer and Vendor records.
-
Dynamics 365 F&O: OData REST endpoint over data entities, plus the Data Management Framework for batch. Authentication: OAuth via Microsoft sign-in: provide the D365 F&O environment URL, sign in with Microsoft credentials, and grant the Stacksync app consent (admin consent may be required — "Need admin approval for this app"). Rillet: 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. Stacksync manages authentication, retries, and rate limits on both sides.
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
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 337 integrations available for Dynamics 365 F&O and Rillet.
Popular · 4 of 337
No integrations match .
