Integration guides · October 8, 2026

Acumatica EDI Integration: Complete Guide

Retail EDI on Acumatica with EDISQ — inbound 850s creating sales orders, shipment confirmation firing the 856, invoices flowing out as 810s.

Cloud ERP was supposed to make integrations easy, and with Acumatica it mostly did — the platform is API-first and the sales workflow is clean. What no ERP includes, Acumatica included, is the retail EDI layer: partner-specific X12 dialects, certified maps, compliance validation, and the connectivity retailers dictate. The EDISQ integration supplies that layer and lets Acumatica do what it's good at: running your orders, inventory, and financials as the single source of truth.

Order flow: from 850 to shipped and billed

Trace one retailer order through the integrated system and the whole design is visible. An 850 arrives from the partner and is checked against that retailer's companion-guide rules before anything else happens — bad identifiers and rule violations get caught at the door. The clean order posts into Acumatica as a sales order with the retailer's item numbers, ship-to codes, and references already translated to your master data. An 855 goes back automatically, answering the partner's response-time expectations while your team simply sees a new order in the queue.

Fulfillment proceeds however you run it — pick, pack, confirm. The confirmed shipment is the pivotal event: it triggers the 856 ship notice, assembled with the shipment hierarchy and carton identifiers the partner's receiving operation will scan against, transmitted while the freight is still moving. Releasing the invoice completes the loop as an 810 that echoes the PO number and shipped quantities, arriving at the retailer's payables already aligned for the match. For partners that require availability feeds, inventory positions can publish outbound as scheduled 846 documents along the way.

Division of labor

A useful way to evaluate any ERP-EDI pairing is to ask which system owns what. In this one, Acumatica owns truth: items, customers, stock, orders, financials. EDISQ owns translation and compliance: the partner maps, the cross-reference tables binding retailer identifiers to Acumatica records, the validation that stops non-compliant documents before transmission, and the 997 acknowledgment traffic that proves delivery both ways. Neither system reaches into the other's job, which is why the integration stays stable through Acumatica upgrades and retailer spec revisions alike — map changes land on EDISQ's side as part of the service.

The implementation arc

Acumatica shops usually start this project under deadline — a big-retailer program, say Lowe's, with a go-live date in the vendor packet. The path: connect EDISQ to your Acumatica instance; enable the partner from the 2,200+ directory, loading certified maps; build the item and location cross-references; replay the partner's certification scenarios in the sandbox until the full order-to-invoice cycle passes; go live with monitoring on the first cycles. Subsequent partners skip straight to cross-references and testing, because the ERP side is already done.

Plan for exceptions as part of the rollout rather than an afterthought. Even a well-tuned flow occasionally produces a document that fails partner validation — a new item missing from the cross-reference is the classic case — and what matters is where that failure lands. Configure the integration so exceptions surface to the people who can fix the data, with the document held rather than transmitted broken; a rejected item mapping corrected in minutes never becomes a chargeback dispute measured in weeks.

Pricing that ignores your size

Nothing about the Acumatica integration is priced as an enterprise add-on. EDISQ's meter reads documents and nothing else: 25 free each month, then from $0.50 per document tapering to $0.10 at the largest volumes, computed marginally within each bracket. The connector, the partner maps, and AS2/SFTP/VAN transport are all included — no mapping or setup fees, and live trading runs on a flat $100/month Production minimum applied entirely to document usage. Connector details sit on the Acumatica integration page, and the full rate ladder is on pricing.

FAQ

How do retailer POs reach Acumatica?

The connector receives the 850, validates it against the partner's rules, and creates an Acumatica sales order with items, customer, and ship-to already cross-referenced — the order is ready to process on arrival.

When does the ASN transmit?

On shipment confirmation. Confirming the shipment in Acumatica hands the connector the data to build the 856 — hierarchy, cartons, identifiers per the partner's spec — and it transmits ahead of the freight.

Can one Acumatica integration serve many retailers?

Yes. The ERP integration is built once; each trading partner you enable layers its own certified maps and validation onto the same connection, so partner two is configuration rather than a project.