Connect Acumatica to EDI instantly
Join thousands of businesses moving EDI orders, invoices and fulfilment updates between Acumatica and their trading partners on XEDI, no manual re-keying.
No credit card needed ✦ Free EDI mailbox included
Getting started with Acumatica EDI
XEDI connects Acumatica with retailers, wholesalers and logistics providers so EDI orders, acknowledgements, despatch advice and invoices move between Acumatica and your trading partners without anyone re-entering them.
One managed platform, no custom code
XEDI maps Acumatica to your trading partners and validates every document, so data flows straight into the systems your teams already use.
Acumatica is built to be integrated, which shortens the work
Acumatica exposes its business objects through a contract-based API and its own import and export scenarios, so an EDI integration uses documented routes rather than anything bolted on. A retailer's order becomes a sales order against the right customer, stock items and warehouse; a shipment raises the despatch advice; the invoice leaves from Acumatica.
What that means in practice is that the argument is rarely about whether Acumatica can accept the document. It is about which identifiers each retailer uses and how those line up with your item and customer records, which is the part we do.
Where a multi-branch setup complicates it
Acumatica installations often run several branches or companies against one tenant, each with its own numbering, warehouses and tax treatment. A retailer's order has to land against the right one, and a delivery point they add later has to resolve without somebody picking from a list.
We map each partner's identifiers to the branch, warehouse and customer they actually belong to, so the routing is decided once rather than at the point somebody is looking at an order.
What your team sees day to day
You get an EDI mailbox and a portal that works like an inbox. Retailer orders arrive and your team is notified, so trading can start before the Acumatica work is finished rather than waiting on it.
Each document then derives from the last: the order becomes the despatch advice rather than a re-keyed one, amended if you are shipping differently from what was ordered, with SSCC labels for the pallets, and becomes the invoice once delivered. Delivery of that invoice is confirmed in the dashboard rather than assumed.
The integration sits over that workflow and automates it, so orders land as Acumatica sales orders and shipments raise the outbound documents. Smaller teams run the portal alone; our API serves enterprises wanting finer granularity; an Acumatica integration is the middle.
Documents you can exchange
- Purchase orders landing as Acumatica sales orders
- Order acknowledgements returned to trading partners
- Despatch advice and ASN messages from Acumatica shipments
- Invoices raised from Acumatica
- Stock and price data where a partner maintains a catalogue
Built for Acumatica teams
Whoever owns Acumatica in your business, XEDI keeps EDI accurate and hands-off.
- Operations and fulfilment teams
- Finance teams
- Retail and wholesale suppliers
- Acumatica administrators
- Businesses replacing manual order entry
Acumatica EDI document types
The set varies by retailer, but an Acumatica supplier programme is usually built from these flows.
| Document | What it carries | Direction |
|---|---|---|
| Purchase orders | Retailer demand landing as an Acumatica sales order against the right customer, stock items, price and warehouse. | Partner to Acumatica |
| Order acknowledgements | Confirmation of what will be supplied, including accepted, amended and rejected lines. | Acumatica to partner |
| Advanced shipping notices | Despatch and pack detail raised from an Acumatica shipment, to carton or pallet level where the retailer requires it. | Acumatica to partner |
| Invoices | Invoices raised in Acumatica and referenced to the order and delivery so the retailer can match them. | Acumatica to partner |
| Credit notes | Credit memos raised in Acumatica against the invoice they adjust. | Acumatica to partner |
| Stock and price data | Item, pack and price data published to retailers that maintain a catalogue against your range. | Acumatica to partner |
How to connect Acumatica with EDI using XEDI
Because Acumatica's routes are documented, the build is mapping and verification rather than development. The sequence below is what onboarding looks like from your side.
-
01
We scope the Acumatica branches, warehouses and retailers in each document flow.
-
02
We build the mapping between each retailer's documents and your Acumatica customers, stock items and warehouses.
-
03
We configure validation so a document is checked against the retailer's rules before it reaches Acumatica.
-
04
We prove the order, shipment and invoice flows against what each retailer requires and against how your branches are set up.
-
05
You get documents landing against the right branch every time, and we keep it that way as you add retailers.
Ready to connect Acumatica?
Talk through documents, mapping, testing and go-live with XEDI.
Everything about Acumatica EDI
Common requirements
- Acumatica access
- Branch and warehouse structure
- Customer and location records
- Stock item and pack data
- Which partners you trade with
What we need from you to build it
Only the things we cannot hold for you. What each trading partner requires is already on our side, so there is no specification to obtain.
- Acumatica access
- A role and API or integration user with rights to the screens and objects in scope, usually sales orders, shipments and invoices.
- Branch and warehouse structure
- Which branch, company and warehouse each retailer trades against, since numbering, tax and routing follow that.
- Customer and location records
- Each retailer mapped to an Acumatica customer, with their delivery points resolvable to a ship-to.
- Stock item and pack data
- GTINs at each packaging level and the unit a retailer orders in, against how the item is held in Acumatica.
- Which partners you trade with
- The retailers in scope, now and next. What each requires is already on our side.
Why suppliers choose XEDI for Acumatica
- Your retailers are very likely already connected, so the first order can arrive before Acumatica is mapped.
- A new retailer is not an Acumatica customisation. We build and verify the connection before it carries live documents.
- Documents are validated against the retailer's rules before they are sent, so a rejection surfaces while the order can still be changed.
- One connection covers the retailers you trade with now and every one you take on later, each onboarded by us.
- Branch and warehouse routing is decided in the mapping, so nobody is choosing where an order belongs.
- If a retailer raises a problem, it comes to us. We are notified on your behalf and put it right before it becomes a delivery issue.
Can XEDI connect Acumatica to EDI trading partners?
Yes. XEDI maps each retailer's EDI documents to Acumatica sales orders, shipments and invoices through its documented integration routes, and returns acknowledgements, despatch advice and invoices in the format each retailer requires.
Does an Acumatica EDI integration need customisation?
Usually not. Acumatica's API and import scenarios already expose the objects involved, so the work is mapping retailer identifiers to your records rather than building anything inside the ERP.
Can it handle multiple branches or companies?
Yes. Each retailer is mapped to the branch, warehouse and customer they trade against, so orders land in the right place without anyone routing them by hand.
Plan your Acumatica EDI setup
Everything you need to scope, map and go live with Acumatica, in one place.