Acknowledge what you can actually fulfil.
The integration checks warehouse availability when you acknowledge each line. If the quantity isn't there, it won't let you confirm the order as fully accepted.
NATIVE EDI FOR ACUMATICA
Open Acumatica.
The orders are
already there.
A trading partner sends a purchase order. It arrives in Acumatica as a sales order, with the lines, addresses and prices in it.
The order, on your own sales order screen
Lines, quantities, prices, ship-to address, UPC codes, warehouse. Everything is filled in. It’s a real Acumatica sales order on the same screen your team already works in.
Walmart. Ford. Amazon. A thousand more.
Many of the trading partners you may need to connect with are already in UniLink’s network. If yours isn't there, UniLink builds it.
More than getting the order into Acumatica
Keep EDI orders under control.
Lines created from EDI can't be casually changed or deleted. Quantity, price and other changes are handled through the acknowledgement fields, so the response you send back reflects what changed.
See what went through, and what didn't.
Every inbound and outbound EDI transfer is logged in Acumatica. Your team can see what was processed, what failed and the error behind it without going into the SFTP server.
Two numbers tell you whether this is worth doing
Neither sits in a budget. The first is buried in someone's day. The second arrives months after the shipment, against the account you worked hardest to win.
The number of orders your team keys in by hand each month.
And what deductions were taken from your remittances last year
The guide has the list of situations where this pays for itself quickly, and the ones where it doesn't yet.
Get the EDI guideHow EDI works inside Acumatica
Customer purchase orders in.
Process orders as they arrive, in bulk, or on a schedule you set.
-
Customer
A customer sends an EDI 850 purchase order.
850 Purchase order -
UniLink
UniLink translates it and passes it to Acumatica.
Translation -
Acumatica
It becomes a populated sales order.
Sales order
Customer documents out.
Send the EDI 855 purchase order acknowledgement, 856 advance shipping notice (ASN) and 810 invoice back through UniLink from the Acumatica screens your team already works in.
AcumaticaUniLinkCustomer
- 855 Acknowledgement
- 856 ASN
- 810 Invoice
Purchase orders out.
Send EDI 850 purchase orders from Acumatica to your vendors.
-
Acumatica
Send an EDI 850 purchase order from Acumatica.
850 Purchase order -
UniLink
UniLink translates it into EDI.
Translation -
Vendor
Your vendor receives the EDI purchase order.
Purchase order
Vendor documents in.
When their documents come back, the 855 updates your purchase order, the 856 creates the purchase receipt, and the 810 creates the AP bill.
VendorUniLinkAcumatica
- 855PO Acknowledgement
- Updates purchase order
- 856ASN
- Creates purchase receipt
- 810Invoice
- Creates AP bill
Whichever standard your trading partners use
EDI standards vary by market. Your Acumatica workflow doesn't have to.
North America
X12
X12 is the EDI standard commonly used across North America, including the 850 purchase order, 855 acknowledgement, 856 advance shipping notice and 810 invoice.
UK and EU
EDIFACT & EANCOM
EDIFACT and EANCOM are commonly used across the UK and EU. They're different standards, not different levels of EDI capability.
Different standards. One Acumatica workflow.
UniLink builds each Smart Map around the requirements of the trading partner on the other end, with an implementation team that works through those requirements with you.
UniLink built the EDI engine.
AcuPower built what runs inside Acumatica.
AcuPower
Built the Acumatica side: the code that turns an inbound file into a populated sales order, and the screens your team sends documents from.
- Gold Certified Acumatica Partner
- 55 Acumatica-certified specialists
- Led by Yuriy Zaletskyy, 7-time Acumatica MVP
The UniLink Group
Built the EDI engine and the trading partner connections. They onboard your partners, build the maps and look after the account.
- 25+ years in cloud-based EDI
- Acumatica Certified
- Dedicated Acumatica team
“Most EDI projects don't fail at the mapping. They fail at the seam, where the documents are supposed to become records in the system you actually run the business on. That seam is where we spent our effort.”
“This is a natural extension of the Acumatica product that customers already know and trust. We're excited to have collaborated with AcuPower to bring seamless EDI connectivity directly into the platform they use every day.”
Who handles your EDI relationship?
UniLink. They sell it, onboard your trading partners and look after the account. When something needs changing inside Acumatica, they come to us.
Frequently Asked Questions
Yes. The Acumatica side of the integration is installed as an Acumatica customisation and adds EDI processing, controls and transfer logs inside Acumatica. Customer purchase orders become Acumatica sales orders, and your team sends acknowledgements, ASNs and invoices from the Acumatica workflow rather than re-keying them into a separate EDI portal.
The integration handles EDI 850 purchase orders, 855 purchase order acknowledgements, 856 advance shipping notices (ASNs) and 810 invoices across customer and vendor workflows.
They do. Incoming EDI orders can be processed individually, in bulk, or automatically on a schedule you set. Once processed, an inbound 850 becomes a populated sales order in Acumatica. You can start with manual processing and move to scheduled processing when you're ready.
UniLink sets up your EDI account and trading partner connections, and works with you to install and connect the Acumatica integration. Each customer or vendor is configured for the EDI documents they use, and UniLink builds and tests the required maps before the trading partner goes live.
Yes. On the sales side, customer EDI 850 purchase orders become sales orders in Acumatica, with 855 acknowledgements, 856 ASNs and 810 invoices going back out. On the purchasing side, Acumatica sends 850 purchase orders to vendors; an inbound 855 updates the purchase order, an 856 creates the purchase receipt, and an 810 creates the AP bill.
No. UniLink handles trading partner onboarding and mapping and provides ongoing EDI support, while the integration lets your team manage the day-to-day workflow from Acumatica.
Both, on different sides. The UniLink Group provides the EDI engine and brings 25+ years of trading partner connections. AcuPower built the Acumatica side: the code that turns an inbound EDI file into a populated sales order, and the screens that send the acknowledgement, shipping notice and invoice back out.
See it with your own trading partner
Bring the trading partner that sent you the mandate. UniLink will show you how their documents would land in your Acumatica and what onboarding them would involve.
Book a walkthrough with UniLink
Trip KnappBusiness Development Executive,
The UniLink Group
The UniLink Group
UniLink runs the demos. They built the EDI engine, and they'd be the ones onboarding your partners, so you're talking to the people who'd do the work.
