Real-time
Two-way sync
Changes in Microsoft Dynamics GP or Rillet instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Accounting and finance
Microsoft Dynamics GP to Rillet integration — real-time, two-way sync
Keep Microsoft Dynamics GP 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 Microsoft Dynamics GP and Rillet
Keep Rillet and Microsoft Dynamics GP agreeing on customers, invoices, and balances, whether they split the finance workload or one is replacing the other.
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 Field, Account, Customer, Vendor in Rillet with Purchase Orders (POP), Inventory Items (IV), GL Accounts & Journal Entries, Receivables & Payables Transactions in Microsoft Dynamics GP 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 Push billing events from a product or usage-metering system into Rillet for revenue recognition.
- 02 Sync AR and collection status back to customer success tools ahead of renewals.
- 03 Sync customers and invoices between GP and a CRM so sales sees balances and billing history.
- 04 Push web or CRM orders into Sales Order Processing through eConnect instead of manual entry.
Common sync patterns
Where Rillet handles billing: invoices land in Microsoft Dynamics GP
Invoices and payment activity from the billing side post through to the enterprise system automatically.
Migration without a hard cutover
When one system is replacing the other, run both in parallel with records matching until the switch is complete.
One customer and vendor master
Where both systems keep records of the same organizations, corrections made in either propagate to the other.
What you can sync between Microsoft Dynamics GP 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.
| Microsoft Dynamics GP objects | Rillet objects | How this pairing syncs | |
|---|---|---|---|
| Customers Receivables master records (RM tables) synced with CRMs and billing tools. | 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. | |
| Vendors Payables master records aligned with procurement and AP automation. | 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. | |
| Inventory Items (IV) Item master and quantity data mirrored to ecommerce and planning systems. | Reimbursement Synced with incremental and full sync per the Stacksync docs. | Inventory Items (IV) is specific to Microsoft Dynamics GP and Reimbursement to Rillet — each maps to any object or custom field on the other side. | |
| GL Accounts & Journal Entries Financial ledger data replicated to warehouses for consolidated reporting. | Custom Field Synced with incremental and full sync per the Stacksync docs. | GL Accounts & Journal Entries is specific to Microsoft Dynamics GP and Custom Field to Rillet — each maps to any object or custom field on the other side. | |
| Receivables & Payables Transactions Open and historical AR/AP transactions read for cash and aging reporting. | Account Synced with incremental and full sync per the Stacksync docs. | Receivables & Payables Transactions is specific to Microsoft Dynamics GP and Account to Rillet — each maps to any object or custom field on the other side. | |
| Company Databases Per-company SQL databases that define the scope of any sync. | Invoice Synced with incremental and full sync per the Stacksync docs. | Company Databases is specific to Microsoft Dynamics GP and Invoice to Rillet — each maps to any object or custom field on the other side. |
How changes propagate between Microsoft Dynamics GP 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.
Microsoft Dynamics GP Rillet Sub-second propagation
DetectionChanges in Microsoft Dynamics GP are captured at the source via change data capture — no polling loop against its API. SQL Server change tracking or log-based CDC on the company database, or polling on row timestamps.
DeliveryEach detected change is written to Rillet through its API, with automatic retries and rate-limit backoff.
Rillet Microsoft Dynamics GP 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 applied to Microsoft Dynamics GP as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- Rillet: Subject to the platform's API rate limits.
What ships with Microsoft Dynamics GP ⇄ Rillet
Connect Microsoft Dynamics GP and Rillet for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Microsoft Dynamics GP–Rillet connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Microsoft Dynamics GP 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 Microsoft Dynamics GP or Rillet record.
Observability
Monitoring
Track your Microsoft Dynamics GP ⇄ Rillet sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Microsoft Dynamics GP and Rillet.
How the Microsoft Dynamics GP and Rillet connectors work
Microsoft Dynamics GP
- Integration surface
- SQL Server database access plus the eConnect stored-procedure API; Web Services for GP on some deployments
- Authentication
- SQL Server credentials or Windows authentication
- Change detection
- SQL Server change tracking or log-based CDC on the company database, or polling on row timestamps
- Capabilities
- read · write · CDC
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 Microsoft Dynamics GP 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 Microsoft Dynamics GP 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.
Microsoft Dynamics GP
connected
Rillet
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Microsoft Dynamics GP 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 · Microsoft Dynamics GP ⇄ 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.
Microsoft Dynamics GP RilletCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Microsoft Dynamics GP and Rillet integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Microsoft Dynamics GP and Rillet: authenticate both systems, choose the objects to sync (such as Microsoft Dynamics GP's Customers and Vendors), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Microsoft Dynamics GP: SQL Server database access plus the eConnect stored-procedure API; Web Services for GP on some deployments. Authentication: SQL Server credentials or Windows authentication. 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.
-
Rillet: Rillet is built for SaaS companies, with a general ledger organized around automated revenue recognition and month-end close. Microsoft Dynamics GP: Tables follow module prefixes such as RM (receivables), SOP (sales order processing), POP (purchasing), and IV (inventory). Stacksync's field mapping accounts for these differences between Microsoft Dynamics GP and Rillet without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Microsoft Dynamics GP and Rillet records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Microsoft Dynamics GP and Rillet connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Microsoft Dynamics GP–Rillet integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Microsoft Dynamics GP and Rillet. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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
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 426 integrations available for Microsoft Dynamics GP and Rillet.
Popular · 5 of 426
-
Microsoft Dynamics GP ⇄ Navan -
Microsoft Dynamics GP ⇄ Ramp -
Microsoft Dynamics GP ⇄ Recurly -
Microsoft Dynamics GP ⇄ Workday -
Rillet ⇄ NetSuite
No integrations match .
