Skip to content
ERP ⇄ Accounting and finance

Acumatica to Recurly integration — real-time, two-way sync

Keep Acumatica and Recurly 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 Recurly

Keep Recurly 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 Measured Units and Usage, Accounts, Subscriptions, Plans in Recurly with Projects, Opportunities and Cases, Customers, Vendors 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

  • 01 Trigger revenue-recognition or ERP entries when new_subscription and canceled_subscription webhooks fire.
  • 02 Post usage records to Measured Units on metered Subscriptions from a metering database before each bill run.
  • 03 Mirror stock items and quantities to external channels so availability stays accurate across systems.
  • 04 Replicate journal transactions and financial data into a SQL database for reporting and consolidation.

Common sync patterns

Subsidiary to headquarters

Where Recurly serves a business unit and Acumatica is the group system, transactions and customer records roll up continuously, so consolidation starts from live data.

Where Recurly handles billing: invoices land in Acumatica

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.

What you can sync between Acumatica and Recurly

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 Recurly objects How this pairing syncs
Invoices AR and AP billing documents synced for payment tracking and CRM visibility. Invoices Charge and credit billing documents; read-heavy for revenue reporting, and creatable through Purchases for one-off charges. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Stock Items Inventory master data with quantities shared with external sales channels. Transactions Individual payment attempts — captures, refunds, and voids; typically read into a warehouse for reconciliation and dunning analysis. Stock Items is specific to Acumatica and Transactions to Recurly — each maps to any object or custom field on the other side.
Shipments Fulfillment documents read to update tracking in storefronts and CRMs. Line Items One-time charges and credits on an account outside a subscription; synced for accurate revenue and adjustment reporting. Shipments is specific to Acumatica and Line Items to Recurly — each maps to any object or custom field on the other side.
Payments Customer payment records reconciled against invoices from payment platforms. Coupons and Redemptions Discount definitions and their application to accounts and subscriptions; read for discount and promotion analysis. Payments is specific to Acumatica and Coupons and Redemptions to Recurly — each maps to any object or custom field on the other side.
Journal Transactions GL entries replicated into reporting databases. Billing Info Tokenized payment method (card/ACH) on an account; written when onboarding customers and read for payment-health signals (never stores raw card numbers). Journal Transactions is specific to Acumatica and Billing Info to Recurly — each maps to any object or custom field on the other side.
Projects Project cost and billing structures synced with delivery tools. Measured Units and Usage Metered-billing units; usage records are posted to a subscription before each bill run for consumption-based pricing. Projects is specific to Acumatica and Measured Units and Usage to Recurly — each maps to any object or custom field on the other side.

How changes propagate between Acumatica and Recurly

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.

Acumatica Recurly Sub-second propagation

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 Recurly through its API, with automatic retries and rate-limit backoff.

Recurly Acumatica Sub-second propagation

DetectionRecurly notifies Stacksync of record changes through webhook events. Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints.

DeliveryEach detected change is written to Acumatica through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Recurly: Production sites default to 1,000 requests/min with only GET requests counting toward the limit; sandbox sites 400/min with all requests counting; the limit is a sliding 5-minute window, X-RateLimit headers report the quota, and breaches return HTTP 429.
What ships with Acumatica ⇄ Recurly

Connect Acumatica and Recurly for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Acumatica–Recurly connection.

Real-time

Two-way sync

Changes in Acumatica or Recurly instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Acumatica or Recurly 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 Recurly record.

Observability

Monitoring

Track your Acumatica ⇄ Recurly 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 Recurly.

How the Acumatica and Recurly 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

Recurly

Integration surface
REST API (V3, date-versioned; legacy V2 XML API also exists)
Authentication
API key via HTTP Basic auth (key as username, blank password); keys are per-site, with separate sandbox and production keys
Change detection
Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints sorted by updated_at with begin_time/end_time filters
Capabilities
read · write · webhooks
Rate limits
Production sites default to 1,000 requests/min with only GET requests counting toward the limit; sandbox sites 400/min with all requests counting; the limit is a sliding 5-minute window, X-RateLimit headers report the quota, and breaches return HTTP 429.
How it works

How to connect Acumatica to Recurly — 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.

  1. 01

    Connect your apps

    Authenticate Acumatica and Recurly with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Acumatica connected
    Recurly connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Acumatica and Recurly 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Acumatica ⇄ Recurly
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Acumatica Recurly
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Acumatica and Recurly integration FAQ

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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 511 integrations available for Acumatica and Recurly.

Popular · 7 of 511
All Acumatica integrations All Recurly integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own