Two-way sync
Changes in Acumatica or Rillet instantly reflect in both systems. No stale data, no manual imports.
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.
Finance teams pair Acumatica operations data with Rillet as the accounting system of record. Acumatica Customers, Vendors, and Invoices sync to Rillet Customer, Vendor, Invoice, and Bill records so the ledger reflects operational activity without month-end re-entry.
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.
Acumatica Invoices are created in Rillet as Invoice records against the matching Customer.
Acumatica Purchase Orders and Vendor records feed Rillet Bills and Vendor entries for AP processing.
Acumatica Customers and Vendors stay aligned with Rillet Customer and Vendor records.
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 | How this pairing syncs | |
|---|---|---|---|
| Customers AR master data 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 Supplier 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. | |
| Invoices AR and AP billing documents synced for payment tracking and CRM visibility. | Invoice 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. | |
| Opportunities and Cases Built-in CRM records synced with external sales and support tools. | Journal Entry Synced with incremental and full sync per the Stacksync docs. | Opportunities and Cases is specific to Acumatica and Journal Entry to Rillet — each maps to any object or custom field on the other side. | |
| Sales Orders Order documents created from e-commerce and CRM systems, read back for fulfillment status. | Invoice Payment Synced with incremental and full sync per the Stacksync docs. | Sales Orders is specific to Acumatica and Invoice Payment to Rillet — each maps to any object or custom field on the other side. | |
| Purchase Orders Procurement documents exchanged with supplier-facing systems. | Charge Synced with incremental and full sync per the Stacksync docs. | Purchase Orders is specific to Acumatica and Charge to Rillet — each maps to any object or custom field on the other side. |
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.
DetectionAcumatica notifies Stacksync of record changes through webhook events. Push notifications configurable on data changes, plus polling on LastModifiedDateTime fields.
DeliveryEach detected change is written to Rillet through its API, with automatic retries and rate-limit backoff.
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 Acumatica through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Acumatica–Rillet connection.
Changes in Acumatica or Rillet instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Acumatica or Rillet data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Acumatica or Rillet record.
Track your Acumatica ⇄ Rillet sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Acumatica and Rillet.
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.
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.
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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
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 Customers and Vendors), 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: Invoice flow to accounting; Payables handoff; Entity master sync. Acumatica Invoices are created in Rillet as Invoice records against the matching Customer.
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.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 437 integrations available for Acumatica and Rillet.