Real-time
Two-way sync
Changes in Acumatica or Rillet instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Accounting and finance
Acumatica to Rillet integration — real-time, two-way sync
Keep Acumatica 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 Acumatica and Rillet
Keep Rillet and Acumatica 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 Credit Memo, Bill, Journal Entry, Invoice Payment in Rillet with Journal Transactions, Projects, Opportunities and Cases, Customers in Acumatica 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
- Sync AR and collection status back to customer success tools ahead of renewals.
- Keep customers and invoices aligned between Rillet and a CRM so finance and sales work from the same account records.
- Replicate journal transactions and financial data into a SQL database for reporting and consolidation.
- Sync vendor bills from AP automation tools into Acumatica for approval and payment.
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.
Subsidiary to headquarters
Where Rillet serves a business unit and Acumatica is the group system, transactions and customer records roll up continuously, so consolidation starts from live data.
What you can sync between Acumatica 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.
| Acumatica objects | Rillet objects | |
|---|---|---|
| Sales Orders Order documents created from e-commerce and CRM systems, read back for fulfillment status. | Journal Entry Synced with incremental and full sync per the Stacksync docs. | |
| Invoices AR and AP billing documents synced for payment tracking and CRM visibility. | Invoice Payment Synced with incremental and full sync per the Stacksync docs. | |
| Purchase Orders Procurement documents exchanged with supplier-facing systems. | Charge Synced with incremental and full sync per the Stacksync docs. | |
| Stock Items Inventory master data with quantities shared with external sales channels. | Reimbursement Synced with incremental and full sync per the Stacksync docs. | |
| Shipments Fulfillment documents read to update tracking in storefronts and CRMs. | Custom Field Synced with incremental and full sync per the Stacksync docs. | |
| Payments Customer payment records reconciled against invoices from payment platforms. | Account Synced with incremental and full sync per the Stacksync docs. |
What ships with Acumatica ⇄ Rillet
Connect Acumatica and Rillet for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Acumatica–Rillet connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Acumatica 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 Acumatica or Rillet record.
Observability
Monitoring
Track your Acumatica ⇄ Rillet sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Acumatica and Rillet.
How the Acumatica and Rillet connectors work
Acumatica
- Integration surface
- Contract-based REST API (JSON over versioned endpoints), plus SOAP web services and OData access to Generic Inquiries
- Authentication
- OAuth 2.0 or cookie-based session login with Acumatica credentials
- Change detection
- Push notifications configurable on data changes, plus polling on LastModifiedDateTime fields
- Capabilities
- read · write · webhooks
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 Acumatica 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 Acumatica 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.
Acumatica
connected
Rillet
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Acumatica 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 · Acumatica ⇄ 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.
Acumatica RilletCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Acumatica and Rillet integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Acumatica and Rillet: authenticate both systems, choose the objects to sync (such as Acumatica's Sales Orders and Invoices), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Rillet side: Credit Memo, Bill, Journal Entry, Invoice Payment, plus custom fields where Rillet exposes them. On the Acumatica side: Journal Transactions, Projects, Opportunities and Cases, Customers. 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 Acumatica and Rillet: Migration without a hard cutover; One customer and vendor master; Subsidiary to headquarters. When one system is replacing the other, run both in parallel with records matching until the switch is complete.
-
Acumatica: Contract-based REST API (JSON over versioned endpoints), plus SOAP web services and OData access to Generic Inquiries. Authentication: OAuth 2.0 or cookie-based session login with Acumatica credentials. 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: Several objects (Subsidiary, Tax Rate, Product, Contract, Bank Account, Bank Transaction) do not support incremental sync — historic sync only. Acumatica: Push notifications can be configured to send data-change notifications to an external URL, based on generic inquiries that define which changes to watch. Stacksync's field mapping accounts for these differences between Acumatica and Rillet without custom code.
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 Acumatica and Rillet.
Popular · 8 of 386
-
Acumatica ⇄ Stripe -
Acumatica ⇄ Workday -
Acumatica ⇄ Anaplan -
Acumatica ⇄ Chargebee -
Rillet ⇄ Global Shop Solutions -
Rillet ⇄ Infor CloudSuite - Rillet ⇄ Infor LN
- Rillet ⇄ Infor M3
No integrations match .
