Skip to content
ERP ⇄ Storage

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

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

Move the documents and data that Acumatica produces into Box as files, and let files stored in Box update the records they belong to in Acumatica, continuously and without exports or manual filing.

Acumatica runs the business on structured records: Shipments, Payments, Journal Transactions, Projects. Box holds files and the metadata that describes them: Users, Groups, Tasks, Events. The two do not share a customer table or an order ledger. What they share is documents. Nearly every record Acumatica touches produces a file that belongs in storage, whether an invoice, a purchase order, a statement, or a shipping doc, and many files that land in Box, from signed contracts to vendor bills to receipts, describe a transaction Acumatica needs to record. Left unconnected, that link is maintained by hand: someone exports a PDF and drags it into a folder, or downloads a file and keys its details into a record.

Stacksync keeps Shipments, Payments, Journal Transactions, Projects in Acumatica and Users, Groups, Tasks, Events in Box in sync, bi-directionally and in real time. A document and its details, the customer, the type, the date, an amount, an order or invoice number, are mapped field by field, so a file arrives in Box already labeled and filed, and metadata captured against a stored file can create or update the matching record in Acumatica. Changes on either side show up within seconds, with conflict resolution in place of nightly exports and manual filing.

The result is that a transaction and the document that backs it stay together. Finance, operations, and audit teams find the file behind a record without digging through folders, and the record in Acumatica and the file in Box never describe two different versions of the same document.

Common use cases

  • 01 Align Acumatica's built-in CRM opportunities and cases with an external sales or support platform.
  • 02 Two-way sync of customers, orders, and invoices between Acumatica and a CRM so sales sees ERP truth without ERP logins.
  • 03 Provision and deprovision Users, Groups, and Collaborations from an HR system or IdP so Box access follows onboarding and offboarding.
  • 04 Push generated documents from an ERP or contract system into Box Folders with the right Collaborations applied for the deal team.

Common sync patterns

An archive that stays current

As records change in Acumatica, the corresponding files and metadata in Box are kept in step, so a stored document reflects the latest version rather than a stale one-time export.

Audit-ready retention

Every transaction's supporting file lives in Box beside its metadata, giving finance and audit teams a complete, searchable trail tied back to the record in Acumatica.

Documents filed with their context

Files that Acumatica produces land in Box labeled with the customer, document type, and reference number they belong to, so the right copy is one search away instead of buried in a folder.

What you can sync between Acumatica and Box

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 Box objects How this pairing syncs
Journal Transactions GL entries replicated into reporting databases. Folders Hierarchical containers whose tree, names, and parent moves are mirrored so a target system reflects Box's structure; the account root is always folder ID 0. Journal Transactions is specific to Acumatica and Folders to Box — each maps to any object or custom field on the other side.
Projects Project cost and billing structures synced with delivery tools. Metadata Structured key-value instances attached to files and folders via metadata templates; synced two-way with database columns for classification and search. Projects is specific to Acumatica and Metadata to Box — each maps to any object or custom field on the other side.
Opportunities and Cases Built-in CRM records synced with external sales and support tools. Collaborations Access grants linking a user or group to a file or folder with a role such as viewer, editor, or co-owner; written to manage sharing programmatically. Opportunities and Cases is specific to Acumatica and Collaborations to Box — each maps to any object or custom field on the other side.
Customers AR master data synced with CRMs and billing tools. Users Managed and app users in the enterprise; provisioned, updated, and deprovisioned to keep Box access aligned with an HR or identity source. Customers is specific to Acumatica and Users to Box — each maps to any object or custom field on the other side.
Vendors Supplier records aligned with procurement and AP automation. Groups Named user collections used for bulk collaboration; membership synced from a directory or IdP. Vendors is specific to Acumatica and Groups to Box — 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. Tasks Review or approval assignments on a file with due dates and states; read for workflow reporting or written to start approvals. Sales Orders is specific to Acumatica and Tasks to Box — each maps to any object or custom field on the other side.

How changes propagate between Acumatica and Box

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

Box Acumatica Sub-second propagation

DetectionBox notifies Stacksync of record changes through webhook events. V2 webhooks fire on triggers such as FILE.UPLOADED, FILE.TRASHED, and METADATA_INSTANCE.UPDATED.

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

Rate-limit considerations

  • Box: Per user: 1,000 API calls per minute and 240 file uploads per minute; exceeding limits returns HTTP 429 with a Retry-After header. Box Business plans also carry a licensed monthly API-call allotment per enterprise.
What ships with Acumatica ⇄ Box

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Box

Integration surface
REST API (api.box.com/2.0), plus the Events API and V2 Webhooks
Authentication
OAuth 2.0 for user-delegated access, or server-to-server auth via JWT (RSA keypair) or Client Credentials Grant (CCG) using a Box app; short-lived developer tokens for testing
Change detection
V2 webhooks fire on triggers such as FILE.UPLOADED, FILE.TRASHED, and METADATA_INSTANCE.UPDATED; the Events API (user stream via long-poll by stream_position, or enterprise/admin events) provides a near-real-time change feed
Capabilities
read · write · webhooks
Rate limits
Per user: 1,000 API calls per minute and 240 file uploads per minute; exceeding limits returns HTTP 429 with a Retry-After header. Box Business plans also carry a licensed monthly API-call allotment per enterprise.
How it works

How to connect Acumatica to Box — 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 Box 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
    Box connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Acumatica and Box 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 ⇄ Box
    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 Box
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Acumatica and Box 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
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 507 integrations available for Acumatica and Box.

Popular · 7 of 507
All Acumatica integrations All Box 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